Imported from oimiragieo/agent-studio (
.claude/skills/schema-updater/SKILL.md). Install upstream withnpx skills add oimiragieo/agent-studio --skill schema-updater. Copyright stays with the author.
Schema Updater
Overview
Use this skill to refresh an existing JSON Schema safely: research current best practices, compare against the artifact it validates, generate a TDD patch backlog, apply updates, and verify ecosystem integration.
When to Use
- Schema no longer matches the artifact structure it validates
- New fields added to skills/agents/hooks/workflows but schema not updated
- Reflection flags schema validation failures
- User asks to audit/refresh an existing schema
The Iron Law
Never update a schema blindly. Every refresh must be evidence-backed, TDD-gated, and integration-validated.
Workflow
Step 0: Evaluate Current State
- Read the schema file and understand what it validates
- Find the artifacts it validates (skills, agents, hooks, workflows)
- Compare schema required fields against actual artifact structure
- Identify gaps: missing fields, wrong types, stale descriptions
Step 1: Research Best Practices
- Read
.claude/schemas/CLAUDE.mdfor schema conventions - Review similar schemas for patterns
- Check JSON Schema Draft-07 specification compliance
- Use
Skill({ skill: 'research-synthesis' })if external research needed
Step 2: Generate Patch Backlog
- List specific changes needed
- Prioritize: required field additions > type corrections > description updates
- Ensure backward compatibility where possible
Step 3: Apply Updates
- Write or update validation tests first (RED phase)
- Apply schema changes (GREEN phase)
- Refactor for clarity (REFACTOR phase)
- Use
Edittool — never rewrite the entire file
Step 4: Verify Integration
- Verify schema is valid JSON Schema Draft-07
- Verify
$idand$schemafields are present and correct - Validate at least 3 existing artifacts against the updated schema
- Run
pnpm lint:fix && pnpm format - Run schema validation tests
Step 5: Record
- Log changes via
MemoryRecordif significant - Update CHANGELOG.md entry
Domain-Specific Validation
- Schema MUST be valid JSON Schema Draft-07 (
$schema: "http://json-schema.org/draft-07/schema#") - Schema MUST have
$idfield matching its file path - Schema MUST be referenced by at least one validator or test
- Required fields MUST match actual artifact structure
- Default values MUST match framework conventions
Anti-Patterns
- Adding required fields that break existing valid artifacts
- Removing fields without checking all consumers
- Using features beyond Draft-07 (e.g., Draft-2020-12
prefixItems) - Making the schema so strict it rejects valid edge cases