Inspect JSON files or API responses with jq and produce a compact map of keys and value types. Use the result to understand nested data before writing queries or processing the full dataset.
Infer JSON structure and types with jq-based schema discovery.
Review the instructions the agent will receive before you install.
Use ./.github/skills/jqschema/jqschema.sh to generate a compact structural schema (keys + types) from JSON input. Pipe any JSON source through it to discover structure before querying full data.
# Analyze a file or command output
cat data.json | ./.github/skills/jqschema/jqschema.sh
gh api search/repositories?q=language:go | ./.github/skills/jqschema/jqschema.sh
The script replaces object values with type names ("string", "number", "boolean", "null"), reduces arrays to first-element structure, and outputs compact JSON. Use perPage: 1 to fetch minimal data when exploring unknown API shapes.
Example: {"total_count":1000,"items":[{"login":"user1","id":123}]} → {"total_count":"number","items":[{"login":"string","id":"number"}]}
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.
Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.
Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.
Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.
Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.
Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.