agent operations skill risk: low

Conductor Project Artifacts Validator

The prompt defines a skill for validating Conductor project artifacts by running shell commands to check directories and required files, applying status marker patterns from tracks…

External action: low

SKILL 1 file

SKILL.md

Download

---
name: antigravity-awesome-skills-conductor-validator
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

ROLES & RULES

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.

EXPECTED OUTPUT

Format

plain_text

Constraints

clarify goals, constraints, and required inputs
apply relevant best practices and validate outcomes
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.

EXAMPLES

Includes status markers in tracks.md, task markers in plan.md, and Track ID pattern with example.

CAVEATS

Missing context

Definition or background on what a 'Conductor' project is
Expected output format or report structure for the validation results
How validation failures should be reported or handled

Ambiguities

The 'Use this skill when' and 'Do not use this skill when' sections contain repetitive placeholder text ('check if conductor directory exists') that was never replaced with meaningful content.
Description field is truncated: 'Validates Conductor project artifacts for completeness,'

QUALITY

OVERALL: 0.45
CLARITY: 0.55
SPECIFICITY: 0.60
REUSABILITY: 0.25
COMPLETENESS: 0.40

IMPROVEMENT SUGGESTIONS

Replace all placeholder phrases in the 'Use this skill when' section with accurate, specific usage criteria.
Add a required 'Output format' section that specifies how validation results should be presented.
Complete the truncated description sentence.

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.