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. It is especially useful for teams working in multi. Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "conductor-validator" skill to help with this workflow task. Context: Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
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
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
conductor-status
Display project status, active tracks, and next actions
conductor-setup
Initialize project with Conductor artifacts (product definition, tech stack, workflow, style guides)
conductor-revert
Git-aware undo by logical work unit (track, phase, or task)
conductor-new-track
Create a new track with specification and phased implementation plan
conductor-manage
Manage track lifecycle: archive, restore, delete, rename, and cleanup
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow
ml-antipattern-validator
Prevents 30+ critical AI/ML mistakes including data leakage, evaluation errors, training pitfalls, and deployment issues. Use when working with ML training, testing, model evaluation, or deployment.
data-validator
Validate data against schemas, business rules, and data quality standards.
configuration-validator
Validates environment variables, config files, and ensures all required settings are documented. Use when working with .env files, configs, or deployment settings.
docs-validator
Documentation quality validator for Logseq Template Graph. Checks documentation completeness, accuracy, formatting, links, and consistency. Activates when asked to "validate docs", "check documentation", "audit docs quality", "find broken links", or similar requests. Provides actionable feedback and specific fixes for documentation issues.
system-integration-validator
Validates system integration before deployment. Use when checking ports, database connections, frontend-backend APIs, or debugging blocked/stuck workflows. Detects dead ends, bottlenecks, circular dependencies.