interactor-credentials

Manage OAuth tokens and API keys with automatic refresh and namespace isolation.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/pulzze/account-server-docs --skill interactor-credentials
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interactor-credentials
Source: https://github.com/pulzze/account-server-docs/tree/main/.claude/skills/i/interactor-credentials
Command: npx skills add https://github.com/pulzze/account-server-docs --skill interactor-credentials

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interactor Credential Management removes the complexity of securely storing and rotating OAuth tokens and API keys for external services. It enables per-user and per-organization credential isolation, automatic token refresh, and ongoing monitoring of credential status across providers like Google, Slack, Salesforce, and more.

Core Features & Use Cases

  • Token Storage: Encrypted storage of access tokens, refresh tokens, and API keys.
  • Automatic Refresh: OAuth tokens are refreshed before expiry.
  • Multi-tenant Isolation: Namespaces separate different users' credentials.
  • Revocation Handling: Detects when users revoke OAuth access.
  • Unified Interface: One API for OAuth credentials and API keys, with consistent workflows.
  • Use Cases: Connect external services, manage long-lived authorizations, rotate credentials safely, and audit credential status.

Quick Start

Initiate an OAuth flow for a user by calling the /oauth/initiate endpoint and follow the returned authorization URL to complete the grant. Once completed, poll /oauth/status/{flow_id} until a credential_id is returned.

Frequently Asked Questions about interactor-credentials

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I securely manage OAuth tokens for external services in a multi-tenant app?

Automatically refresh OAuth tokens before expiry using a backend-only execution model that handles token retrieval and revocation. This ensures long-lived authorizations remain valid across providers like Google, Slack, and Salesforce without manual intervention.

How do I start an OAuth flow for external service credentials?

Detect when users revoke OAuth access through ongoing monitoring of credential status across providers. The unified credential API tracks revocation events, allowing you to audit credential state and handle disconnected external services appropriately.

Can I use a single API for both OAuth tokens and API keys across different providers?

Namespaces separate different users' credentials, enforcing multi-tenant isolation across the application. This backend-only model ensures per-user and per-organization credential isolation so external service authorizations never cross tenant boundaries.

What is the best way to rotate OAuth tokens and API keys for external services?

A backend-only execution model is required to enforce namespace isolation and secure token handling. This ensures OAuth flows, token refresh, and credential monitoring operate server-side without exposing tokens to client environments.