hand-off
Get work done that needs another person's own logins, files or memory. Decide whether to just do it yourself, and if not, ask that person by DM with the full request.
- License 许可
- MIT
- 所属仓库
- yc-software/qm
- 最近更新
- 2026-11-15
- Stars
- ★ 1.6w
- Forks
- 2.0k
01 前言 Front Matter
- name
- hand-off
- description
- Get work done that needs another person's own logins, files or memory. Decide whether to just do it yourself, and if not, ask that person by DM with the full request.
03 SKILL.md 正文
Hand work to another person
First, can you do it yourself?
- Open posture (your prompt has
## Sharing posture: Open): do the work yourself with the requester's own logins. Don't hand it off. - Isolated: hand off only when the work needs that person's own logins, keys, files or memory.
Shared services and org credentials don't need a hand-off. If you only need one of their
credentials, use the
request-accessskill instead.
Ask them by DM
curl -fsS -X POST "$AGENT_API_URL/v1/reach" \
-H "x-agent-capability: $AGENT_API_TOKEN" -H 'content-type: application/json' \
-d '{"recipient":"<their name or Slack id>","text":"<the full request>"}'
- They haven't seen this conversation. Write out the whole request: what's needed and why.
- Start the DM with the source channel name and a permalink to the originating thread, and ask them to reply there (or DM the requester if they can't post there).
- One DM to that person. Never post the request in a channel.
Then
- Say you messaged someone only after reach returns
ok: true, and name the person it matched (recipient.displayName). If it failed or matched the wrong person, say that instead. - Don't wait or poll for their reply.
04 同仓库更多 Skills
zoom
Find, create, reschedule, and cancel the user's Zoom meetings through their own Zoom connection.
use-shared-credential
When you need to call a service the org has a SHARED credential for (a SERP/search key, a paid-API key, a data-vendor feed, a Git remote) — and the platform has told you that credential is available to this conversation — make the call BY PROXY through the credential broker. You never see the secret; the core stamps it onto the outbound request for you.
ui-state
See what the person is looking at in the QM web UI right now — the whole page (sidebar, every multiview pane, open dialogs) as raw HTML, the app's state as JSON, optionally the CSS and a screenshot. Use when they ask about something on their screen, want help with the UI, or you need to check what a canvas you wrote actually rendered.
ui-canvas
Draw your own HTML/CSS/JS as a full-window overlay on top of the QM web UI — a dashboard, a form, a visualization, controls that message you back. Write, update, replace, pin or dismiss it. Use when an interactive or visual result beats a chat reply.
taste-skill
Design taste and process for anything a person will look at in a browser — landing page, dashboard, prototype, deck. The default design driver for a browsable artifact, with an anti-slop playbook for the visual language.
slack-drafts
Create Slack message drafts in the user's own composer, as the user, through their per-user Slack OAuth. Drafting only — the user reviews and sends from Slack.