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.

First seen Jan 23, 2026

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.

Also in this package

Other skills from rmyndharis/antigravity-skills · top by installs.

npx skills add rmyndharis/antigravity-skills

Browse all from 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.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 1.5K
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead Glob Grep Bash
Declared agents antigravity
More metadata
model
opus
color
cyan

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,456 B
  • docs SUMMARY.md 205 B

History

  1. First seen on skills.sh
  2. 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