Review schema first
Review schema as a single source of truth (Schema-first)From its SKILL.md
npx -y skills add yida29/archrip --skill review-schema-firstAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, as published. Nobody here has run it
Schema-first review — single source of truth & contracts
Audit whether the project has one authoritative schema, and whether all producers/consumers conform.
Scope
Use $ARGUMENTS to select the schema (default: the main JSON/data contract) and its producers/consumers.
Checklist
- Where is the authoritative schema? (JSON Schema / OpenAPI / protobuf / TS types)
- Is it duplicated as hand-written TS interfaces elsewhere?
- Do validators enforce the same rules as the schema?
- Are there multiple variants (input vs processed output)? If yes, are they explicitly versioned?
- Do templates/examples/docs match the schema?
- Is the schema reference URL pinned (tagged) vs
main?
Output format
- SSoT map: schema file(s) + all producers/consumers
- Divergences (schema vs code vs docs), with file paths
- Minimum path to Schema-first
- e.g. split input/output schemas, generate types, use a single validator
$ARGUMENTS