configuration-skill

Manage API keys and OAuth credentials via chat with per-key approvals.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/misunders2d/ori --skill configuration-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: configuration-skill
Source: https://github.com/misunders2d/ori/tree/main/skills/configuration-skill
Command: npx skills add https://github.com/misunders2d/ori --skill configuration-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Secure management of API keys and OAuth credentials via chat, enabling safe, auditable integration setup.

Core Features & Use Cases

  • Add, list, and remove API keys and OAuth credentials securely from chat.
  • Supports multiple providers (Slack, Google, GitHub, ClickUp, etc.) with a deterministic per-key approval flow.
  • Provides governance and auditability through vault-backed storage and guided configuration.

Quick Start

Configure Slack by supplying SLACK_BOT_TOKEN, then SLACK_APP_TOKEN, in sequential steps.

Frequently Asked Questions about configuration-skill

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

FAQPage Schema
How do I securely configure API keys and OAuth credentials through chat?▼

Securely configure API keys and OAuth credentials through chat by using a deterministic, per-key approval workflow that routes provider-specific tokens into vault-secure storage, preventing unauthorized access during integration setup.

What's the best way to add Slack tokens step by step for integration setup?▼

Add Slack tokens step by step for integration setup by supplying the SLACK_BOT_TOKEN first, then the SLACK_APP_TOKEN sequentially, completing the configuration path through guided chat interactions.

Does this workflow support managing credentials for multiple providers like Google and GitHub?▼

Managing credentials for multiple providers like Google and GitHub is supported, allowing you to add, list, update, or remove OAuth credentials and API keys across various platforms using a unified governance process.

How does per-key approval improve API key security during configuration?▼

Per-key approval improves API key security during configuration by enforcing a deterministic governance workflow, ensuring each credential is explicitly authorized and vault-secured before activating any provider integration.

Can I list and remove existing OAuth credentials across different providers?▼

List and remove existing OAuth credentials across different providers through chat commands, applying the same per-key approval governance to maintain auditable and secure integration lifecycle management.

Why use vault-secure capture for adding API keys via chat interactions?▼

Vault-secure capture for adding API keys via chat interactions ensures sensitive tokens bypass plaintext exposure, satisfying strict governance and security requirements while maintaining an auditable configuration trail.