handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or agent; brief a colleague taking over; prepare a shift change summary; or onboard someone mid-task. Produces ready-to-use handoff documents covering current status, next steps, known issues, technical context, and communication templates for both planned and unplanned transfers.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, comprehensive natural trigger terms covering many user phrasings, explicit 'Use when' guidance, and a clearly distinct niche. The description is thorough without being padded, and uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating structured handoff documents, summarizing project status, documenting key decisions/blockers/open questions, and generating onboarding briefs. Also specifies output contents: current status, next steps, known issues, technical context, and communication templates. | 3 / 3 |
Completeness | Clearly answers both 'what' (creating structured handoff documents, summarizing status, documenting decisions/blockers/questions, generating onboarding briefs) and 'when' with an explicit 'Use when...' clause listing multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'hand off', 'hand over', 'transition a project', 'pass work', 'brief a colleague taking over', 'shift change summary', 'onboard someone mid-task'. These are highly natural phrases that cover many variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around work transitions and handoffs between team members or agents. The specific focus on handoff documents, shift changes, and mid-task onboarding is distinct and unlikely to conflict with general project management or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with well-structured templates and clear workflows. Its main weakness is length — the full handoff document template, communication templates, and multiple checklists make it quite long for a single SKILL.md file. Some content like the anti-patterns one-liner and the 'Receiving a Handoff' section add limited value relative to their token cost.
Suggestions
Move the full handoff document template and communication templates into a separate TEMPLATES.md file, keeping only a brief summary and link in SKILL.md
Remove or significantly trim the 'Receiving a Handoff' section and 'Handoff Anti-Patterns' — these describe behaviors Claude already understands and add little actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately verbose. While the templates and checklists are useful, there's some unnecessary padding (e.g., the anti-patterns section is vague, the 'Receiving a Handoff' section states obvious steps Claude would know). The handoff document template is quite long and could be more concise. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste ready templates including a full handoff document structure, bash commands for code state preparation, communication templates with fill-in-the-blank fields, and detailed checklists. These are directly usable. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit checklists (before/during/after meeting), the code state preparation has a clear validation sequence (git status → tests → build), and the quality checklist serves as a final verification step for both giver and receiver. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with all templates, checklists, and guidance inline. The handoff document template alone is quite long and could be a separate referenced file. The 'Integration with Other Skills' section hints at cross-references but the main content would benefit from splitting templates into separate files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- rohitg00/skillkit
- Commit
dfa8d12
- 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.