4a5f1234bb
* chore: upgrade maintenance scripts to robust PyYAML parsing - Replaces fragile regex frontmatter parsing with PyYAML/yaml library - Ensures multi-line descriptions and complex characters are handled safely - Normalizes quoting and field ordering across all maintenance scripts - Updates validator to strictly enforce description quality * fix: restore and refine truncated skill descriptions - Recovered 223+ truncated descriptions from git history (6.5.0 regression) - Refined long descriptions into concise, complete sentences (<200 chars) - Added missing descriptions for brainstorming and orchestration skills - Manually fixed imagen skill description - Resolved dangling links in competitor-alternatives skill * chore: sync generated registry files and document fixes - Regenerated skills index with normalized forward-slash paths - Updated README and CATALOG to reflect restored descriptions - Documented restoration and script improvements in CHANGELOG.md * fix: restore missing skill and align metadata for full 955 count - Renamed SKILL.MD to SKILL.md in andruia-skill-smith to ensure indexing - Fixed risk level and missing section in andruia-skill-smith - Synchronized all registry files for final 955 skill count * chore(scripts): add cross-platform runners and hermetic test orchestration * fix(scripts): harden utf-8 output and clone target writeability * fix(skills): add missing date metadata for strict validation * chore(index): sync generated metadata dates * fix(catalog): normalize skill paths to prevent CI drift * chore: sync generated registry files * fix: enforce LF line endings for generated registry files
66 lines
1.5 KiB
Markdown
66 lines
1.5 KiB
Markdown
---
|
|
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.
|
|
|
|
'
|
|
risk: unknown
|
|
source: community
|
|
date_added: '2026-02-27'
|
|
---
|
|
|
|
# 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
|
|
```
|