Skip to content

credential-brokers — guides

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

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.