npx skills add sickn33/agentic-awesome-skills --skill conductor-validator
rmyndharis/antigravity-skills
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
Installation
npx skills add rmyndharis/antigravity-skills --skill conductor-validator
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Configure .conductor/settings.toml, migrate legacy conductor.json, and set up local/cloud Condu…
14 installsUse when the user asks to "run my launch day", "build a launch day runbook / war room", or "dec…
10 installsWalk the guided 6-gate release runbook (G0 readiness, G1 adversarial review, G2 version bump an…
494 installsExecute tasks from a track's implementation plan following TDD workflow
382 installsManage track lifecycle: archive, restore, delete, rename, and cleanup
373 installsCreate a new track with specification and phased implementation plan
372 installsAlso in this package
Other skills from rmyndharis/antigravity-skills · top by installs.
npx skills add rmyndharis/antigravity-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
Read Glob Grep BashMore metadata
- model
- opus
- color
- cyan
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,456 B -
docs
SUMMARY.md205 B
History
- First seen on skills.sh
- First recorded snapshot · 18 installs
SKILL.md
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.
## Pattern Matching
**Status markers in tracks.md:**
- Track Name # Not started
- [~] Track Name # In progress
- Track Name # Complete
**Task markers in plan.md:**
- Task description # Pending
- [~] Task description # In progress
- Task description # Complete
**Track ID pattern:**
<type><name><YYYYMMDD> Example: featureuserauth_20250115