handout

Package the current conversation into a self-contained Markdown handover file.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/SilvrDuck/skills --skill handout
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handout
Source: https://github.com/SilvrDuck/skills/tree/main/skills/handout
Command: npx skills add https://github.com/SilvrDuck/skills --skill handout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The handout skill creates a self-contained Markdown briefing so another person (or a fresh LLM session) can immediately understand the project context and current status without reading the entire chat transcript.

Core Features & Use Cases

  • Conversation-to-handover packaging: Converts the current session into a concise, structured document optimized for reuse.
  • Argument-focused outputs: When given a focus question, organizes the handover around answering that specific blocker rather than summarizing everything.
  • File-safe artifact generation: Writes the result to a predictable repo-root filename (defaulting to HANDOUT.md) and avoids clobbering existing files by using a numeric suffix.

Quick Start

Use /handout to write a general handover saved as HANDOUT.md at the repo root that you can paste into a fresh LLM to continue work immediately.

Frequently Asked Questions about handout

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize a chat session for an LLM handover?▼

To summarize a chat session for an LLM handover, you package the current conversation into a self-contained Markdown document. This skill structures the context into project primer, goals, completed work, and current state for immediate reuse.

Can I focus a conversation handover on a specific question?▼

Yes, you can focus a conversation handover on a specific question. When provided with a focus question, the skill organizes the Markdown output around answering that specific blocker rather than summarizing the entire session history.

What is the best way to create a markdown handover file at the repo root?▼

The best way to create a markdown handover file at the repo root is to use a skill that writes directly to the repository. It generates a predictable HANDOUT.md file, automatically adding numeric suffixes to avoid overwriting existing files.

Does the generated handover document include metadata for collaboration?▼

Yes, the generated handover document includes metadata for collaboration. The Markdown file features YAML frontmatter defining the name and description, ensuring a fresh LLM or human collaborator understands the briefing context immediately.

How do I structure session context for a fresh LLM workflow?▼

You structure session context for a fresh LLM workflow by dividing the information into defined sections. The handover includes a project primer, user goal, what has been done, the current state, and what would actually help next.

What happens if a HANDOUT.md file already exists in my repository?▼

If a HANDOUT.md file already exists in your repository, the skill avoids clobbering your existing file. It automatically generates the new handover artifact with a numeric suffix to preserve both versions safely.