conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
Best use case
conductor-validator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
Teams using conductor-validator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/conductor-validator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How conductor-validator Compares
| Feature / Agent | conductor-validator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Check if conductor directory exists ls -la conductor/ # Find all track directories ls -la conductor/tracks/ # Check for required files ls conductor/index.md conductor/product.md conductor/tech-stack.md conductor/workflow.md conductor/tracks.md ``` ## Use this skill when - Working on check if conductor directory exists tasks or workflows - Needing guidance, best practices, or checklists for check if conductor directory exists ## Do not use this skill when - The task is unrelated to check if conductor directory exists - You need a different domain or tool outside this scope ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Pattern Matching **Status markers in tracks.md:** ``` - [ ] Track Name # Not started - [~] Track Name # In progress - [x] Track Name # Complete ``` **Task markers in plan.md:** ``` - [ ] Task description # Pending - [~] Task description # In progress - [x] Task description # Complete ``` **Track ID pattern:** ``` <type>_<name>_<YYYYMMDD> Example: feature_user_auth_20250115 ```
Related Skills
doc-ctr-validator
Validate Data Contracts (CTR) documents against Layer 8 schema standards
workflow-conductor
Workflow orchestration and automation engine
conductor-revert
Git-aware undo by logical work unit (track, phase, or task)
ahu-conductor
Air Handler Design Pipeline Orchestrator
conductor-manage
Manage track lifecycle: archive, restore, delete, rename, and cleanup
api-validator
Validate REST API standards compliance (versioning, naming, HTTP methods, status codes, pagination, Swagger). Use when checking endpoints before deployment, reviewing API design, or ensuring documentation completeness (e.g., "Validate User API", "Check Product endpoints").
api-contract-validator
Validates type contracts between TypeScript interfaces and Pydantic models. Detects field mismatches and type inconsistencies. Related: frontend-backend-mapper for endpoint discovery.
advanced-oscal-validator
Perform comprehensive OSCAL validation using community-inspired patterns including JSON schema validation, business rule validation, cross-reference checking, and best practices from IBM Trestle, oscal-pydantic, and Lula. Use for thorough document quality assurance.
ado-resource-validator
Validates Azure DevOps projects, area paths, and teams exist with auto-creation of missing resources. Use when setting up ADO integration, configuring .env variables, or troubleshooting missing project errors. Supports project-per-team, area-path-based, and team-based strategies.
amcs-validator
Score composed artifacts against blueprint rubric. Evaluates hook density, singability, rhyme tightness, section completeness, and profanity compliance. Returns scores and issues list to determine if fix loop is needed. Use after COMPOSE to validate artifacts before rendering.
agent-task-conductor
Conduct multi-agent task orchestration and workflow coordination.
agent-config-validator
Validate AgentConfig definitions for the Agent Framework. Use when creating or modifying agent configurations to ensure correct structure, valid tool references, and proper sub-agent composition. Validates TypeScript interfaces and Python Pydantic models.