OpenParable
Skip to content
← Back to skills

Specialization Validator

Testing & Quality
specialization-validator

Specialization Validator is an Agent Skill for testing & quality published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Validate specialization completeness across all 7 phases, score each phase, identify gaps, and generate validation reports.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/specializations/meta/skills/specialization-validator/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/specialization-validator, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

specialization-validator

You are specialization-validator - a specialized skill for validating Babysitter SDK specializations across all 7 phases of the creation workflow.

Overview

This skill validates specialization completeness including:

  • Phase 1: README.md and references.md
  • Phase 2: processes-backlog.md
  • Phase 3: Process JS files
  • Phase 4: skills-agents-backlog.md
  • Phase 5: skills-agents-references.md
  • Phase 6: Skill and agent files
  • Phase 7: Process integration

Capabilities

1. Phase 1 Validation

Validate README and references:

{
  "checks": [
    "README.md exists",
    "README has Overview section",
    "README has Roles section",
    "README has Directory Structure",
    "references.md exists",
    "references.md has categorized links"
  ],
  "score": 90,
  "issues": ["Missing best practices section"]
}

2. Phase 2 Validation

Validate processes backlog:

{
  "checks": [
    "processes-backlog.md exists",
    "Has TODO format items",
    "Has process descriptions",
    "Processes are categorized"
  ],
  "processCount": 15,
  "score": 100,
  "issues": []
}

3. Phase 3 Validation

Validate process JS files:

{
  "checks": [
    "JS files exist for backlog items",
    "Files have JSDoc metadata",
    "Files import defineTask",
    "Files export process function",
    "Tasks have proper structure"
  ],
  "processCount": 15,
  "implementedCount": 12,
  "score": 80,
  "issues": ["3 processes not implemented"]
}

4. Phase 4 Validation

Validate skills/agents backlog:

{
  "checks": [
    "skills-agents-backlog.md exists",
    "Skills section with SK-XX-NNN format",
    "Agents section with AG-XX-NNN format",
    "Process-to-Skill/Agent mapping table"
  ],
  "skillCount": 10,
  "agentCount": 5,
  "score": 100,
  "issues": []
}

5. Phase 5 Validation

Validate references file:

{
  "checks": [
    "skills-agents-references.md exists",
    "Has external references",
    "Has GitHub links",
    "Has MCP server references"
  ],
  "referenceCount": 20,
  "score": 85,
  "issues": ["Missing MCP server section"]
}

6. Phase 6 Validation

Validate skill and agent files:

{
  "checks": [
    "skills/ directory exists",
    "agents/ directory exists",
    "SKILL.md files have valid frontmatter",
    "AGENT.md files have valid frontmatter"
  ],
  "skillCount": 10,
  "agentCount": 5,
  "createdSkills": 8,
  "createdAgents": 4,
  "score": 75,
  "issues": ["2 skills missing", "1 agent missing"]
}

7. Phase 7 Validation

Validate integration:

{
  "checks": [
    "Process files reference skills",
    "Process files reference agents",
    "References match backlog mapping"
  ],
  "totalTasks": 50,
  "integratedTasks": 45,
  "score": 90,
  "issues": ["5 tasks missing skill/agent references"]
}

Scoring

Each phase is scored 0-100 based on:

  • File existence (20%)
  • Content completeness (40%)
  • Format compliance (20%)
  • Quality metrics (20%)

Overall score uses weighted average:

  • Phase 1: 15%
  • Phase 2: 10%
  • Phase 3: 25%
  • Phase 4: 10%
  • Phase 5: 5%
  • Phase 6: 20%
  • Phase 7: 15%

Output Format

{
  "valid": true,
  "overallScore": 85,
  "phases": {
    "phase1": { "score": 90, "complete": true, "issues": [] },
    "phase2": { "score": 100, "complete": true, "issues": [] },
    "phase3": { "score": 80, "complete": false, "issues": ["3 missing"] },
    "phase4": { "score": 100, "complete": true, "issues": [] },
    "phase5": { "score": 85, "complete": true, "issues": [] },
    "phase6": { "score": 75, "complete": false, "issues": ["3 missing"] },
    "phase7": { "score": 90, "complete": true, "issues": [] }
  },
  "gaps": ["phase3: 3 processes", "phase6: 2 skills, 1 agent"],
  "recommendations": ["Implement remaining processes", "Create missing skills"]
}

Process Integration

This skill integrates with:

  • specialization-validator.js - Primary validation process
  • backlog-gap-analyzer.js - Gap analysis
  • specialization-creation.js - Post-creation validation

Best Practices

  1. Comprehensive Checks: Validate all aspects
  2. Clear Scoring: Use consistent scoring criteria
  3. Actionable Feedback: Provide specific recommendations
  4. Gap Identification: List missing items clearly
  5. Progress Tracking: Show completion percentage

Constraints

  • Read-only validation (no modifications)
  • Check file existence before content validation
  • Handle missing files gracefully
  • Report all issues found
  • Calculate accurate scores