Help us improve
Share bugs, ideas, or general feedback.
From task-harness
Validates a task harness YAML file for syntax, schema, and dependency errors before execution. Use when checking if a YAML task file is ready for execution without starting it. Trigger with "validate task harness yaml", "check yaml file", or "verify harness config".
npx claudepluginhub omara1-bakri-org/local-plugins --plugin task-harnessHow this skill is triggered — by the user, by Claude, or both
Slash command
/task-harness:validateThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Pre-validates a task harness YAML file to catch configuration errors before starting execution.
Validates task.md files for frontmatter presence, required fields (id, title), enum values (status, priority), unique IDs, dependency/parent validity, cycles, and naming conventions. Use when checking task directories.
Validates YAML syntax, normalizes formatting, schema-checks for Kubernetes/GitHub Actions/Docker Compose. Outputs minimal patches, issues, and validation commands.
Validates task files for format and convention errors using the taskmd CLI. Useful when checking task files for compliance before use.
Share bugs, ideas, or general feedback.
Pre-validates a task harness YAML file to catch configuration errors before starting execution.
The validate skill performs comprehensive checks on a YAML task file including:
This allows catching errors early before starting a potentially long-running harness session.
Verify the provided YAML file path is valid:
[[ -f "$YAML_FILE" ]] || echo "ERROR: File not found"
Use yq to verify the YAML is parseable:
yq eval '.' "$YAML_FILE" > /dev/null 2>&1
Check required fields:
harness.metadata.name - Harness identifierharness.tasks - Non-empty array of tasksid, name, and objective or promptEnsure no duplicate task IDs exist:
yq -r '.harness.tasks[].id' "$YAML_FILE" | sort | uniq -d
Check all depends_on references point to existing task IDs and detect circular dependencies.
Display comprehensive validation results with status and recommendations.
YAML Validation Report
======================
File: tasks/auth-implementation.yaml
Status: VALID ✓
Metadata:
Name: implement-auth-feature
Tasks: 5
Task Summary:
✓ plan-auth - Design Authentication System
✓ implement-model - Implement User Model
✓ implement-routes - Implement Routes
✓ write-tests - Write Tests
✓ update-docs - Update Documentation
Dependency Graph: Valid (no cycles)
Ready to start: /task-harness:start tasks/auth-implementation.yaml
YAML Validation Report
======================
File: tasks/broken.yaml
Status: INVALID ✗
Errors:
- Task 'implement' references non-existent dependency: 'design'
- Duplicate task ID: 'test'
- Circular dependency detected: A → B → A
Fix these errors before starting.
| Error | Cause | Resolution |
|---|---|---|
| File not found | Invalid path | Check file path spelling |
| YAML syntax error | Malformed YAML | Fix indentation/syntax |
| Duplicate task ID | Same ID used twice | Make IDs unique |
| Invalid dependency | Reference to non-existent task | Check depends_on spelling |
| Circular dependency | A depends on B depends on A | Restructure dependencies |
User: /task-harness:validate tasks/auth-feature.yaml
Skill: Parses YAML, validates all checks pass
Result:
YAML Validation Report
======================
File: tasks/auth-feature.yaml
Status: VALID ✓
Tasks: 5
Dependencies: Valid
Ready to start!
User: /task-harness:validate tasks/broken.yaml
Skill: Finds multiple validation errors
Result:
YAML Validation Report
======================
Status: INVALID ✗
Errors:
- Missing 'id' in task 2
- Circular dependency: plan → implement → plan
User: /task-harness:validate tasks/minimal.yaml
Skill: Valid but with suggestions
Result:
YAML Validation Report
======================
Status: VALID (with warnings)
Warnings:
- No test commands configured
- No lint commands configured
Consider adding quality gates.