Skills Check if conductor directory exists
📦

Check if conductor directory exists

Low Risk ⚙️ External commands

Validate Conductor project structure and progress

Conductor projects require consistent artifact validation across setup and implementation phases. This skill automates directory checks and progress marker verification to ensure project completeness.

Supports: Claude Codex Code(CC)
⚠️ 67 Poor
1

Download the skill ZIP

2

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

3

Toggle on and start using

Test it

Using "Check if conductor directory exists". Check if the conductor directory exists

Expected outcome:

Directory 'conductor/' exists with 6 items: index.md, product.md, tech-stack.md, workflow.md, tracks.md, and tracks/ subdirectory.

Using "Check if conductor directory exists". Verify required Conductor files

Expected outcome:

All required files present: index.md, product.md, tech-stack.md, workflow.md, tracks.md

Security Audit

Low Risk
v1 • 2/24/2026

This skill uses bash commands exclusively for read-only file system checks (ls -la, ls). The external_commands risk is minimal because all commands are hardcoded directory listings with no user input injection vectors. No network access, code execution, or file modification capabilities present.

0
Files scanned
0
Lines analyzed
2
findings
1
Total audits
Low Risk Issues (1)
SKILL.md:15-21
External Command Usage
Skill executes bash commands for directory and file listing. Commands are hardcoded with no user input, limiting injection risk.

Risk Factors

⚙️ External commands (1)
SKILL.md:15-21
Audited by: claude

Quality Score

38
Architecture
100
Maintainability
87
Content
31
Community
88
Security
74
Spec Compliance

What You Can Build

Post-Setup Validation

After initializing a new Conductor project, verify all required artifacts are present and properly structured before beginning implementation work.

Diagnostic Troubleshooting

When experiencing workflow issues or missing context, quickly audit the project structure to identify gaps in documentation or track organization.

Pre-Implementation Review

Before starting new feature tracks, confirm the project context is complete and all prerequisite documentation exists for informed decision-making.

Try These Prompts

Basic Directory Check 
Check if the conductor directory exists and list its contents to verify the project structure is in place.
Required Files Validation 
Verify all required Conductor files exist: index.md, product.md, tech-stack.md, workflow.md, and tracks.md. Report any missing files.
Track Progress Review 
List all tracks in the conductor/tracks directory and check their status markers in tracks.md. Summarize which tracks are not started, in progress, or complete.
Full Project Validation 
Perform a complete Conductor project validation: check directory structure, verify required files, review track status markers, and validate track ID naming conventions. Provide a summary report of any issues found.

Best Practices

  • Run validation after initial project setup to confirm all artifacts are created correctly
  • Check status markers in tracks.md regularly to maintain accurate progress tracking
  • Follow the track ID naming convention: type_name_YYYYMMDD for consistent organization

Avoid

  • Do not use this skill to modify or create files - it is read-only validation only
  • Avoid running validation on non-Conductor projects - results will be inaccurate
  • Do not ignore missing file warnings - address gaps before proceeding with implementation

Frequently Asked Questions

What files does this skill check for?
The skill verifies the presence of index.md, product.md, tech-stack.md, workflow.md, and tracks.md in the conductor directory root.
Can this skill fix missing files?
No, this skill only performs read-only validation. It identifies missing files but does not create or modify them.
What do the status markers mean in tracks.md?
Status markers indicate track progress: [ ] means not started, [~] means in progress, and [x] means complete.
What is the correct track ID format?
Track IDs should follow the pattern: type_name_YYYYMMDD (for example: feature_user_auth_20250115).
When should I run this validation?
Run validation after project setup, when diagnosing issues, or before starting implementation to verify project context is complete.
Does this skill work with all AI tools?
Yes, this skill is compatible with Claude, Codex, and Claude Code, using Read, Glob, Grep, and Bash tools.

Developer Details

Author

sickn33

License

MIT

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/conductor-validator

Ref

main

File structure

📄 SKILL.md