conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
72
60%
Does it follow best practices?
Impact
96%
1.39xAverage score across 3 eval scenarios
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/conductor-validator/SKILL.mdCheck 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:**Example: feature_user_auth_20250115
- Commit
57c135b
- Last updated
- First committed
Also appears in
on Sep 26, 2026
on Sep 26, 2026
on Sep 26, 2026
since Aug 19, 2026
since Aug 19, 2026
on Apr 16, 2026
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.