CtrlK
BlogDocsLog inGet started
Tessl Logo

handoff

将当前对话压缩为交接文档(handoff document / session handoff brief),供下一个 agent 接续工作。手动调用 /handoff。

60

Quality

70%

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/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.

A tight, well-organized instruction-only skill that respects token budget and gives concrete guidance with a clear decision checkpoint. Minor gains are possible by providing fillable section templates and an explicit validation step.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no concept over-explanation; every line (output path, six-section structure, rules) earns its place and assumes Claude's competence.

5 / 5

Actionability

Gives a concrete output path template and a concrete six-section document structure plus actionable rules, but the section items are descriptive rather than filled-in templates and there is no executable code/command, leaving minor gaps.

4 / 5

Workflow Clarity

Single-purpose skill with a clear sequence (output location, document structure, rules) and an explicit decision checkpoint for very short conversations; not a 5 because there is no explicit validate/retry feedback loop.

4 / 5

Progressive Disclosure

A simple skill under 50 lines with no need for external references, organized into well-signaled sections (输出位置, 文档结构, 规则), meeting the simple-skill exception for a top score.

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 clearly conveys the skill's purpose and trigger but is held back by a missing explicit 'Use when...' clause and limited synonym/trigger-term coverage. It is distinct and specific enough to avoid most conflicts.

Suggestions

Add an explicit 'Use when...' clause naming the situations that call for a handoff (e.g., long sessions ending, handing off to a fresh agent, context about to be lost).

Broaden trigger-term coverage with synonyms users might actually say (e.g., 'context handoff', 'session summary', 'hand off work', '交接', '续接').

List 1-2 more concrete actions beyond 'compress/summarize' (e.g., redact secrets, cross-reference existing artifacts) to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ('压缩为交接文档') and one concrete action but does not enumerate several specific actions, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Has a clear 'what' (compress conversation into a handoff brief for the next agent) but 'when' is only weakly implied via '手动调用 /handoff' with no explicit 'Use when...' trigger clause, which caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms ('交接文档', 'handoff document', 'session handoff brief') and the '/handoff' trigger, but synonym and variation coverage is limited.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear, specific niche (handoff documents for a successor agent) with a distinct trigger, leaving only minor overlap risk with adjacent skills.

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.

Validation15 / 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
feiskyer/claude-code-settings
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.