Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Conductor Project Artifacts Validator

agent evaluation skill risk: low

Conductor Project Artifacts Validator

Validates Conductor project artifacts for completeness by checking the conductor directory, tracks, and required files including index.md, product.md, tech-stack.md, workflow.md, a…

  • External action: low

SKILL 1 file

SKILL.md
Download 
---
name: antigravity-awesome-skills-conductor-validator-4b743fc6
description: "Validates Conductor project artifacts for completeness,"
---
# 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
```

## 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.

REQUIRED CONTEXT

  • conductor directory structure
  • tracks.md
  • plan.md

OPTIONAL CONTEXT

  • resources/implementation-playbook.md

ROLES & RULES

  1. Do not use this skill when the task is unrelated to check if conductor directory exists
  2. You need a different domain or tool outside this scope
  3. Use this skill only when the task clearly matches the scope described above
  4. Do not treat the output as a substitute for environment-specific validation, testing, or expert review
  5. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing

EXPECTED OUTPUT

Format
plain_text
Constraints
  • clarify goals and required inputs first
  • provide actionable steps and verification

SUCCESS CRITERIA

  • Clarify goals, constraints, and required inputs
  • Apply relevant best practices and validate outcomes
  • Provide actionable steps and verification

FAILURE MODES

  • May be used outside its defined scope
  • Output may not substitute for environment-specific validation, testing, or expert review

EXAMPLES

Includes examples of status markers in tracks.md, task markers in plan.md, and Track ID pattern.

CAVEATS

Dependencies
  • Requires resources/implementation-playbook.md when detailed examples are needed
Missing context
  • Expected output format or report structure after running the checks
  • What constitutes success vs failure for the validation
  • How the shell commands should be executed (local, remote, container, etc.)
Ambiguities
  • Description is truncated: "Validates Conductor project artifacts for completeness,"
  • Repeated placeholder text "check if conductor directory exists" appears in use/do-not-use sections
  • No definition or context for what "Conductor project" or "conductor/" directory structure actually is

QUALITY

OVERALL
0.28
CLARITY
0.35
SPECIFICITY
0.25
REUSABILITY
0.20
COMPLETENESS
0.30

IMPROVEMENT SUGGESTIONS

  • Replace the broken description and use/do-not-use sections with a single clear purpose statement
  • Add an explicit output template or checklist the validator should produce
  • Remove or generalize the hardcoded shell commands so the prompt can be reused across projects

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT