Conductor validator

Skill bg-szy/TOP-SKILLS/skills/marketplace/conductor-validator

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install

npx -y skills add bg-szy/TOP-SKILLS --skill conductor-validator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.

SKILL.md

1.5 KB, 289 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it: 1 file

14.4 KB alongside SKILL.md

skill-report.json14.4 KB