CtrlK
BlogDocsLog inGet started
Tessl Logo

implement-spec

Implement a spec from the plans directory

59

Quality

67%

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 ./.opencode/skills/implement-spec/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content is well-structured and highly actionable, with concrete commands, a clear sequenced workflow, explicit feedback loops, and stopping conditions; its main weakness is mild redundancy across the task, before-coding, and autonomous-workflow sections that could be consolidated.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence without explaining known concepts, but the 'Autonomous Workflow' section and 'Commands' block repeat steps 7-9 (test/typecheck/lint), and 'Before Coding' partly restates 'Your Task', so it could be tightened.

2 / 3

Actionability

It provides concrete executable commands ('bun run test', 'bun run typecheck', 'bun run lint:fix'), specific file paths, an explicit directory-structure example, and a named tool (TodoWrite), giving copy-paste-ready guidance.

3 / 3

Workflow Clarity

Steps are clearly sequenced in 'Your Task' and the 'Autonomous Workflow' includes an explicit feedback loop (implement -> test -> fix -> typecheck -> lint -> repeat) with stopping conditions, matching the score-3 anchor for sequenced processes with validation checkpoints.

3 / 3

Progressive Disclosure

No bundle files exist, so this is evaluated as a self-contained skill; the body is well-organized into clearly labeled sections with no nested references, satisfying the well-organized-structure criterion for the top anchor.

3 / 3

Total

11

/

12

Passed

Description

50%

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 accurate and appropriately concise, naming a clear domain and action, but it lacks explicit trigger guidance and lists only a single action, leaving it generic and not clearly distinct from other skills.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when the user asks to implement a feature described in a spec file under .agents/plans/').

List concrete actions to raise specificity (e.g., 'Read a spec, implement the feature, write tests, and run typecheck and lint').

Include natural trigger terms a user would actually say (e.g., 'spec', 'plan', 'implement the plan', 'build the feature from the spec').

DimensionReasoningScore

Specificity

The phrase 'Implement a spec from the plans directory' names the domain (specs/plans) and one concrete action (implement), but does not list multiple specific concrete actions like the score-3 anchor requires.

2 / 3

Completeness

It answers 'what' (implement a spec from the plans directory) but provides no 'Use when...' or equivalent explicit trigger guidance, which per the rubric guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

'spec' and 'plans directory' are relevant keywords but lean toward internal/technical jargon and miss common natural variations a user would actually say; not quite the no-keywords level of 1.

2 / 3

Distinctiveness Conflict Risk

It is somewhat specific (specs in a plans directory) but 'implement a spec' is generic enough that it could overlap with other implementation-related skills and is not a clearly distinct niche.

2 / 3

Total

8

/

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
LibPDF-js/core
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.