CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

to-spec

把当前对话转成 spec 并发布到项目 issue tracker:不做访谈,只综合已经讨论的内容。

Quality

74%

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

Quality

Content

82%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.

This is a well-crafted, instruction-only skill body: tight, non-padded prose, an explicit numbered workflow with a user checkpoint, and a complete copy-paste spec template. The only notable gaps are the absence of a seam example and any post-publication validation step.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout: it never explains concepts Claude already knows (what a spec, user story, or seam is), and every line — the no-interview rule, the seam preferences ('Seams 越少越好,理想数量是一个'), the prototype-snippet exception — adds non-obvious instruction. This matches 'every token earns its place'.

5 / 5

Actionability

Guidance is mostly executable: a concrete 3-step process, a copy-paste spec template with exact section headings, a formatted user-story example, an exact label name (ready-for-agent), and a fallback command (/setup-matt-pocock-skills). Minor gaps keep it below anchor 5: no example of what a valid 'seam' looks like, and the mechanics of publishing to the issue tracker are delegated to the environment without specifics.

4 / 5

Workflow Clarity

The three steps are clearly numbered and sequenced, with an explicit user-confirmation checkpoint before publishing ('与用户确认这些 seams 是否符合预期') and a conditional first step. It falls short of anchor 5 because there is no post-publish validation or error-recovery loop (e.g. what to do if tracker publication fails or the user rejects the seams).

4 / 5

Progressive Disclosure

The body is well organized (intro, 流程 steps, clearly delimited spec-template) with no external bundle files to reference, which is appropriate for a self-contained skill. It misses anchor 5 because at ~70 lines — above the under-50-line simple-skill threshold — the large inline spec template is content that could arguably live in a separate reference file.

4 / 5

Total

17

/

20

Passed

Description

53%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 communicates a clear, concrete purpose (turn the conversation into a spec, publish it to the issue tracker, no interviews) but is missing an explicit 'when to use' clause and broader trigger vocabulary. It is specific enough to distinguish from generic skills, yet its coverage of what the skill actually does is partial.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to turn the current discussion or requirements into a spec / issue' to answer 'when' as well as 'what'.

Include natural trigger synonyms users would say — e.g. 'spec', 'requirements doc', 'write-up', 'ticket' — to broaden trigger-term coverage.

Mention one or two more concrete actions the skill performs (e.g. drafting test seams, applying the ready-for-agent label) to lift specificity beyond two actions.

DimensionReasoningScore

Specificity

The description names its domain and two concrete actions ("把当前对话转成 spec" and "发布到项目 issue tracker"), matching the '1-2 concrete actions, but not comprehensive' anchor. It omits other concrete capabilities of the skill (seam drafting, the ready-for-agent label, the spec template), so it does not reach anchor 4's 'several specific actions with minor gaps'.

3 / 5

Completeness

The 'what' is clear — synthesize the current conversation into a spec and publish it to the issue tracker — but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is above anchor 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

"spec", "对话" (conversation), and "issue tracker" are relevant keywords a user might say, but common variations and synonyms (e.g. "requirements", "write up", "ticket", "RFC") are missing. This sits at 'some relevant keywords but missing common variations', not anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

The niche is well defined — synthesizing already-discussed content into a spec published to an issue tracker, explicitly excluding interviews — making it mostly distinct with only minor overlap risk against other spec- or issue-writing skills. It falls short of anchor 5 because it lacks distinct explicit trigger phrases.

4 / 5

Total

13

/

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

vinvcn/mattpocock-skills-zh-CN

Path

skills/engineering/to-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.