Agent skill / mattpocock
Compact the current conversation into a handoff document for another agent to pick up.
Core file
| name | handoff |
| description | Compact the current conversation into a handoff document for another agent to pick up. |
| argument-hint | "What will the next session be used for?" |
| disable-model-invocation | true |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionhandoffExecute the skills CLI command in your project's root directory to begin installation:
Package manager
npx skills install mattpocock/skills/handoffFetches handoff from mattpocock/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate handoff. Access via /handoffin your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Copy the command for your terminal
Package manager
npx skills install mattpocock/skills/handoffWorks with
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
mattpocock/skills
mattpocock/skills
mattpocock/skills
mattpocock/skills
mattpocock/skills
I recommend handoff for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
handoff fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: handoff is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added handoff from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for handoff matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: handoff is focused, and the summary matches what you get after install.
Useful defaults in handoff — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
handoff has been reliable in day-to-day use. Documentation quality is above average for community skills.
handoff reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: handoff is focused, and the summary matches what you get after install.
showing 1-10 of 61