CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

implement

Use when the user asks to execute an existing task plan's Solution under TDD — RED → GREEN → REFACTOR → CHECK per AGENTS.md. Requires a written plan under the `tasks` role. Do NOT trigger on planning, review, or unrelated failing tests.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A rigorous, highly actionable TDD workflow with explicit checkpoints, failure classification, and a closing checklist — genuinely non-obvious procedural guidance rather than padding. Its weaknesses are presentation-level: a malformed final step heading, triple restatement of core rules across sections, and a long inlined baseline-record procedure that would suit a reference file.

Suggestions

Fix the malformed step 6 heading and body ('6. **6. **TOTAL STOP**' with the entire step wrapped in stray bold markers) — the duplicated number and broken bold break markdown rendering of the final narrate-upward instruction.

Consolidate rules stated three times across the Rules, Instructions, and Verification sections (never edit tests to pass, no lint/format suppression, second-fix-failure STOP) — state each once authoritatively and reference it from the checklist to cut tokens.

Move the lengthy baseline-record procedure (step 2) and the 'looking at the code without your change' guidance into a one-level-deep reference file to slim the main SKILL.md body.

DimensionReasoningScore

Conciseness

The body is dense and operative throughout — manifest-detection priorities, fail-fast flag names, git worktree commands — with no padding and no explanation of concepts Claude already knows (it never explains what TDD is). It sits at anchor 4 rather than 5 because core rules are restated across the Rules, Instructions, and Verification sections and several sentences (e.g., the baseline-record environment bullets) are over-long compounds that could be tightened.

4 / 5

Actionability

Guidance is largely executable: a concrete check-command priority chain ('deno.json → deno task check', 'package.json → npm run check/test/lint'), copy-ready commands ('git worktree add <scratch-dir> HEAD', 'git show HEAD:<path>'), and named suppression tokens to avoid. It falls short of anchor 5 due to minor gaps: the STOP-ANALYSIS REPORT format is referenced but never specified, the baseline record's scratch location/format is left vague, and step 6's heading is malformed ('**6. **TOTAL STOP**'), obscuring the final instruction.

4 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced with explicit validation checkpoints and feedback loops: RED must fail for the right reason, CHECK must pass or failures are classified against the baseline record, a second failed fix triggers a STOP-ANALYSIS REPORT, and a final verification checklist plus full-suite re-run close the loop. This matches anchor 5 (clear sequence, explicit validation, error-recovery loops, checklist); anchor 4 would require missing checkpoints, which are not missing.

5 / 5

Progressive Disclosure

A single well-organized SKILL.md (~96 lines) with clear sections (Overview, Context, Rules, Instructions, Verification) and no external bundle files to navigate. It fits anchor 4 rather than 5 because the >50-line body inlines a substantial sub-procedure (the ~15-line baseline-record mechanism and the 'look at code without your change' guidance) that could live in a one-level-deep reference file, and the only pointer (AGENTS.md) is external to the skill.

4 / 5

Total

17

/

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 with an explicit 'Use when' clause, concrete prerequisite (a written plan under the `tasks` role), named TDD phases, and explicit negative triggers that sharply delimit it from planning and review skills. The only gap is slight synonym coverage for natural user phrasings like 'implement the plan'.

DimensionReasoningScore

Specificity

The description names a concrete action set — 'execute an existing task plan's Solution under TDD — RED → GREEN → REFACTOR → CHECK per AGENTS.md' — which enumerates the four cycle phases as specific actions. It stops short of anchor 5 because it does not enumerate the underlying actions (write failing test, minimal code, refactor) and 'execute a plan's Solution' remains somewhat abstract; it clears anchor 3 because multiple concrete phase-level actions are explicitly listed.

4 / 5

Completeness

It explicitly answers both questions: 'Use when the user asks to execute an existing task plan's Solution under TDD' (when, with a concrete trigger phrase and prerequisites — 'Requires a written plan under the `tasks` role') and the what (execute the Solution under the RED → GREEN → REFACTOR → CHECK cycle). Explicit negative triggers ('Do NOT trigger on planning, review, or unrelated failing tests') further delimit the when, matching anchor 5; anchor 4 would apply only if the when were vague, which it is not.

5 / 5

Trigger Term Quality

Natural trigger terms are present: 'execute', 'task plan', 'Solution', 'TDD', plus negative triggers 'planning, review, or unrelated failing tests' that sharpen matching. A few natural phrasings users would say are missing (e.g., 'implement the plan', 'build/finish the tasks'), so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — implementing an already-written plan under TDD — with both positive triggers and explicit exclusions ('Do NOT trigger on planning, review, or unrelated failing tests') that separate it from sibling planning/review skills. Conflict risk is minimal, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

korchasa/flowai-plugins

Path

plugins/flowai/skills/implement/SKILL.md

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.