CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hand-off

Get work done that needs another person's own logins, files or memory. Decide whether to just do it yourself, and if not, ask that person by DM with the full request.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary lean, single-purpose instruction skill: an executable command, an explicit decision gate, a validation checkpoint on the outbound action with failure handling, and zero padding. All guidance is concrete and every token earns its place.

DimensionReasoningScore

Conciseness

Every line is load-bearing: the curl command, the DM content rules ('Start the DM with the source channel name and a permalink to the originating thread'), and the reporting constraints ('Say you messaged someone only after reach returns ok: true'). There is no padding and no explanation of concepts Claude already knows, matching the lean-and-efficient anchor; even the one explanatory line ('They haven't seen this conversation') is non-obvious and earns its place.

5 / 5

Actionability

The body provides a copy-paste-ready, complete curl command with environment variables and clearly marked fill-in placeholders, plus concrete rules for DM content and for post-send reporting including the failure path ('If it failed or matched the wrong person, say that instead'). This matches the fully-executable anchor rather than anchor 4, which anticipates minor gaps in the commands or coverage.

5 / 5

Workflow Clarity

Clear three-phase sequence — decide (posture gate: 'Open posture... do the work yourself'; 'Isolated: hand off only when...'), DM (executable command), then report — with an explicit validation checkpoint ('only after reach returns ok: true') and error-recovery guidance for failed or wrong-recipient matches. The single DM is not a destructive or batch operation, and the validation and failure handling present match the explicit-checkpoints-with-feedback anchor; anchor 4 would require missing checkpoints, which is not the case.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external reference files (none exist in the bundle), and is organized into clear sections ('First, can you do it yourself?', 'Ask them by DM', 'Then') that each carry one level of the workflow. The single cross-reference to the sibling request-access skill is clearly signaled and appropriate. Per the scoring note, an under-50-line skill with no need for external references scores 5 with well-organized sections.

5 / 5

Total

20

/

20

Passed

Description

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

A concise, third-person description of a narrow, well-defined capability with concrete actions and a clear qualifying condition. Its main weaknesses are the absence of an explicit 'Use when...' trigger clause and missing natural trigger synonyms, which cap completeness and trigger-term quality at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a task requires someone's own logins, credentials, files, or knowledge and you cannot complete it yourself.'

Include natural trigger phrases a requester would actually say — 'credentials', 'on their behalf', 'hand it off', 'can you ask them' — to broaden keyword coverage.

Briefly distinguish the skill from the sibling request-access skill (e.g., 'for a single credential, use request-access instead') to sharpen distinctiveness and reduce overlap risk.

DimensionReasoningScore

Specificity

Quotes: 'Decide whether to just do it yourself', 'ask that person by DM with the full request', 'needs another person's own logins, files or memory'. It lists several concrete actions (self-serve decision, DM ask with full request) plus the qualifying condition, matching the 'several specific actions; minor gaps' anchor; it is above the 1-2-action anchor at 3 but the action list is not comprehensive enough for 5.

4 / 5

Completeness

The 'what' is clear ('Get work done that needs another person's own logins... ask that person by DM with the full request'), but there is no explicit 'Use when...' clause or equivalent trigger guidance — the 'when' is only weakly implied by the condition clause. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3; this also fits anchor 3 better than anchor 4, which requires an explicit 'when'.

3 / 5

Trigger Term Quality

Quotes: 'logins', 'files or memory', 'DM', 'ask that person'. Some natural keywords are present, but common variations users would actually say — 'credentials', 'on their behalf', 'hand it off', 'their account' — are missing, which fits the 'some relevant keywords but missing common variations or synonyms' anchor rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

Quotes: 'another person's own logins, files or memory', 'ask that person by DM with the full request'. The niche — delegating work to a specific person via DM — is mostly distinct with only minor overlap risk against closely related skills (e.g., a generic messaging or request-access skill). It lacks the explicit distinct triggers needed for the minimal-conflict anchor at 5, but is clearly more specific than the overlap-prone anchors at 2-3.

4 / 5

Total

14

/

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

yc-software/qm

Path

skills-seed/hand-off/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.