CtrlK
BlogDocsLog inGet started
Tessl Logo

claude-handoff

把当前对话交接给一个全新的 background agent,让它立即接手工作。

60

Quality

71%

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/in-progress/claude-handoff/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

90%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 lean, actionable, and gives a fully specified command with concrete guidance on summary contents. It loses a little on workflow clarity and structure due to the absence of explicit step sequencing and section headers.

Suggestions

Add a short numbered sequence (write summary → strip sensitive info → launch agent) to make the workflow explicit.

Use section headers (e.g., '## Summary contents', '## Launching') to organize the sub-instructions for easier scanning.

Add a brief verification note that the launched agent appears in `claude agents` so the user can confirm the handoff succeeded.

DimensionReasoningScore

Conciseness

Lean body with a single copy-paste command and only task-relevant detail (e.g., where --name surfaces); assumes Claude's competence with no padding or explanation of known concepts.

5 / 5

Actionability

Provides the exact executable command `claude --bg --name "<descriptive name>" "<handoff summary>"` plus a concrete example name and specific instructions on what the summary must contain.

5 / 5

Workflow Clarity

The single action (write summary, launch background agent) is unambiguous with sensible safeguards (strip sensitive info, reference artifacts by path), but steps are not explicitly sequenced and there is no validation checkpoint; not 5 due to missing explicit ordering.

4 / 5

Progressive Disclosure

Content is short and appropriately inline with no need for external references, but lacks section headers to organize the distinct sub-instructions; not 5 because the 'well-organized sections' expected for a top score are absent.

4 / 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 states what the skill does but omits any 'Use when...' trigger guidance, capping completeness and trigger quality. It is reasonably distinct as a handoff utility but would benefit from explicit usage triggers.

Suggestions

Add a 'Use when...' clause stating when to invoke this skill (e.g., 'Use when ending a session that needs to continue in a background agent').

Include natural trigger terms users would actually say, such as 'handoff', 'continue work', or 'hand over the session'.

Mention 1-2 more concrete capabilities (e.g., summarizing state, preserving context) to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('交接给一个全新的 background agent') and one concrete action ('立即接手工作'), matching the anchor for 1-2 concrete actions without comprehensive coverage; not 4 because only a single action is described.

3 / 5

Completeness

Provides a clear 'what' (hand off conversation to a new background agent) but no 'when' / 'Use when...' clause; per guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords like '交接' (handoff) and 'background agent' but lacks natural trigger phrases or synonyms a user would say; missing common variations keeps it at 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

Conversation handoff to a background agent is a distinct niche with minimal overlap risk; not 5 because the thin single-sentence description leaves minor overlap with general agent-management 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
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.