OpenClaw · Skill
JSON Linter
A simple utility to recursively scan the workspace for .json files and validate their syntax using JSON.parse() .
Web & Frontend Development
v1.0.0
VirusTotal: Benign
Install
Start with the primary install command. Alternate entrypoints are included below for ClawHub and OpenClaw CLI users.
Primary command
clawhub install wanng-ide/json-linterClawHub installer
npx clawhub@latest install wanng-ide/json-linterOpenClaw CLI
openclaw skills install wanng-ide/json-linterDirect OpenClaw install
openclaw install wanng-ide/json-linterWhat this skill does
A simple utility to recursively scan the workspace for .json files and validate their syntax using JSON.parse() .
Why it matters
Scanning the entire workspace in one command surfaces all JSON errors at once instead of discovering them one file at a time at runtime.
Typical use cases
- Catching broken config files before a deployment
- Auditing a repo after a bulk find-and-replace on JSON
- Validating data asset files added by a non-technical teammate
- Checking memory files for syntax errors after manual edits
- Running a quick sanity check after merging multiple branches
Source instructions
JSON Linter
A simple utility to recursively scan the workspace for .json files and validate their syntax using JSON.parse().
Usage
# Scan the entire workspace (from current working directory)
node skills/json-linter/index.js
# Scan a specific directory
node skills/json-linter/index.js --dir path/to/dir
Output
JSON report containing:
scanned_at: Timestamptotal_files: Number of.jsonfiles scannedvalid_files: Number of valid filesinvalid_files: Number of invalid fileserrors: Array of error objects:path: Relative path to fileerror: Error message (e.g., "Unexpected token } in JSON at position 42")
Example Output
{
"scanned_at": "2026-02-14T21:45:00.000Z",
"total_files": 150,
"valid_files": 149,
"invalid_files": 1,
"errors": [
{
"path": "config/broken.json",
"error": "Unexpected token } in JSON at position 42"
}
]
}