crocoder-dev/opencode-sce-handover-writer
Create structured handover notes for Shared Context Engineering tasks.
100
100%
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 trigger terms that users would naturally say, explicit 'Use when...' guidance, and clear distinctiveness from other documentation skills. The description is well-structured and appropriately concise while being comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'summarizing task context, decisions made, open questions, and recommended next steps' and specifies the output location 'context/handovers/'. Uses proper third person voice. | 3 / 3 |
Completeness | Clearly answers both what ('Creates a structured handover document summarizing task context, decisions made, open questions, and recommended next steps') AND when with explicit 'Use when...' clause and specific trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'hand off', 'transition', 'pass a task', 'handover notes', 'task transition document', 'capture current progress'. Also includes explicit trigger phrases like 'create a handover', 'hand this off', 'write handover notes'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on handover/transition documentation with distinct triggers like 'handover', 'hand off', 'pass this task on'. Unlikely to conflict with general documentation or note-taking skills due to specific terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that exemplifies good practices: it's concise, provides an actionable template with concrete examples, has a clear workflow with validation, and is appropriately structured for its scope. The skill assumes Claude's competence while providing exactly the guidance needed for consistent handover document creation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, with no unnecessary explanations of concepts Claude already knows. Every section serves a clear purpose and the template is appropriately minimal. | 3 / 3 |
Actionability | Provides a concrete, copy-paste ready template with specific examples for each section. The file naming convention and directory structure are explicit and actionable. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with an explicit validation checkpoint ('Verify completeness'). The workflow handles edge cases (missing details) with clear guidance to infer and label assumptions. | 3 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections. No external references are needed, and the structure (What/How/Template/Output) provides easy navigation. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents