CtrlK
BlogDocsLog inGet started
Tessl Logo

implement

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

51

Quality

55%

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

Quality

Content

86%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 lean, actionable workflow that leverages existing slash-commands and gives a clear sequenced process with periodic validation. Its main weakness is the absence of explicit failure-handling feedback loops and concrete command strings for the typechecking/test steps.

DimensionReasoningScore

Conciseness

The body is lean and imperative with zero padding or explanation of concepts Claude already knows; every line earns its place. Matches the score-5 anchor for lean, efficient content that assumes Claude's competence.

5 / 5

Actionability

Concrete executable guidance is present via specific slash-commands ("/tdd", "/code-review") and concrete actions (run typechecking, run a single test file, run the full suite, commit to the branch). Below 5 because there are no copy-paste-ready commands/code for the typechecking and test invocations, leaving minor gaps.

4 / 5

Workflow Clarity

A clear sequence is given (implement via TDD on seams, periodic typechecking/tests, full suite at end, code-review, commit) with validation checkpoints via "定期运行 typechecking" and running tests. Below 5 because explicit feedback loops (if checks fail, fix and retry) are not stated.

4 / 5

Progressive Disclosure

This is a short single-purpose skill (~5 lines) with no need for external references, so well-organized concise content earns a 5 per the simple-skill guideline. The content is appropriately self-contained with no nested or buried references.

5 / 5

Total

18

/

20

Passed

Description

25%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 is too vague to function as effective trigger guidance: it states a generic action with no concrete capabilities and no explicit "when to use" clause. It risks overlapping with many development skills.

Suggestions

Add a concrete list of capabilities (e.g., write code from a spec, break tickets into tasks, implement features) instead of the generic "implement a piece of work".

Add an explicit "Use when..." trigger clause naming natural phrases users say (e.g., "Use when the user provides a spec or tickets and asks to implement the described work").

Include common synonyms/variants of trigger terms (spec, specification, ticket, task, issue) to improve natural keyword coverage.

DimensionReasoningScore

Specificity

The phrase "实现一段工作" (implement a piece of work) names the domain (spec/ticket) but the action is fully generic with no concrete actions listed. It is below the midpoint because no specific capability is described, but above 1 since a domain is named.

2 / 5

Completeness

It offers only a vague "what" (implement work from spec/ticket) and no "when"/"Use when..." trigger guidance, matching the anchor for a vague what with no when. Per guidelines the missing trigger clause caps completeness, and it does not reach 3.

2 / 5

Trigger Term Quality

Only "spec" and "ticket" appear as keywords; these are relevant but minimal and lack common variations/synonyms users would naturally say. Below 3 because coverage is thin and generic.

2 / 5

Distinctiveness Conflict Risk

"Implement work from spec/ticket" is very broad and would overlap with many general development skills. Below 3 because the overlap risk is high, above 1 because spec/ticket narrow it slightly.

2 / 5

Total

8

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
vinvcn/mattpocock-skills-zh-CN
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.