`credential-brokers` — guides
Understand and select the credential setup and broker interfaces that keep cleartext secrets out of agent context.
The credential layer behind every skill that touches a private API. A skill never holds a secret: it invokes a credentialed primitive — a CLI, an MCP server, a Python module — that resolves the secret in-process (environment variable → OS keyring → dotfile) and makes the API call itself. Cleartext never reaches the model. The credential-setup skill walks a user through entering the keys a skill declares.
New here? Read Credentialed skills for the two-layer model, then add a credentialed skill when you’re authoring one.
How-to
Section titled “How-to”- Add a credentialed skill — pick a broker, declare the credentials, and wire the verbatim security-rules blocks.
Reference
Section titled “Reference”credbrokerSSO API — the consumer surface forauth: sso-cookie: resolving a jar, re-establishing an expired session, first capture, destination derivation, and which failures a consumer may recover from.
Explanation
Section titled “Explanation”- Credentialed skills — the two-layer architecture, why skills don’t hold tokens, and how it differs by install route.
Installing and upgrading live in ../_shared/. The shipped jira and figma skills are runnable references for the pattern.