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.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/conductor/skills/workflow-patterns/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured overview with excellent progressive disclosure to a real one-level reference, but the SKILL.md body delegates nearly all executable detail and the sequenced workflow to that reference, leaving the body itself light on actionability and in-body workflow sequencing.

Suggestions

Inline 2-3 executable commands or a compact code snippet (e.g. the commit-message format or the git-notes command) so the body is actionable without requiring the reference for the common cases.

Add a brief in-body outline of the core TDD lifecycle sequence (RED -> GREEN -> REFACTOR -> coverage check -> commit -> checkpoint) with the explicit 'wait for approval' checkpoint, rather than deferring the entire workflow to details.md.

Trim the best-practices list to the non-obvious items to reduce overlap with the 'When to Use' list and remove principles Claude already knows.

Dimension	Reasoning	Score
Conciseness	The ~40-line body is lean and assumes Claude's familiarity with TDD, but the 12-item best-practices list overlaps somewhat with the 'When to Use' list and restates principles Claude already knows (e.g. 'Never skip RED', 'Small commits'), leaving minor trimmable padding.	4 / 5
Actionability	The body offers high-level directives ('Never skip RED', 'One logical change per commit') with no executable commands or code; all concrete, runnable guidance is delegated to references/details.md rather than shown inline.	3 / 5
Workflow Clarity	The body itself only lists scenarios and principles without sequencing the multi-step TDD workflow; the explicit sequenced steps with validation checkpoints live entirely in the referenced details.md, so the in-body sequence and checkpoints are only implicit.	3 / 5
Progressive Disclosure	A clean overview with well-organized sections and a single clearly-signaled one-level-deep reference (references/details.md, verified to exist) with an explicit read-condition, matching the ideal clear-overview anchor.	5 / 5
	Total	15 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states both capabilities and an explicit trigger clause tied to a distinctive named workflow. Slight room to sharpen the action verbs and add synonym variants for trigger terms.

Dimension	Reasoning	Score
Specificity	Lists several specific actions ('implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, understanding the verification protocol'), but the gerunds are workflow-stage abstractions rather than concrete verbs, leaving minor coverage gaps versus a comprehensive 5.	4 / 5
Completeness	Explicitly answers both what (TDD task implementation, checkpoints, git commits, verification) and when via a clear 'Use this skill when...' trigger clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural domain terms a user would say ('TDD workflow', 'phase checkpoints', 'git commits', 'verification protocol') with good coverage, but lacks common synonyms or file-extension-style variants that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The 'Conductor's TDD workflow' framing carves a clear niche with distinct, named triggers and minimal overlap risk with unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: wshobson/agents
Path: plugins/conductor/skills/workflow-patterns/SKILL.md
Commit: d6837ae

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

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.