conductor-validator
Has your agent check if project files are complete and correct. It's useful to ensure everything is right before starting or if something goes wrong.
What it does
This agent checks if the important files for a Conductor project are complete, correct, and consistent with each other. It helps ensure everything is in the right place before proceeding.
When to use it
- ✓After setting up a Conductor project.
- ✓When trying to understand why something isn't working.
- ✓Before starting to work on a new part of the project.
Example of what to ask your AI
“Validate my Conductor project files.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
It reads the configuration files and compares them with the files that actually exist in your project. Then, it checks if links and status markers are correct and reports what needs to be fixed.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill conductor-validatorOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/conductor-validator/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Validate Conductor workflow artifacts
When to Use
Inspect a project that actually uses a conductor/ workflow directory after setup, before resuming a track, or when diagnosing inconsistent plans/status. This is distinct from the Rails Conductor desktop-app setup (conductor.json/script/server).
Read-only discovery
# Run from the explicitly selected project root; missing paths are findings, not permission to create them.
ls -ld conductor/ conductor/tracks/
ls conductor/index.md conductor/product.md conductor/tech-stack.md conductor/workflow.md conductor/tracks.md
Validation procedure
- Read current project instructions and the actual configured Conductor workflow/version.
- Compare the declared artifact list with the project’s real files; report missing, unreadable and extra artifacts separately.
- Resolve local index/track links, track IDs and plan/status markers against their referenced content. Do not assume directory presence proves completeness.
- Reconcile completed markers with recorded implementation/test evidence and the current revision; report stale or conflicting state without inventing a pass.
- Output a concise list of file, observed inconsistency, expected contract and proposed correction. Apply fixes only when requested; preserve existing plans and dirty work.
No implementation-playbook file or runnable validator script is bundled. The procedure above is the complete local guide; optional project-specific automation must actually exist and be reviewed before execution.
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
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.
FAQ
What is a 'Conductor project'?
It's a type of project that uses a specific structure of files and folders to organize work, like a roadmap or action plan.
What are 'artifacts'?
These are the essential files and information that make up the project, such as the main plan, technical details, and steps to follow.
Does it fix problems by itself?
No, it only reports what the problems are and how to fix them. You need to decide if and how to apply the corrections.
Details
Original description by the author
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context. '
Popularity
- GitHub stars
- 48k
- Ranking position
- #2622
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
benchmark-optimization-loop
Has your agent improve something's speed in a measured way. It tests multiple versions and chooses the fastest one that still works correctly.
affaan-m/ECC
change-impact
Helps your agent analyze the impact of code changes before making them. It compares the planned vs. actual results afterward, covering paths, data, tests, and documentation. Useful for risky or system-wide changes.
affaan-m/ECC
click-path-audit
Lets your agent trace all user buttons and interactions to find bugs. It finds issues where functions seem to work alone but fail together. Useful when bugs persist even after debugging.
affaan-m/ECC