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

31%

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 ./skills/workflow-patterns/SKILL.md

The canonical home for this skill is workflow-patterns in rmyndharis/antigravity-skills

Quality

Content

18%Scale 1-5

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

This skill is essentially a placeholder that defers all meaningful content to a resource file (`resources/implementation-playbook.md`) that is not provided in the bundle. The body contains no concrete guidance about TDD workflow, phase checkpoints, git commits, or verification protocols despite claiming to cover all of these. The instructions are generic meta-advice that could apply to any skill and provide zero domain-specific value.

Suggestions

Add the actual TDD workflow steps (red-green-refactor cycle) with concrete commands and examples directly in the SKILL.md, e.g., specific git commands for commits, how to run tests, what phase checkpoints look like.

Replace the generic instructions ('Clarify goals, constraints, and required inputs') with specific, actionable guidance for each workflow phase, including validation checkpoints and error recovery steps.

Include at least one concrete example of a complete task implementation cycle showing the sequence: write failing test → implement → verify → commit → update plan.md.

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the essential patterns so the skill is self-contained enough to be useful.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections add some bulk without much value. The instructions section is generic filler ('Clarify goals, constraints, and required inputs') rather than skill-specific content. However, it's not excessively verbose—it's short but wastes what space it uses.	3 / 5
Actionability	The instructions are entirely vague and abstract—'Apply relevant best practices and validate outcomes' and 'Provide actionable steps and verification' are meta-instructions with zero concrete guidance. There are no code examples, commands, specific steps, or executable content. Everything meaningful is deferred to a resource file that isn't provided.	1 / 5
Workflow Clarity	Despite the skill being explicitly about TDD workflow, phase checkpoints, git commits, and verification protocols, there is no actual workflow described. No steps are sequenced, no validation checkpoints are defined, and no concrete process is outlined. The entire workflow is presumably in the referenced resource file.	1 / 5
Progressive Disclosure	There is a reference to `resources/implementation-playbook.md` which is appropriate for progressive disclosure, but the SKILL.md itself contains essentially no substantive overview content—it's an empty shell pointing to a file that doesn't exist in the bundle. Good progressive disclosure requires a useful overview with pointers to details, not a vacuous overview that defers everything.	2 / 5
	Total	7 / 20 Passed

Description

44%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.

The description relies heavily on project-specific terminology ('Conductor', 'phase checkpoints', 'verification protocol') without explaining what these mean or what concrete actions the skill performs. While it has a 'Use when' clause, the triggers are abstract and the 'what it does' portion is essentially absent — it lists categories rather than capabilities. The description would benefit from concrete action verbs and clearer explanation of the skill's outputs.

Suggestions

Replace vague verbs ('handling', 'managing', 'understanding') with concrete actions describing what the skill actually does, e.g., 'Guides implementation through red-green-refactor phases, generates phase checkpoint summaries, and creates structured git commit messages'.

Add a brief explanation of what 'Conductor' is and what the TDD workflow entails so Claude can match user requests that don't use the exact term 'Conductor'.

Include natural trigger terms and synonyms users might say, such as 'test-driven development', 'task phases', 'run tests first', 'commit after passing tests', etc.

Dimension	Reasoning	Score
Specificity	Names the domain (TDD workflow, phase checkpoints, git commits, verification protocol) but the actions are generic ('implementing', 'handling', 'managing', 'understanding') rather than concrete. No specific operations are described.	2 / 5
Completeness	Has a 'when' clause ('Use this skill when...') but the 'what' is weak — it lists categories of activity without explaining what the skill actually does or produces. The 'when' triggers are present but vague (e.g., 'implementing tasks according to Conductor's TDD workflow' doesn't clarify what Conductor is or what specific guidance is provided).	3 / 5
Trigger Term Quality	Includes some relevant keywords like 'TDD', 'git commits', 'phase checkpoints', and 'verification protocol', but these are project-specific jargon. Missing natural user phrases like 'test-driven development', 'run tests', 'commit changes', or 'task workflow'.	3 / 5
Distinctiveness Conflict Risk	References 'Conductor' which is a specific tool/system, providing some distinctiveness. However, terms like 'TDD workflow', 'git commits', and 'verification protocol' are broad enough to overlap with general TDD skills, git workflow skills, or testing skills.	3 / 5
	Total	11 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/workflow-patterns/SKILL.md
Commit: 7520423

Reviewed: ~10 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.