CtrlK
BlogDocsLog inGet started
Tessl Logo

handoff

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

65

Quality

78%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean, well-structured, and actionable, providing a clear output location, an explicit document structure, and concrete rules that assume Claude's competence without redundant explanation — a strong, well-scoped simple skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it states the output path, a 6-section structure, and terse rules without explaining what a handoff is or why it matters, so every token earns its place.

3 / 3

Actionability

Concrete, specific guidance throughout: a named output path pattern, a numbered 6-section document structure, and actionable rules (redact API keys, reference existing artifacts by path/URL, treat args as focus direction, skip if <3 rounds); per the scoring notes, code absence is not penalized for an instruction-only skill when guidance is this actionable.

3 / 3

Workflow Clarity

This is a simple single-output skill (write doc → save to path → tell user the path), and per the simple-skills note workflow clarity can score 3 when the single action is unambiguous; the short-conversation branch is stated explicitly and no destructive/batch feedback loop is required.

3 / 3

Progressive Disclosure

Under 50 lines, single-task, no external references needed, and organized into clear sections (输出位置 / 文档结构 / 规则), so per the simple-skills note progressive disclosure scores 3 on well-organized sections alone.

3 / 3

Total

12

/

12

Passed

Description

57%

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 is distinct and non-conflicting, but it enumerates only a single action and lacks an explicit 'Use when…' trigger clause, which caps both completeness and specificity below the top level.

Suggestions

Add a 'Use when…' / '使用场景' clause stating when Claude (or the user) should invoke this skill, e.g. 'Use when wrapping up a session and handing off context to a fresh agent.'

Enumerate multiple concrete actions the skill performs (e.g. summarize completed work, capture blockers, list next steps) to lift specificity to the top anchor.

Broaden trigger-term coverage with natural synonyms users say ('context handoff', 'session summary', 'pick up where I left off') in addition to 'handoff document'.

DimensionReasoningScore

Specificity

Names the domain (handoff/session handoff brief) and a concrete action ('将当前对话压缩为交接文档' / '供下一个 agent 接续工作'), but lists only one core action rather than multiple specific concrete actions, matching the 'domain and some actions' anchor rather than the enumerated-actions anchor.

2 / 3

Completeness

It clearly answers 'what' (compress conversation into a handoff doc for the next agent) but 'when' guidance is only the invocation hint '手动调用 /handoff' with no 'Use when…' clause describing triggering situations, so per the rubric's explicit rule a missing 'Use when…' caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural user-facing terms ('交接文档', 'handoff document', 'session handoff brief', '/handoff'), but coverage is narrow — it omits common variations like 'context handoff', 'session summary', or 'pick up where I left off', so it lands at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

It occupies a clear narrow niche (generating a session handoff brief) with a distinct trigger (/handoff), making it unlikely to fire for unrelated skills — matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

9

/

12

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.