AGENT SKILL

secret-drop

Request a credential nobody has saved yet (an API key, a site login) with a one-time, expiring link that saves it to the person's keychain. Use instead of asking for secrets in chat or sending people to the keychain page.

License 许可
MIT
所属仓库
yc-software/qm
最近更新
2026-11-15
Stars
★ 1.6w
Forks
2.0k

01 前言 Front Matter

name
secret-drop
description
Request a credential nobody has saved yet (an API key, a site login) with a one-time, expiring link that saves it to the person's keychain. Use instead of asking for secrets in chat or sending people to the keychain page.

03 SKILL.md 正文

Secret drop: request a new credential by link

Use this when a task needs a credential nobody has saved yet. Never ask for a secret in chat, and never tell the person to add it on the keychain page by hand.

  • A teammate's credential that is already saved: use the request-access skill instead.
  • A CLI with a device-code or browser login (gh, aws sso, gcloud): use interactive-login.

Mint the link

Only on a turn a person sent. Scheduled and trigger-fired turns are refused.

curl -fsS -X POST "$AGENT_API_URL/v1/keychain/drops" \
  -H "x-agent-capability: $AGENT_API_TOKEN" -H 'content-type: application/json' \
  -d '{"service":"acme","purpose":"sign in to the Acme dashboard","fields":[{"key":"ACME_EMAIL","label":"Email","secret":false},{"key":"ACME_PASSWORD","label":"Password"}]}'
  • service names the credential; purpose is one plain sentence the person sees on the form.
  • fields declares the form inputs (1–8). Keys are env var names; secret:false shows the input in clear text (usernames, emails). For a single token, omit fields and pass "envKey":"ACME_API_KEY" instead.
  • The link belongs to the person whose turn this is. If a different teammate in this conversation will fill it, add "onBehalfOf":"<their id>".
  • Send the header exactly as shown. Authorization: Bearer is not accepted.

The response is {dropId, url}. Give the person url exactly as returned. It carries a link-bound token, so a rebuilt URL will not work.

Then

  • Tell them in one line what the link is for. It works once and expires.
  • Stop. Don't poll.
  • When they submit, the value is saved encrypted to their keychain (and, in a channel or group, granted to this conversation) and this conversation wakes with the new credential's handle. Select that handle in execute.credentials to get the declared env vars.
  • If the link expires or they used the wrong account, mint a fresh one.

A memory brain's client secret

When an org admin registers a memory brain (PUT /v1/admin/memory-registry/brains/<id>), or a member connects their own (PUT /v1/memory/brain), its client secret never goes through chat or the agent. Mint a brain link instead, on that person's own turn:

curl -fsS -X POST "$AGENT_API_URL/v1/keychain/drops" \
  -H "x-agent-capability: $AGENT_API_TOKEN" -H 'content-type: application/json' \
  -d '{"memoryBrain":"acme-personal","purpose":"connect the Acme personal memory brain"}'
  • Only memoryBrain and purpose: no service, fields, envKey or onBehalfOf.
  • The form shows them where memory goes (the brain and who is bound to it) before they submit.
  • The secret goes straight to QM's memory registry. It never enters a keychain, can't be granted and is never on the agent's computer, so there is no handle to select and nothing wakes this conversation. Ask them to tell you when they've submitted, then check hasClientSecret in GET /v1/admin/memory-registry (admins) or GET /v1/memory/brain (a member's own brain).
  • If the brain's URL changed after the link was made, the link refuses; mint a fresh one.

04 同仓库更多 Skills

yc-software
yc-software/qm

zoom

Find, create, reschedule, and cancel the user's Zoom meetings through their own Zoom connection.

★ 1.6w
yc-software
yc-software/qm

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.

★ 1.6w
yc-software
yc-software/qm

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.

★ 1.6w
yc-software
yc-software/qm

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.

★ 1.6w
yc-software
yc-software/qm

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.

★ 1.6w
yc-software
yc-software/qm

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.

★ 1.6w