Agent Skills › yc-software/qm › request-access

request-access

GitHub

当命令需要未授权的密钥链凭证时,向所有者发送访问请求。通过 API 提交申请,等待审批后自动重试命令,确保权限合规且流程自动化。

skills-seed/request-access/SKILL.md yc-software/qm

Trigger Scenarios

需要访问他人密钥链凭证 命令因缺少授权被阻塞

Install

npx skills add yc-software/qm --skill request-access -g -y
More Options

Non-standard path

npx skills add https://github.com/yc-software/qm/tree/main/skills-seed/request-access -g -y

Use without installing

npx skills use yc-software/qm@request-access

指定 Agent (Claude Code)

npx skills add yc-software/qm --skill request-access -a claude-code -g -y

安装 repo 全部 skill

npx skills add yc-software/qm --all -g -y

预览 repo 内 skill

npx skills add yc-software/qm --list

SKILL.md

Frontmatter
{
    "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."
}

Request access to someone's credential

Use this when a command needs someone's credential and the Credentials section shows no handle for it here. 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 -sS -X POST "$AGENT_API_URL/v1/keychain/asks" \
  -H "x-agent-capability: $AGENT_API_TOKEN" -H 'content-type: application/json' \
  -d '{"owner":"<their name or principal id>","service":"<service, e.g. github>","purpose":"<what the command will do>"}'
  • The server finds the credential from owner and service. If it can't tell which one you mean, it answers 404 or 409 with candidates; pick one and send {"credential":"<its credential id>", ...} instead.
  • purpose is 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.

Version History

  • b4f4b30 Current 2026-11-02 10:52
  • 6803edb 2026-10-18 18:22

Same Skill Collection

.claude/skills/dev-instance/SKILL.md
.claude/skills/update-qm/SKILL.md
.claude/skills/upstream-pr/SKILL.md
.codex/skills/deploy-qm/SKILL.md
.codex/skills/dev-instance/SKILL.md
.codex/skills/update-qm/SKILL.md
.codex/skills/upstream-pr/SKILL.md
cli/templates/deployment/SKILL.md
plugins/onboarding/skills/onboarding/SKILL.md
skills-seed/admin/SKILL.md
skills-seed/browse/SKILL.md
skills-seed/cloud-cli/SKILL.md
skills-seed/composio/SKILL.md
skills-seed/connect-apps/SKILL.md
skills-seed/define-loop/SKILL.md
skills-seed/dropbox/SKILL.md
skills-seed/email-draft-in-voice/SKILL.md
skills-seed/email-voice-profile/SKILL.md
skills-seed/github-gitlab/SKILL.md
skills-seed/google-drive-sheets/SKILL.md
skills-seed/google-workspace/SKILL.md
skills-seed/hand-off/SKILL.md
skills-seed/interactive-login/SKILL.md
skills-seed/linear/SKILL.md
skills-seed/memory/SKILL.md
skills-seed/miniapp/SKILL.md
skills-seed/morning-digest/SKILL.md
skills-seed/popular-web-designs/SKILL.md
skills-seed/publish/SKILL.md
skills-seed/secret-drop/SKILL.md
skills-seed/send/SKILL.md
skills-seed/slack-drafts/SKILL.md
skills-seed/taste-skill/SKILL.md
skills-seed/ui-canvas/SKILL.md
skills-seed/ui-state/SKILL.md
skills-seed/use-shared-credential/SKILL.md
skills-seed/zoom/SKILL.md

Metadata

Files
0
Version
b4f4b30
Hash
cf990551
Indexed
2026-10-18 18:22

trang chủ - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-11-02 15:43
浙ICP备14020137号-1