# Use Shared Credential

When you need to call a service the org has a SHARED credential for (a SERP/search key...

- Repository: https://github.com/yc-software/qm (15597 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add yc-software/qm --skill use-shared-credential -g -a claude-code -y`
Codex: `npx skills add yc-software/qm --skill use-shared-credential -g -a codex -y`
Cursor: `npx skills add yc-software/qm --skill use-shared-credential -g -a cursor -y`
Gemini CLI: `npx skills add yc-software/qm --skill use-shared-credential -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Use a shared org credential (by proxy, never the raw secret)

Some credentials aren't yours and aren't on your computer, they're **one org credential the
admin vends to people**, like a shared doc: an org web-search key, a paid-API key, a
data-vendor feed. You are NOT given the secret (a shared bearer sitting in your shell could
leak). Instead you make the call **by proxy**: you name the credential + the request, and the
core stamps the secret onto the outbound call at the wire and returns the response.

## When this applies

The **Credentials** inventory groups available credentials by owner. Organization rows marked
`proxy` give the host and allowed methods/paths. Select that credential's handle (e.g. `gitlab`) in
`execute.credentials` for the command making the request, with an explicit `sandbox_id`. Core supplies
`AGENT_CREDENTIAL_TOKEN` only to that command; its absence before selection does not mean
access is missing. Use that token, not `AGENT_API_TOKEN`, for broker requests.

Only listed credentials are available. A separately authorized personal login or connected
app may also be available; use only its advertised capabilities and permissions. Never
route around a denial or ask the user to paste a token.

## How to call it

```bash
curl -fsS -X POST "$AGENT_API_URL/v1/credentials/broker" \
  -H "x-agent-capability: $AGENT_CREDENTIAL_TOKEN" \
  -H "content-type: application/json" \
  -d '{
        "credential": "<slug from your system prompt>",
        "method": "GET",
        "url": "https://<the credential's host>/<allowed path>?<query>",
        "headers": { "accept": "application/json" }
      }'
```

The reply is an envelope, the upstream status + body, never the secret:

```json
{ "status": 200, "contentType": "application/json", "body": "<the upstream response text>" }
```

The rest: https://github.com/yc-software/qm/blob/HEAD/skills-seed/use-shared-credential/SKILL.md