conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
About this skill
This skill meticulously checks a 'Conductor' project's artifacts to ensure they are complete, consistent, and correctly structured. It performs a series of validation steps, including verifying the existence of the main `conductor/` directory, listing subdirectories within `conductor/tracks/`, and confirming the presence of critical documentation and configuration files such as `index.md`, `product.md`, `tech-stack.md`, `workflow.md`, and `tracks.md`. This automated validation is invaluable for confirming a project's setup, diagnosing configuration-related issues, or ensuring readiness before proceeding with development or deployment. It acts as an automated checklist, helping maintain project integrity and adherence to expected standards.
Best use case
Project setup verification; diagnosing missing files or incorrect directory structures; pre-implementation validation; ensuring project context is complete and consistent according to 'Conductor' project standards.
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
A clear report indicating the presence or absence of key 'Conductor' project directories and files, along with listings of track subdirectories. This helps the user quickly identify any inconsistencies, missing artifacts, or structural deviations from the expected 'Conductor' project layout.
Practical example
Example input
Validate the Conductor project artifacts in the current directory to ensure everything is set up correctly.
Example output
# Check if conductor directory exists drwxr-xr-x 5 user group 160 Apr 1 10:00 conductor/ # Find all track directories drwxr-xr-x 3 user group 96 Apr 1 10:05 conductor/tracks/ drwxr-xr-x 3 user group 96 Apr 1 10:05 conductor/tracks/feature-a/ drwxr-xr-x 3 user group 96 Apr 1 10:05 conductor/tracks/hotfix-b/ # Check for required files -rw-r--r-- 1 user group 1024 Apr 1 10:10 conductor/index.md -rw-r--r-- 1 user group 512 Apr 1 10:11 conductor/product.md -rw-r--r-- 1 user group 768 Apr 1 10:12 conductor/tech-stack.md -rw-r--r-- 1 user group 800 Apr 1 10:13 conductor/workflow.md -rw-r--r-- 1 user group 300 Apr 1 10:14 conductor/tracks.md
When to use this skill
- After initially setting up a Conductor project to confirm all essential components and the expected directory structure are in place.
- When troubleshooting errors or unexpected behavior related to project configuration, particularly when files might be missing or misplaced.
- Before starting a new development sprint, deploying a feature, or handing off a Conductor project, to ensure its integrity and completeness.
- To quickly get an overview of the Conductor project's structure and confirm it adheres to predefined standards.
When not to use this skill
- When the task does not involve validating a 'Conductor' project's file structure or its specific required artifacts.
- For general file system operations (e.g., creating, deleting, or moving files) unrelated to project validation.
- When seeking to modify or create Conductor project artifacts; this skill is diagnostic only.
- When the primary goal is to analyze the *content* of the project files, rather than their presence and structural integrity.
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 | Claude | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | easy | 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.
Which AI agents support this skill?
This skill is designed for Claude.
How difficult is it to install?
The installation complexity is rated as easy. You can find the installation instructions above.
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.
Related Guides
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agent for SaaS Idea Validation
Use AI agent skills for SaaS idea validation, market research, customer discovery, competitor analysis, and documenting startup hypotheses.
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
n8n-expression-syntax
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.
mermaid-expert
Create Mermaid diagrams for flowcharts, sequences, ERDs, and architectures. Masters syntax for all diagram types and styling.
mcp-builder-ms
Use this skill when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
makepad-deployment
CRITICAL: Use for Makepad packaging and deployment. Triggers on: deploy, package, APK, IPA, 打包, 部署, cargo-packager, cargo-makepad, WASM, Android, iOS, distribution, installer, .deb, .dmg, .nsis, GitHub Actions, CI, action, marketplace
macos-menubar-tuist-app
Build, refactor, or review SwiftUI macOS menubar apps that use Tuist.
kaizen
Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.
issues
Interact with GitHub issues - create, list, and view issues.
hugging-face-tool-builder
Your purpose is now is to create reusable command line scripts and utilities for using the Hugging Face API, allowing chaining, piping and intermediate processing where helpful. You can access the API directly, as well as use the hf command line tool.
git-pushing
Stage all changes, create a conventional commit, and push to the remote branch. Use when explicitly asks to push changes ("push this", "commit and push"), mentions saving work to remote ("save to github", "push to remote"), or completes a feature and wants to share it.
git-hooks-automation
Master Git hooks setup with Husky, lint-staged, pre-commit framework, and commitlint. Automate code quality gates, formatting, linting, and commit message enforcement before code reaches CI.
gh-review-requests
Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member. Use when asked to "find PRs I need to review", "show my review requests", "what needs my review", "fetch GitHub review requests", or "check team review queue".
fp-types-ref
Quick reference for fp-ts types. Use when user asks which type to use, needs Option/Either/Task decision help, or wants fp-ts imports.