メニュー
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.
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 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.
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-meta |
| description | 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. |
Validate that a JSON Schema document is itself a valid schema according to the JSON Schema specification.
npx tsx scripts/meta-validate.ts <schema-file> [options]
| Argument | Required | Description |
|---|---|---|
schema-file | Yes | Path to the JSON Schema file to validate |
| Option | Description |
|---|---|
--draft=VERSION | JSON Schema draft version (draft-04, draft-06, draft-07, 2019-09, 2020-12). Default: auto-detect |
--strict | Enable strict mode (additional validation rules) |
--verbose | Show detailed validation information |
Valid schema:
Valid JSON Schema (draft-2020-12)
Keywords: 5
Definitions: 2
Invalid schema:
Invalid JSON Schema
Error: "type" must be a string or array
Path: /properties/name/type
npx tsx scripts/meta-validate.ts schema.json
npx tsx scripts/meta-validate.ts schema.json --draft=draft-07
npx tsx scripts/meta-validate.ts schema.json --strict --verbose
Run from the json-schema plugin directory: ~/.claude/plugins/cache/json-schema/
The script auto-detects the JSON Schema draft version from:
$schema keyword in the documentSupported drafts:
draft-04 - JSON Schema Draft 4draft-06 - JSON Schema Draft 6draft-07 - JSON Schema Draft 72019-09 - JSON Schema Draft 2019-092020-12 - JSON Schema Draft 2020-12 (default)When --strict is enabled, additional validations are performed:
$schema declarationschema-validate to validate JSON data against a schemaschema-check to validate a JSON file against its embedded $schema