New to Claude Skills? Learn how to install them →

Csickn33 on GitHub

Conductor Validator

Free

Ensure your Conductor project artifacts are complete and correct.

Get this skill

Free · Opens the source repo

What Conductor Validator does

The Conductor Validator skill is designed to help developers and designers verify the integrity of their Conductor project artifacts. This skill focuses on validating key components of the project, ensuring that all necessary files are present and that the directory structure is correct. By using this skill, users can quickly diagnose issues during the setup phase or before implementation, making it an essential tool for maintaining project quality.

When you run the Conductor Validator, it performs a series of checks to confirm the existence of the Conductor directory and its required files. This includes verifying that essential documents such as index.md, product.md, tech-stack.md, workflow.md, and tracks.md are in place. Additionally, it lists all track directories to ensure that the project's structure aligns with expected conventions. These validations help prevent potential errors that could arise from missing or misconfigured files.

This skill is particularly useful for teams working with Conductor frameworks or similar project management setups. It provides a straightforward way to maintain project organization and completeness, which is critical for efficient workflows. By integrating this validation step into your routine, you can save time and reduce the risk of issues during project execution.

However, it’s important to note that this skill is intended for specific tasks related to validating Conductor projects. It should not be used for unrelated tasks or as a substitute for comprehensive testing and expert review. Users should ensure they have a clear understanding of their project requirements and the necessary inputs before utilizing this skill.

When to use it

Use this skill when setting up a Conductor project or diagnosing issues with existing artifacts.

When not to use it

Avoid using this skill for tasks outside the scope of Conductor validation or when different tools are required.

What you can build with it

Setup Verification

After setting up a new Conductor project, use this skill to ensure all necessary files are present.

Troubleshooting

When encountering issues in your Conductor project, run this skill to validate the project structure and files.

Pre-Implementation Check

Before implementing your project, verify that all artifacts are complete and correctly configured using this skill.

How to install Conductor Validator

View source

1. Install with the skills CLI

npx skills add sickn33/agentic-awesome-skills/conductor-validator --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by sickn33

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
  • 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: 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.

Frequently asked questions about Conductor Validator

Similar skills