Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From teamem
Hand a claimed scope from the user to a specific teammate — release my claim, post a discussion message explaining the handoff, optionally request the teammate to claim it next. Use when the user is stopping work mid-feature and wants someone else to pick it up.
npx claudepluginhub rubiyh/teamem --plugin teamemHow this skill is triggered — by the user, by Claude, or both
Slash command
/teamem:teamem-handoffThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are coordinating a clean handoff of in-flight work to a teammate.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Guides systematic root-cause debugging when tests fail, builds break, or unexpected errors occur. Provides a structured triage checklist to preserve evidence, localize, and fix issues instead of guessing.
Share bugs, ideas, or general feedback.
You are coordinating a clean handoff of in-flight work to a teammate.
claim_id (or scope paths) the user is handing off.recipient_principal (teammate's name in the space).If any are missing, ask before doing anything.
Confirm the handoff with the user — show them the four inputs and ask "ship it?". Do not proceed without explicit confirmation.
Compose the handoff message. Format it like a checklist for the recipient:
Handoff: <scope summary>
- Status: <done so far>
- Pending: <what's left>
- Branch / commits: <ref>
- Deadline: <if any>
- Notes: <gotchas>
Post the message via mcp__teamem__post_message:
recipient_principal: the teammatebody: the formatted note abovethread_id — handoffs start a new thread)Release the user's claim via mcp__teamem__release_scope with the claim_id.
Tell the user the recipient can pick the message up via SessionStart sync, /teamem-status, or optional channel delivery; they can run /teamem-status to see the discussion in their inbox.
active_claims).get_briefing if uncertain)./teamem-on first) — without active subscribers, the recipient won't see the message until their next /teamem-on.