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

65%

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

Quality

Content

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

The body is concise and lightly organized but lacks concrete, executable guidance and a sequenced workflow despite describing a multi-step TDD/verification process. The single referenced resource file is also missing from the bundle.

Suggestions

Replace abstract instructions with concrete steps: spell out the TDD red-green-refactor cycle and the verification protocol as numbered, executable actions with example git commands.

Add explicit validation checkpoints (e.g., 'run tests; if failing, fix and re-run before committing') so the workflow meets the destructive/batch validation requirement.

Provide the referenced resources/implementation-playbook.md (or remove/correct the reference) so the signaled one-level-deep reference resolves to a real file.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly lean with little over-explanation, but generic instructions like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices and validate outcomes' add modest padding that could be tightened.	4 / 5
Actionability	Guidance is high-level and abstract ('Clarify goals', 'Apply relevant best practices', 'Provide actionable steps and verification') with no concrete commands, code, or specific TDD/git steps to execute — only a pointer to an external playbook.	2 / 5
Workflow Clarity	No sequenced workflow is present; the TDD red-green-refactor cycle and verification protocol are named but not laid out as ordered steps, and validation checkpoints are referenced only vaguely ('validate outcomes').	2 / 5
Progressive Disclosure	Structure exists (Use/Do-not-use/Instructions/Resources sections) and one reference is signaled ('resources/implementation-playbook.md'), but that referenced file does not exist in the bundle, and no other detail files are provided, leaving organization incomplete.	3 / 5
	Total	11 / 20 Passed

Description

83%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, well-structured description with an explicit 'Use when...' trigger and a clear, domain-specific capability list. It is concise and distinct from generic skills, with only minor room to add synonyms and sharper action verbs.

Dimension	Reasoning	Score
Specificity	Names the domain (Conductor's TDD workflow) and several concrete actions ('implementing tasks', 'handling phase checkpoints', 'managing git commits', 'understanding the verification protocol'), but they are framed as situations rather than crisp action verbs, leaving minor gaps.	4 / 5
Completeness	Explicitly answers both 'what' (implementing tasks per Conductor's TDD workflow, phase checkpoints, git commits, verification protocol) and 'when' via the explicit 'Use this skill when...' clause with concrete triggers.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('TDD', 'phase checkpoints', 'git commits', 'verification protocol') with good coverage, though it lacks synonyms or extension-style variants and is narrowly scoped to one proprietary workflow.	4 / 5
Distinctiveness Conflict Risk	Tied to the distinctive Conductor/TDD niche with specific triggers, making it largely distinguishable; minor overlap risk with generic TDD or git-commit skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/workflow-patterns/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.