CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

handoff

把当前对话压缩成交接文档,让另一个代理接手。

Quality

75%

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/productivity/handoff/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 an exemplar of token-efficient instruction writing: every line is a concrete, non-obvious directive (temp-dir placement, artifact dedup by reference, secret redaction, argument handling) with no filler. The only gaps are the unspecified structure of the handoff document itself and a missing final verification pass. Strong result overall.

DimensionReasoningScore

Conciseness

The body is six lean lines of pure instruction with zero concept explanation or padding — platform-specific temp-dir details and redaction rules are stated once with no filler — matching the "every token earns its place" anchor.

5 / 5

Actionability

Guidance is mostly executable and concrete ("$TMPDIR,否则 /tmp;Windows 上是 %TEMP%", a named "suggested skills" section invoking the Skill tool, artifact dedup by path/URL, explicit sensitive-info list), but the handoff document's own structure is unspecified and no example or template is given, keeping it below anchor 5.

4 / 5

Workflow Clarity

As a simple single-purpose skill the action (write a handoff doc with the listed properties) is unambiguous with clear directives, but there is no verification step such as re-checking the drafted document for residual sensitive information, so it falls just short of anchor 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no need for external references (none of references/, scripts/, or assets/ exist), and the flat paragraphs each address exactly one concern in a sensible order, which per the simple-skill guideline merits a 5.

5 / 5

Total

18

/

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 states a clear, concrete purpose but provides no explicit trigger guidance, so a user or model has to infer when to invoke it. It is distinct from neighboring skills yet under-sells its coverage. Adding a "Use when..." clause with natural trigger phrases would lift both completeness and trigger term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a handoff, session handoff, context transfer, or wants to continue work in a new session/agent."

Name what the handoff document covers (e.g. current state, key decisions, next steps, suggested skills) to raise specificity from one action to several concrete capabilities.

Include natural synonyms and phrasings users would actually say ("hand off", "take over", "new session", "brief the next agent") to broaden trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — "把当前对话压缩成交接文档" (compress the current conversation into a handoff document) with the outcome "让另一个代理接手" (another agent takes over) — but does not list several specific actions, matching anchor 3 rather than 4.

3 / 5

Completeness

The "what" is clear (compress the conversation into a handoff document for another agent), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; not 2 because the "what" is concrete rather than vague.

3 / 5

Trigger Term Quality

It contains relevant keywords like "对话" (conversation), "交接文档" (handoff document), and "接手" (take over), but misses common variations and natural trigger phrases such as "session", "context transfer", or "continue in a new session", fitting anchor 3.

3 / 5

Distinctiveness Conflict Risk

The agent-handoff niche ("让另一个代理接手") is mostly distinct with only minor overlap risk against conversation-summarization or compaction skills, matching anchor 4 better than anchor 3's generic domain-only phrasing.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

vinvcn/mattpocock-skills-zh-CN

Path

skills/productivity/handoff/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.