メニュー
Validate JSON data against a JSON Schema. Use when the user asks to validate JSON against a schema, check if JSON conforms to a schema, test JSON data validity, or verify JSON structure matches a schema definition.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user needs help with path queries, JSON transformations, schema validation, or safe JSON editing workflows. Triggered by questions about JSON operations, data extraction, file merging, or validation strategies.
Scan project dependencies for known vulnerabilities. Automatically detect and parse package files (package.json, requirements.txt, Gemfile, go.mod, pom.xml) and check all dependencies against the CVE database. Use when you want to audit a project for security vulnerabilities, check if dependencies have known CVEs, or generate a vulnerability report for compliance.
Search for Common Vulnerabilities and Exposures (CVEs) by ID (e.g., CVE-2024-1086) or by product name (e.g., OpenSSL, Apache Tomcat). Get detailed vulnerability information including severity scores, affected software versions, and references. Use when the user wants to look up CVE information, check if a product has known vulnerabilities, or research security issues.
Validate a JSON file against the schema referenced in its $schema property. Use when the user asks to check JSON against its own schema, validate self-describing JSON, auto-validate JSON files, or verify JSON with embedded schema reference.
Validate that a JSON Schema is well-formed and conforms to the JSON Schema specification. Use when the user asks to check if a schema is valid, verify schema syntax, validate schema structure, or check a JSON Schema file for errors.
Analyze Wayback Machine capture frequency and rate for a URL. Use when the user wants to see how often a URL is archived, capture statistics, or archive density over time.
| name | schema-validate |
| description | Validate JSON data against a JSON Schema. Use when the user asks to validate JSON against a schema, check if JSON conforms to a schema, test JSON data validity, or verify JSON structure matches a schema definition. |
Validate JSON data files against a JSON Schema definition.
npx tsx scripts/validate.ts <json-file> --schema=<schema-file> [options]
| Argument | Required | Description |
|---|---|---|
json-file | Yes | Path to the JSON file to validate |
| Option | Description |
|---|---|
--schema=FILE | Path to the JSON Schema file (required) |
--all-errors | Report all errors, not just the first |
--strict | Enable strict mode validation |
--verbose | Show detailed validation output |
--format | Output format: text (default), json |
Valid JSON:
Valid
Schema: user-schema.json
File: user.json
Invalid JSON:
Invalid (3 errors)
1. /email: must match format "email"
2. /age: must be >= 0
3. /name: must be string
npx tsx scripts/validate.ts data.json --schema=schema.json
npx tsx scripts/validate.ts data.json --schema=schema.json --all-errors
npx tsx scripts/validate.ts data.json --schema=schema.json --format=json
Run from the json-schema plugin directory: ~/.claude/plugins/cache/json-schema/
Validate multiple files against the same schema using glob patterns:
# Validate all JSON files in a directory
for f in data/*.json; do npx tsx scripts/validate.ts "$f" --schema=schema.json; done
When using --format=json:
{
"valid": false,
"file": "user.json",
"schema": "user-schema.json",
"errors": [
{
"path": "/email",
"message": "must match format \"email\"",
"keyword": "format"
}
]
}
Common validation errors:
must be string - Type mismatchmust match format "..." - Format validation failedmust be >= N / must be <= N - Number range violationmust NOT have additional properties - Unknown propertymust have required property '...' - Missing required fieldmust match pattern "..." - String pattern mismatchschema-meta to validate that a schema is well-formedschema-check to validate a JSON file against its embedded $schema