CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

implement-spec

Implement a spec from the plans directory

Quality

69%

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

73%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 a well-structured, highly actionable workflow: concrete commands, explicit validation loops, and clear stopping conditions make it easy to follow autonomously. Its main weakness is redundancy — the same test/typecheck/lint cycle is stated three times across overlapping sections — which inflates token cost without adding information.

Suggestions

Collapse "Your Task", "Autonomous Workflow", and "Commands" into one canonical workflow: a single numbered sequence with the exact commands inline, removing the repeated test/fix/typecheck/lint instructions.

Merge "Before Coding" into the task sequence so planning steps appear once instead of duplicating steps 3-5.

DimensionReasoningScore

Conciseness

The body doesn't explain known concepts, but the same instructions recur across sections — run tests/fix failures, typecheck, and lint each appear in "Your Task", "Autonomous Workflow", and "Commands", and "Before Coding" repeats the planning steps — so it could be meaningfully tightened rather than just trimmed.

3 / 5

Actionability

Concrete, executable guidance throughout: exact commands (`bun run test`, `bun run typecheck`, `bun run lint:fix`), project-specific conventions (`#src/*` import alias, `*.test.ts` co-location, `loadFixture()`), and a directory-structure example. Minor gaps: no example of how to locate or choose the spec file, and the only code block is a directory tree.

4 / 5

Workflow Clarity

A numbered 9-step task sequence is reinforced by an explicit implement→test→fix→repeat loop with validation gates (tests pass, typecheck passes, lint passes) and clearly separated stopping conditions for both success and asking for help — matching the feedback-loop-and-checklist anchor.

5 / 5

Progressive Disclosure

With no bundle files, all content appropriately lives inline under well-labeled sections, and the external references it does cite (ARCHITECTURE.md, CODE_STYLE.md) are clearly signaled. It misses a 5 because the body exceeds 50 lines and the duplicated sections could be consolidated.

4 / 5

Total

16

/

20

Passed

Description

48%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 identifies a real, specific task but is a single bare sentence: one action, no scope, and no guidance on when the skill should trigger. It reads as a placeholder rather than a trigger-optimized description, and would rarely be selected over more descriptive siblings.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to implement a spec/plan from .agents/plans/, or mentions a specification or feature plan that needs to be built out."

Enumerate the concrete actions the skill performs: reading the spec, implementing the feature, writing tests, and running typecheck/lint until everything passes.

Include natural synonyms users would say ("specification", "implementation plan", "feature plan") so the skill triggers on varied phrasing.

DimensionReasoningScore

Specificity

"Implement a spec from the plans directory" names a single concrete action and its location, comparable to the minimal "Processes PDF files" anchor; it never enumerates what implementation involves (writing code, tests, typecheck, lint), so it falls below the 1-2-comprehensive-actions anchor.

2 / 5

Completeness

The description gives a clear 'what' (implement a spec) but has no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"spec" and "plans directory" are terms a user would plausibly say, but common variations like "specification", "implementation plan", or "feature plan" are missing, matching the some-keywords-but-missing-synonyms anchor.

3 / 5

Distinctiveness Conflict Risk

The reference to a dedicated plans directory carves out a fairly distinct niche with only minor overlap risk against generic coding/implementation skills, though it lacks the explicit distinct triggers of a 5.

4 / 5

Total

12

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

LibPDF-js/core

Path

.opencode/skills/implement-spec/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.