workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
64
47%
Does it follow best practices?
Impact
100%
1.75xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/conductor/skills/workflow-patterns/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description relies heavily on domain-specific jargon ('Conductor', 'phase checkpoints', 'verification protocol') without explaining what concrete actions the skill performs. While it includes a 'Use when' clause, the triggers are abstract rather than grounded in specific user requests. The description would benefit from listing concrete actions and including more natural trigger terms.
Suggestions
Add concrete actions the skill performs, e.g., 'Guides implementation through red-green-refactor TDD phases, creates phase-specific git commits, and validates test results at each checkpoint.'
Include more natural trigger terms users would say, such as 'test-driven development', 'red-green-refactor', 'TDD phases', 'task implementation workflow'.
Clarify the 'what' portion by explaining what Conductor is and what outputs the skill produces, rather than assuming the reader knows the terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'implementing tasks', 'handling phase checkpoints', 'managing git commits', and 'understanding the verification protocol' without listing concrete actions. It names domain concepts but doesn't describe what the skill actually does (e.g., no specific actions like 'runs tests', 'creates commits', 'validates phases'). | 1 / 3 |
Completeness | The description has a 'Use when' clause addressing when to use the skill, but the 'what does this do' part is weak — it only vaguely references handling phases, managing commits, and understanding protocols without explaining what concrete outputs or actions the skill produces. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'TDD', 'git commits', 'verification protocol', and 'Conductor' that users might reference. However, 'phase checkpoints' and 'verification protocol' are jargon-heavy, and common variations like 'test-driven development', 'red-green-refactor', or 'task workflow' are missing. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Conductor' and 'TDD workflow' provides some distinctiveness, but 'managing git commits' and 'implementing tasks' are generic enough to overlap with general git or task management skills. The proprietary terms help but aren't sufficient to fully disambiguate. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a comprehensive and highly actionable TDD workflow with clear sequencing and validation checkpoints, which are its strongest qualities. However, it is severely bloated—much of the content explains concepts Claude already understands (git commit types, why tests matter, what TDD is) and could be cut by 50%+ without losing actionable value. The monolithic structure with no external references makes it a poor fit for the progressive disclosure pattern expected of well-structured skills.
Suggestions
Cut explanatory/rationale sections (Why Checkpoints Matter, Performance Considerations, benefits lists) and trust Claude's existing knowledge—aim to reduce content by at least 50%.
Split into multiple files: keep SKILL.md as a concise overview of the 11-step lifecycle, and move Phase Completion Protocol, Quality Assurance Gates, Error Recovery, and Verification Details into separate referenced files.
Remove the Best Practices section entirely—these principles are already embedded in the workflow steps and are redundant.
Consolidate the Git Integration section which repeats commit message format and git notes information already covered in Steps 8-9.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Extensively explains concepts Claude already knows (TDD, git commit message formats, what types like 'feat' and 'fix' mean, why checkpoints matter, what regression testing is). Sections like 'Why Checkpoints Matter', 'Performance Considerations', 'Best Practices' list of 12 items, and 'TDD Variations by Task Type' are largely redundant for Claude. The git notes benefits list and SHA recording rationale are unnecessary padding. | 1 / 3 |
Actionability | Provides fully executable commands (pytest, git, ruff, mypy), concrete code examples (Python tests, bash commands), specific commit message templates, and exact markdown formats for plan.md updates. The 11-step lifecycle and phase completion protocol are copy-paste ready with real commands. | 3 / 3 |
Workflow Clarity | The 11-step TDD lifecycle is clearly sequenced with explicit validation checkpoints (run tests at RED, GREEN, REFACTOR stages; verify coverage at step 6; WAIT for user approval at phase completion). Error recovery paths are defined (failed tests after GREEN, checkpoint rejection, blocked dependencies). Feedback loops are explicit throughout. | 3 / 3 |
Progressive Disclosure | Monolithic wall of text with no bundle files or external references. All content is inline in a single massive file. Sections like Quality Assurance Gates, Verification Checkpoints, TDD Variations, Error Recovery, and Manual Verification Guidance could easily be split into separate referenced files. No progressive disclosure structure exists. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (624 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
895269a
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.