request-access
Ask a person for access to one of their keychain credentials when a command needs it and this conversation has no grant yet. The platform posts an approval card where this conversation is happening; the owner clicks it, and the blocked command re-runs.
- License 许可
- MIT
- 所属仓库
- irisfeng/moqi
- 最近更新
- 2026-11-05
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- request-access
- description
- Ask a person for access to one of their keychain credentials when a command needs it and this conversation has no grant yet. The platform posts an approval card where this conversation is happening; the owner clicks it, and the blocked command re-runs.
03 SKILL.md 正文
Request access to someone's credential
Use this when the keychain manifest lists a credential you need but shows no grant for this conversation. Your own credentials in your own personal conversation never need this.
Request
One call, from this session or any sub-agent. The approval belongs to the whole conversation, so every session in it sees the same grant.
curl -fsS -X POST "$AGENT_API_URL/v1/keychain/asks" \
-H "x-agent-capability: $AGENT_API_TOKEN" -H 'content-type: application/json' \
-d '{"credential":"<credential id>","purpose":"<what the command will do>"}'
purposeis one plain sentence about the command, not the whole task.- If a request for that credential is already pending, the same one comes back. Don't ask twice.
Where the card shows up
You don't choose. The card appears where this conversation is: the Slack thread or channel, inline in the web session (and in its parent when you are a sub-agent), or the scheduled job's destination. Only the credential's owner can click it; nothing said in chat is approval.
Then
- Tell the person in one short line that you asked the owner for access. No request ids, no request text, no "paused".
- Stop. Don't retry, poll, or work around the missing credential.
- When the owner approves, this conversation re-runs the blocked command on its own. Continue with one short line.
- If they deny or it expires, say so in one line and offer another way.
04 同仓库更多 Skills
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.
send
Make a PR, wait for CI with bounded transport retries, independently review, and merge only when all gates pass.