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.
Install with Tessl CLI
npx tessl i github:rohitg00/skillkit --skill handoff-protocols90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 users would actually say, explicitly answers both what and when, and carves out a distinct niche around work transitions and handoffs. The description uses proper third-person voice throughout and avoids vague language or buzzwords.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs.' Also specifies outputs: 'current status, next steps, known issues, technical context, and communication templates.' | 3 / 3 |
Completeness | Clearly answers both what (manages work transitions, creates handoff documents, summarizes status, documents decisions/blockers/questions) AND when with explicit 'Use when...' clause listing multiple trigger scenarios including handoff, transition, briefing, and onboarding contexts. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'hand off, hand over, transition a project, pass work to another person or agent, brief a colleague taking over, shift change summary, onboard someone mid-task.' These are phrases users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on work transitions and handoffs between team members or agents. The specific domain (handoffs, transitions, onboarding mid-task) and distinct triggers (hand off, shift change, pass work) make it unlikely to conflict with general documentation or project management 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 excellent templates and clear workflows for work handoffs. The main weakness is verbosity—some sections explain concepts Claude already knows (basic git hygiene, general communication advice), and the entire content could benefit from splitting detailed templates into separate reference files.
Suggestions
Move the detailed handoff document template and communication templates to separate reference files (e.g., TEMPLATES.md) and link from the main skill
Remove or condense the basic git commands section—Claude knows how to check git status and run tests
Convert the 'Handoff Anti-Patterns' section to a brief inline list rather than a separate heading, as the content is minimal
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some content Claude would know (e.g., basic git commands, general advice like 'avoid brain dumps'). The templates and checklists are useful but could be tightened. | 2 / 3 |
Actionability | Provides fully concrete, copy-paste ready templates including the complete handoff document structure, communication templates, bash commands for code preparation, and detailed checklists. All guidance is specific and executable. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit checkpoints: handoff meeting has before/during/after phases, code preparation has verification steps, and both giver and receiver have quality checklists. The sequence is unambiguous. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a table for handoff types, but the document is monolithic (~200 lines) with no references to external files. The integration section at the end hints at related skills but doesn't link to them. | 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 | |
- 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.