implement

基于 spec 或 ticket 集合实现一段工作。

Quality

61%

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 ./skills/engineering/implement/SKILL.md

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 lean and lays out a sensible implementation workflow ending in review and commit. The main gaps are incomplete actionability (no concrete commands/details) and missing explicit test-failure feedback loops.

Suggestions

Add concrete commands or examples for the periodic checks, e.g. the typecheck command and how to run a single test file, so guidance is copy-paste ready.

Insert an explicit validation feedback loop, e.g. 'If typechecking or tests fail, fix and re-run before proceeding.'

Clarify what '预先约定好的 seams' means or how to identify them, since that term is ambiguous without project context.

Dimension	Reasoning	Score
Conciseness	The body is five short directive sentences with no padding and no explanation of concepts Claude already knows; every token earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.	3 / 3
Actionability	It points to concrete commands/activities (`/tdd`, `/code-review`, typechecking, single test file, full suite, commit to branch), but these are not copy-paste executable and omit key details such as which test file or typecheck command, fitting the 'some concrete guidance but incomplete' anchor.	2 / 3
Workflow Clarity	There is a clear sequence (implement -> /tdd on seams -> periodic typecheck/tests -> full suite -> /code-review -> commit) with an end checkpoint, but no explicit validation feedback loop ('if tests fail, fix and re-run'), matching the 'steps listed but validation gaps' anchor.	2 / 3
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is organized as a clear linear sequence of steps; per the simple-skill guidance this warrants a 3 without separate sections or file references.	3 / 3
	Total	10 / 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 concise and third-person, clearly stating the skill implements work described in specs or tickets. Its main weakness is the absence of an explicit 'Use when' trigger clause and limited trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when implementing work described in a spec or a set of tickets/issues.'

Broaden trigger terms to include natural user phrasings like 'spec', 'tickets', 'issues', 'requirements', 'implement the work', 'build from spec'.

List a couple more concrete actions (e.g. 'write code, run tests, and commit') to lift specificity from a single action to multiple specific actions.

Dimension	Reasoning	Score
Specificity	The description names the domain (spec/ticket) and a single action ("实现一段工作"), matching the 'names domain and some actions, but not comprehensive' anchor; it does not list multiple specific concrete actions that would warrant a 3.	2 / 3
Completeness	It states what the skill does (implement work from a spec or ticket collection) but provides no 'when/Use when' trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'spec', 'ticket', and '实现工作' are relevant and reasonably natural, but coverage is thin and missing common variations, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Tying implementation to spec/ticket input is somewhat specific, but the phrasing is general enough that it could overlap with other general implementation or coding skills, matching the 'somewhat specific but could still 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: vinvcn/mattpocock-skills-zh-CN
Path: skills/engineering/implement/SKILL.md
Commit: f2b2464

Reviewed: 1 day 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.