Our review
Creates a markdown file summarizing key parts of a conversation for handover to another colleague or agent.
Strengths
- Captures tasks, accomplishments, bugs, and uncertainties in a structured format
- Facilitates seamless knowledge transfer
- Saves time by automating documentation of key conversation points
Limitations
- Depends on the quality of conversation context
- May miss nuances if not explicitly mentioned
- Output file may require manual review for completeness
Use when handing over a project to another developer or agent to ensure continuity.
Do not use for trivial tasks where handover is unnecessary, or when the conversation lacks substantive content.
Security analysis
SafeThe skill only instructs to write a summary of conversation points to a markdown file. It does not involve any execution of system commands, network access, or modification of system state beyond file creation. No risks are present.
No concerns found
Examples
Externalise the key parts of this conversation about the database connection issue into a handover markdown file.Create a handover summary of the tasks accomplished this week, the bugs found, and the next steps.I need to hand over this project to a colleague. Please externalise the current conversation into a handover.md file with tasks completed and pending.name: externalise-handover description: Externalise important parts of the current conversation into an .md file for handover.
Externalise / Handover tasks
Instructions
Externalise important parts of the current conversation into an .md file to hand over to another colleague or agent.
Focus on:
- Tasks to do next.
- What's been accomplished (exact commands run, inputs/args, outputs including file paths).
- Bugs encountered.
- Key areas of uncertainties.
- User instructions and clarifications, touched up to be clearer.
Context: Use any additional context provided in the arguments.
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Pivot Decision Framework
Documentation
Documents a strategic pivot or persevere decision with evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.