mcpbeat

Conductor Validator

dokhacgiakhoa/conductor-validator

Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.

390 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill conductor-validator

The instruction itself

3 sections, as written by the author

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

How to use it

Copy the folder

Take dokhacgiakhoa/conductor-validator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.