Skip to content
Back to skills

Conductor Validator

ASecurity

Validates Conductor project artifacts for completeness,

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 8, 2026
toolsgobash

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add monang404/lunawave --skill conductor-validator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Conductor Validator?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Conductor Validator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/monang404-conductor-validator/badge)](https://www.skillsdirectory.com/skills/monang404-conductor-validator)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: conductor-validator
description: Validates Conductor project artifacts for completeness,
  consistency, and correctness. Use after setup, when diagnosing issues, or
  before implementation to verify project context.
allowed-tools: Read Glob Grep Bash
metadata:
  model: opus
  color: cyan
---

# 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
- [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
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…