CtrlK
BlogDocsLog inGet started
Tessl Logo

implement

Create an implementation based on a plan.

41

Quality

40%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/implement/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%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 token-efficient but underspecified: it offers one concrete instruction (test with pytest) amid vague direction, with no clear workflow, validation steps, or executable examples.

Suggestions

Replace vague directives with concrete steps, e.g. specify how to map plan sections to implementation files and how to run pytest.

Add a validation checkpoint such as 'After implementing, run pytest and confirm all tests pass before finishing.'

Fix the grammatical error 'must add follow the plan' and clarify what 'read research' refers to (a path or artifact).

DimensionReasoningScore

Conciseness

The body is extremely lean (a heading and two bullets), assumes Claude's competence, and contains no padding or over-explanation of known concepts; every token earns its place.

5 / 5

Actionability

Beyond 'Make a test for every section in your implementation using pytest', the guidance ('make an implementation', 'follow the plan', 'read research') is high-level hints with no concrete steps or examples, fitting the 'minimal concrete guidance' anchor.

2 / 5

Workflow Clarity

A rough sequence is implied (implement then test) but steps are poorly defined, there is a grammatical error ('must add follow the plan'), and no validation checkpoints exist for verifying the implementation against the plan.

2 / 5

Progressive Disclosure

This is a simple under-50-line skill with no need for external references; the single heading and bullets are reasonably organized and no bundle files are referenced, so it mostly meets the simple-skill exception, though the structure is minimal.

4 / 5

Total

13

/

20

Passed

Description

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

The description is a single vague sentence that names the domain without concrete actions, trigger phrases, or a use-when clause, making it nearly indistinguishable from generic coding skills.

Suggestions

Add concrete actions, e.g. 'Implement a planned feature by writing code, tests, and validating behavior against the plan.'

Add an explicit trigger clause such as 'Use when turning an approved plan into working code.'

Include natural trigger terms users would say (e.g. 'implement the plan', 'code this up', 'build from the plan').

DimensionReasoningScore

Specificity

The phrase 'Create an implementation based on a plan' names the domain (implementation) but the action is minimal and generic; it does not state what is implemented, in what language, or what 'based on a plan' concretely entails.

2 / 5

Completeness

It gives a vague 'what' ('Create an implementation') and no 'when' clause at all; the missing 'Use when...' guidance and the vague what fit the 'vague what and no when' anchor rather than the cap-at-3 clear-what case.

2 / 5

Trigger Term Quality

Only two generic keywords ('implementation', 'plan') appear; no natural trigger phrases users say, no synonyms, and no file extensions, matching the 'one or two generic keywords' anchor.

2 / 5

Distinctiveness Conflict Risk

'Create an implementation based on a plan' is very broad and overlaps heavily with general coding skills; the 'based on a plan' qualifier narrows it slightly but conflict risk remains high.

2 / 5

Total

8

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
pymc-labs/pymc-marketing
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.