json-schema-lookup — Claude Code skill: what it does, how to install
json-schema-lookup — a skill that points Claude at the SchemaStore catalog so it can validate config files and look up allowed options.
Apache-2.0 ★ 173 updated 2026-10-24
npx skills add sammcj/agentic-coding --skill json-schema-lookup -a claude-codeWhat json-schema-lookup does
The skill lays out a lookup routine for SchemaStore. The agent pulls the catalog from https://www.schemastore.org/api/json/catalog.json, picks the entry whose name or fileMatch pattern fits the file at hand, then fetches that entry's url.
From the schema it reads top-level keys, a single field with its type and enum values, the required list, and shared definitions reached through $ref. Everything runs in the shell with curl piped into jq; WebFetch covers the same ground when curl is awkward.
Size is the real snag. Pulling a whole schema is wasteful, so the skill asks for narrow paths and advises caching the catalog when several lookups happen in one session. Some schemas compose their properties through allOf or anyOf, and skipping those arrays leaves the property list short.
What it helps with
- check which keys a
tsconfig.jsonaccepts - find a config schema by its filename pattern
- list the
enumvalues a field allows - see required fields before editing a config
- read one branch of a large schema without pulling the whole document
Example prompts for the agent
- Look up the schema for
package.jsonin SchemaStore and tell me which fields are required. - Does the
tsconfig.jsonschema allowesnextfortarget? - Pull the catalog entry for
.eslintrcand list its top-level properties.
How to install json-schema-lookup
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill json-schema-lookup -a claude-code2Manually: put the files in place
~/.claude/skills/json-schema-lookup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/json-schema-lookup/
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill json-schema-lookup -a codex2Manually: put the files in place
.agents/skills/json-schema-lookup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill json-schema-lookup -a cursor2Manually: put the files in place
.cursor/skills/json-schema-lookup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sammcj/agentic-coding Skills/json-schema-lookup/SKILL.md2Manually: put the files in place
.github/skills/json-schema-lookup/SKILL.md1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill json-schema-lookup -a gemini-cli2Platform CLI
gemini skills install https://github.com/sammcj/agentic-coding --path Skills/json-schema-lookupManually: put the files in place
.devin/skills/json-schema-lookup/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about json-schema-lookup
How do I install json-schema-lookup in Claude Code?
Run npx skills add sammcj/agentic-coding --skill json-schema-lookup -a claude-code. The skill lands at ~/.claude/skills/json-schema-lookup/SKILL.md.
What does json-schema-lookup do?
It gives Claude a procedure for fetching config schemas from SchemaStore and reading them with curl and jq: properties, types, enums, required fields.
What does the skill need in order to run?
Network access for curl or WebFetch, plus jq to parse the JSON. Its allowed-tools list also covers yq, grep, head and less.
Source text
SKILL.md · Apache-2.0
---
name: json-schema-lookup
description: >-
Guidelines for querying schemastore.org. Use when you need to validate or discover
options for config files relating to popular open source projects.
allowed-tools: WebFetch Bash(curl *) Bash(jq *) Bash(yq *) Bash(grep *) Bash(head *) Bash(less *)
---
# JSON Schema Lookup via SchemaStore
Query schemastore.org's catalog of public configuration file schemas to validate structure, discover options, and check allowed values.
## API
- **Catalog**: `https://www.schemastore.org/api/json/catalog.json`
- Structure: `{ "schemas": [{ "name", "description", "fileMatch", "url", "versions"? }] }`
- **Individual schemas**: Fetch the `url` from the matching catalog entry
## Workflow
### 1. Find the schema
Search the catalog by name or filename pattern:
```bash
# Search by name (case-insensitive)
curl -s https://www.schemastore.org/api/json/catalog.json | jq '.schemas[] | select(.name | test("tsconfig"; "i")) | {name, url, fileMatch}'
# Search by filename match
curl -s https://www.schemastore.org/api/json/catalog.json | jq '.schemas[] | select(.fileMatch[]? | test("package\\.json")) | {name, url}'
```
Alternatively, use WebFetch on the catalog URL and ask for the relevant entry.
### 2. Fetch and inspect the schema
```bash
# List top-level properties
curl -s SCHEMA_URL | jq '.properties | keys'
# Inspect a specific field (type, enum values, description)
curl -s SCHEMA_URL | jq '.properties.FIELD_NAME'
# Check definitions/shared types (schemas use $ref to these)
curl -s SCHEMA_URL | jq '.definitions.DEF_NAME.properties'
# Get the full schema (warning - might be large!)
curl -s SCHEMA_URL | jq .
```
### 3. Common queries
```bash
# Find enum values for a field
curl -s SCHEMA_URL | jq '.properties.FIELD.enum'
# List nested properties (e.g. compilerOptions in tsconfig)
curl -s SCHEMA_URL | jq '.definitions.compilerOptionsDefinition.properties.compilerOptions.properties | keys'
# Find all required fields
curl -s SCHEMA_URL | jq '.required'
```
## Tips
- Some schemas use `allOf`/`anyOf` composition -- check those arrays for the full property set
- The `versions` field on catalog entries provides version-specific schema URLs when available
- Schema URLs vary: some point to `json.schemastore.org`, others to `raw.githubusercontent.com`
- For large schemas, query specific paths rather than dumping the entire document
- Cache the catalog response locally if making multiple lookups in one session
© sammcj · Apache-2.0 · sammcj/agentic-coding