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.

68

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 tightly engineered procedural skill with excellent workflow sequencing, explicit validation checkpoints, and highly concrete commands. Its main costs are triple-stated constraints across Rules, Instructions, and Verification, and a malformed markdown header on step 6.

Suggestions

Consolidate the duplicated constraints: Rules 2-6 restate material already embedded in Instructions step 3 and the Verification checklist — state each rule once in the procedural step and keep only the checklist summary.

Fix the broken step 6 header ('6. **6. **TOTAL STOP**' with nested bold markers and doubled numbering) so the final reporting step renders correctly.

Trim rule 9's decision-gate explanation to its trigger condition and required action; the enumerated examples of above-class/method decisions could be shortened without losing the gate's force.

DimensionReasoningScore

Conciseness

The Overview re-explains the RED/GREEN/REFACTOR/CHECK cycle and Rules 2-6 largely restate what Instructions step 3 and the Verification checklist already specify, creating three passes over the same constraints. Mostly efficient and free of concept-padding, but the duplication could be tightened.

3 / 5

Actionability

Provides fully executable guidance: a concrete check-command detection priority with literal commands (deno task check, npm run check, make check, pytest/ruff check, go vet), explicit stop conditions, no-op handling, and a specified final-report structure. As an instruction-only skill, the guidance is copy-paste actionable.

5 / 5

Workflow Clarity

The TDD loop is clearly sequenced with explicit validation gates (test MUST fail at RED, check MUST exit 0), feedback loops for error recovery (re-run after refactor, STOP-ANALYSIS REPORT on second fix failure), and a closing verification checklist. The malformed step 6 header ('6. **6. **TOTAL STOP**') is a cosmetic defect that does not obscure the sequence.

5 / 5

Progressive Disclosure

No bundle files exist; the skill is a self-contained single file with clear sections (Overview, Context, Rules, Instructions, Verification) and easy navigation. At ~86 lines with long inline rules (e.g. rule 9's decision gate), it exceeds the simple-skill threshold where organization alone would merit a 5.

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 trigger description: it states explicit when-conditions, the concrete TDD-based what, and negative triggers that prevent misfires on planning or review requests. Only minor gains available from spelling out the cycle phases or adding synonymous user phrasings.

DimensionReasoningScore

Specificity

'execute an existing task plan's Solution under TDD — RED → GREEN → REFACTOR → CHECK per AGENTS.md' names the domain and concrete actions, but the phases are named rather than described. Fits 'several specific actions; minor gaps' better than the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both questions: 'Use when the user asks to execute an existing task plan's Solution under TDD' gives the when, and the RED→GREEN→REFACTOR→CHECK cycle with the tasks-role requirement gives the what, with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Natural trigger terms are present ('execute', 'task plan', 'Solution', 'TDD') plus negative triggers, but common user phrasings like 'implement the plan' or 'make the tests pass' are absent — good coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (implement phase of a plan lifecycle) with explicit carve-outs — 'Do NOT trigger on planning, review, or unrelated failing tests' — that separate it from adjacent planning/review skills, giving minimal conflict risk.

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.