conductor-validator
This skill verifies the existence, structure, and status markers of Conductor project files and task plans to maintain consistency.
Install
mkdir -p .claude/skills/conductor-validator && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6559" && unzip -o skill.zip -d .claude/skills/conductor-validator && rm skill.zipInstalls to .claude/skills/conductor-validator
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Validates Conductor project artifacts for completeness,Key capabilities
- →Identify missing conductor directory structures
- →Check progress markers in tracks.md
- →Validate task status indicators in plan.md
- →Audit project artifacts against required naming conventions
How it works
The skill performs filesystem checks for specific directories and parses markdown files to match standardized status marker syntax.
Inputs & outputs
When to use conductor-validator
- →Verify Conductor project file structure
- →Check progress of project tracks
- →Validate task status in plan.md
- →Ensure all required artifacts are present
About this skill
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
- Track Name # Complete
**Task markers in plan.md:**
- Task description # Pending
- [~] Task description # In progress
- Task description # Complete
**Track ID pattern:**
<type><name><YYYYMMDD> Example: feature_user_auth_20250115
## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
When not to use it
- →When performing deep coding tasks unrelated to structure
- →When validating production environment deployments
Limitations
- →Only identifies structural issues within the defined directory
- →Does not validate the functional correctness of the project code
How it compares
It enforces strict project-wide consistency by checking against predefined status markers rather than manually reviewing individual files.
Compared to similar skills
conductor-validator side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| conductor-validator (this skill) | 1 | 4mo | No flags | Beginner |
| linear-ticket | 1 | 7mo | No flags | Intermediate |
| retro | 0 | 1mo | No flags | Intermediate |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by sickn33
View all by sickn33 →You might also like
linear-ticket
useautumn
Refine rough engineering thoughts into structured Linear tickets with GitHub permalinks
retro
Thawatchai-Petkaew
Run a story retrospective that distills lessons from closed work and feeds them back into the team's memory — appends to the `docs/delivery/LESSONS.md` ledger and proposes promotions into `.claude/rules/<role>.md` for owner approval. Use when a story is Done (merged + verified) and you want the Scou
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
python-code-style
wshobson
Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.
code-review-excellence
wshobson
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
code-walk-thru
pchalasani
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.