handoff-create
Generate a structured handoff document from the current session. Captures scope, relevant files with line numbers, key discoveries, work completed, current status, next steps, and code snippets. Use before ending a session or handing work to another agent.
What this skill does
Generate a structured handoff document from our current conversation and save it to `claudedocs/handoffs/handoff_YYYYMMDD_HHMMSS.md` (or use the filename provided as `$ARGUMENTS[0]` if given). Create the `claudedocs/handoffs/` directory if it does not exist. ## Document Structure Include exactly these sections: ```markdown # Handoff: [Task Name] - [YYYY-MM-DD HH:MM] ## Task [One sentence: what is being accomplished] ## Scope [What needs to be done. Be specific about boundaries: what is in scope and what is explicitly out of scope] ## Files [All relevant files touched or needed. Format: `path/to/file:line` when a specific line matters] - `src/auth/middleware.ts:45` - token validation logic - `tests/auth.spec.ts` - test suite for this change - `docs/api.md` - needs update after implementation ## Discoveries [Key findings and insights from the work so far. Things the next agent needs to know that are not obvious from the code] - [Discovery 1] - [Discovery 2] ## Work Done [Completed tasks. Append-only: never remove prior entries. Include commit hashes when available] - [x] Task A completed (commit: abc1234) - [x] Task B completed ## Status [Current state: what is done, what remains, test status, blockers] ## Next Steps [Actionable checklist of remaining tasks, in order] 1. [ ] Step 1 2. [ ] Step 2 3. [ ] Step 3 ## Code [Relevant code snippets with context. Focus on the parts a resuming agent needs to understand immediately] \`\`\`typescript // Key implementation detail \`\`\` ``` ## Rules - Keep it under 600 words total. A resuming agent should be able to load this and proceed within 30 seconds of reading. - Use `path/to/file:line` format for all file references. Line numbers matter. - "Work Done" is append-only. Never remove previous entries. - Do not include the full git diff or full file contents. Include only the code snippets that are non-obvious. After saving, confirm the file path.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.