CtrlK
BlogDocsLog inGet started
Tessl Logo

implement

Create an implementation based on a plan.

44

Quality

44%

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

72%

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

The body is admirably concise and appropriately minimal for a simple skill, but its guidance is vague and lacks executable detail or a clearly sequenced workflow with explicit verification checkpoints. A typo ('You must add follow the plan') also slightly undermines clarity.

Suggestions

Replace vague direction with concrete steps, e.g. '1. Read the plan file end-to-end. 2. Implement each section in order. 3. For each section, add a pytest test and run `pytest -q` before moving on.'

Fix the typo 'You must add follow the plan' to 'Follow the plan'.

Add an explicit validation loop: run the test suite after each section and only proceed once tests pass.

DimensionReasoningScore

Conciseness

The body is extremely lean (a heading and two short bullets) with no padding or explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

It gives some concrete guidance ('Make a test for every section... using pytest') but the rest is vague ('follow the plan', 'read research if you have questions') with no executable code, commands, or examples, fitting the incomplete-guidance anchor.

2 / 3

Workflow Clarity

Steps are present as a loose bullet list (follow plan -> read research if needed -> test each section) but the sequence is not tightly ordered and validation checkpoints are only implicit, matching the 'listed but checkpoints missing or implicit' anchor.

2 / 3

Progressive Disclosure

This is a simple, single-purpose skill well under 50 lines with no need for external references, and it is reasonably organized with a heading and bulleted guidance, so per the simple-skill note it qualifies for a 3.

3 / 3

Total

10

/

12

Passed

Description

17%

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 too vague to effectively route invocation: it names one generic action, lacks any 'Use when...' trigger, and would overlap heavily with other implementation skills. It also uses imperative second-person voice rather than third person.

Suggestions

Rewrite in third person and list concrete actions, e.g. 'Implements a planned feature: writes code per the plan, consults linked research, and adds pytest tests for each section.'

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

Include natural trigger terms users would say ('implement the plan', 'build from the plan', 'write the implementation') to improve routing and distinctiveness.

DimensionReasoningScore

Specificity

The description 'Create an implementation based on a plan' names only a single generic action ('create an implementation') with no concrete sub-actions, matching the vague/abstract anchor; additionally it uses imperative second-person voice ('Create'), which per the guidelines reduces specificity by one.

1 / 3

Completeness

It states a weak 'what' (create an implementation) but provides no 'when'/trigger guidance at all, so per the missing-'Use when...' rule completeness is capped at 2.

2 / 3

Trigger Term Quality

The only terms are 'implementation' and 'plan', which are overly generic and not natural keywords a user would say to invoke this specific skill; there are no common variations or trigger phrases.

1 / 3

Distinctiveness Conflict Risk

The phrasing is extremely generic and would conflict with many code/implementation skills, offering no niche or distinct triggers to disambiguate.

1 / 3

Total

5

/

12

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.