菜单
Compact the current conversation into a handoff document so another agent or future session can continue the work without losing context. Use when ending a session, switching tasks, the context is getting long, or user says handoff, wrap up, save progress, or "continue this later".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Search, install, update, and rate AI agent skills from agentskill.sh (100,000+ skills). Use when the user asks to find skills, install extensions or plugins, discover new capabilities, check what skills are available, or says "how do I do X" when a skill might help. Also handles listing installed skills, checking for updates, rating skills, removing skills, and scanning skills for security issues. Triggers on: /learn, find skill, install skill, search skills, what skills, add capability, get plugin, check skill safety.
Review and improve AI agent skills (SKILL.md files) against best practices from the Agent Skills specification and Anthropic's authoring guidelines. Scores skills on 10 quality dimensions, identifies specific issues, and rewrites problem areas. Use when creating, editing, auditing, or improving agent skills. Triggers on: review skill, improve skill, audit SKILL.md, check skill quality, skill best practices, optimize skill description.
AI-native product thinking and modern product design philosophy. Every product should consider AI copilots, semantic search, intelligent automation, conversational workflows, contextual AI assistance, and recommendation systems. Products must feel modern, premium, intelligent, polished, and production-ready. Use when designing new features, reviewing product roadmap, or evaluating whether AI capabilities would enhance a workflow. Covers Azure OpenAI, OpenAI, Anthropic, RAG pipelines, vector DBs, semantic indexing, and AI workflow orchestration.
Autonomous senior-engineer bug fixing workflow. Investigates independently, inspects logs, traces root causes, reproduces issues, fixes thoroughly, and validates correctness — without asking for unnecessary guidance. Use whenever encountering bugs, failing builds, broken UX, CI failures, test failures, regressions, or any unexpected behavior. Operates the way a staff engineer would: hypothesis-driven, evidence-driven, root-cause-driven.
Aggressive consumer-product improvement doctrine. Runs the Analyze → Critique → Reimagine → Stress Test → Improve → Refine cycle on any shipped or in-flight feature. Evaluates UX friction, cognitive load, perceived intelligence, retention mechanics, delight, AI-native opportunities, and five user perspectives (first-time, daily, power, mobile, impatient). Use after every implementation pass, when auditing existing UI, when expanding a feature, when the user shares product feedback, or proactively to elevate "functional but boring" surfaces into premium consumer-grade experiences. Mandates feature-ecosystem thinking, not isolated screens.
Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to agents-memory-updater. Use when the user asks to mine prior chats, maintain AGENTS.md, or run the continual-learning loop.
| name | handoff |
| description | Compact the current conversation into a handoff document so another agent or future session can continue the work without losing context. Use when ending a session, switching tasks, the context is getting long, or user says handoff, wrap up, save progress, or "continue this later". |
Write a handoff document capturing everything needed to continue this work.
1. GOAL — what we're building/fixing (one sentence)
2. CURRENT STATE — what's done, what's in progress, what's blocked
3. KEY DECISIONS MADE — choices that shouldn't be re-litigated
4. OPEN QUESTIONS — unresolved decisions awaiting input
5. NEXT STEPS — exact actions to take (not vague "continue working")
6. FILES TOUCHED — paths modified this session
7. SUGGESTED SKILLS — which skills the next session should invoke
Save to the OS temp directory (not the workspace):
$env:TEMP/handoff-{project}-{date}.md/tmp/handoff-{project}-{date}.mdTell the user the path so they can reference it next session.
Keep it SHORT. Under 50 lines. A good handoff is one page a new agent can scan in 10 seconds and know exactly what to do.