continue-implementation

Continue implementing a spec from a previous session

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/continue-implementation/SKILL.md

Quality

Content

100%

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 strong, lean instruction skill: concrete commands, a clear iterative workflow with validation, and explicit stopping conditions, all well-organized into focused sections. It assumes Claude's intelligence and adds only project-specific guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive, assuming Claude's competence with no concept explanations or padding; every section earns its place (e.g. "Follow CODE_STYLE.md strictly", concrete command blocks).	3 / 3
Actionability	It provides fully executable commands (`bun run test:run`, `bun run typecheck`, `bun run lint:fix`) and specific file references (`ARCHITECTURE.md`, `CODE_STYLE.md`, `#src/*`, `fixtures/`), making the guidance copy-paste ready.	3 / 3
Workflow Clarity	A clear sequenced workflow (implement -> test -> fix -> typecheck -> lint -> repeat) with explicit validation checkpoints and well-defined stop conditions for both success and help-seeking.	3 / 3
Progressive Disclosure	The skill is a single well-organized file with clear sections and no need for external references; per the simple-skills note, well-organized single-file content scores 3.	3 / 3
	Total	12 / 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 clear and grammatical but thin: it states the action without concrete capability breadth or an explicit trigger clause. It conveys the niche but would benefit from a "Use when..." statement and richer trigger terms.

Suggestions

Add an explicit trigger clause, e.g. "Use when resuming an implementation started in a prior session or when the user asks to continue a spec."

Broaden trigger terms to natural phrasings users would say, such as "resume work", "continue feature", or "pick up where you left off".

Name the concrete actions involved (e.g. "Assess current state, implement remaining spec work, and run tests") to raise specificity.

Dimension	Reasoning	Score
Specificity	Names a concrete action ("Continue implementing") and a domain ("spec"), but does not enumerate multiple specific capabilities, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	The description states what the skill does but omits any "Use when..." trigger clause; per the guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	"spec" and "previous session" are relevant terms, but coverage is narrow and lacks common variations like "resume work" or "continue feature," fitting the 'some relevant keywords but missing variations' anchor.	2 / 3
Distinctiveness Conflict Risk	"Continue implementing a spec from a previous session" carves out a resume niche but could still overlap with general implementation skills, matching the 'somewhat specific but could overlap' anchor.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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/continue-implementation/SKILL.md
Commit: 36bf165

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.