agentleFS
sammcjsammcj/agentic-coding/Skills/json-schema-lookup/SKILL.md

json-schema-lookup

Skill167 starsChanged 10 days agoApache-2.0View on GitHub

Guidelines for querying schemastore.org. Use when you need to validate or discover options for config files relating to popular open source projects.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search the catalog by name or filename pattern:

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

# 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

# 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

# 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.