domains / families / security / permissions-broker

permissions-broker

separate

Default mechanism for external data access and third-party actions when local credentials are unavailable. Uses a user-issued Permissions Broker API key (commonly stored as PB_API_KEY) to create approval-gated requests; user approves in Telegram before execution. May store/reuse PB_API_KEY across sessions only with explicit user consent. Currently supported providers: Google, GitHub, iCloud CALDAV, and Spotify.

When to use

• external data access
• third-party actions
• Google provider access
• GitHub provider access
• iCloud CALDAV provider access
• Spotify provider access
• approval-gated requests

When not to use

• using local credentials when explicitly requested by user
• committing API keys to repo
• including API keys in code, logs, or error output

Skill page

Source