vellum-oauth-integrations

Configure OAuth 2.0 provider connections and execute authenticated requests.

2|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/autonomy-cloud/kairos-interface --skill vellum-oauth-integrations-autonomy-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vellum-oauth-integrations
Source: https://github.com/autonomy-cloud/kairos-interface/tree/main/skills/vellum-oauth-integrations
Command: npx skills add https://github.com/autonomy-cloud/kairos-interface --skill vellum-oauth-integrations-autonomy-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of setting up OAuth 2.0 integrations so your assistant can act on your behalf in third-party apps while minimizing unnecessary permissions.

Core Features & Use Cases

  • Provider discovery and configuration: Identify available OAuth providers, choose their operating mode (managed vs your-own), and understand what each mode implies for setup and routing.
  • Account connection and scope management: Guide the user through connecting accounts, selecting the least-privilege scopes, and updating scopes by reconnecting with expanded permissions.
  • Authorized request execution patterns: Provide rules for making authenticated requests on the user’s behalf, including an explicit confirmation gate for side-effect operations.

Quick Start

Connect a new OAuth provider by running the appropriate OAuth connect flow and selecting only the scopes needed for the specific action you want the assistant to perform.

Frequently Asked Questions about vellum-oauth-integrations

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

FAQPage Schema
How do I connect a third-party account using OAuth 2.0 safely?

Managed OAuth provider mode routes setup and authentication through the assistant's infrastructure, whereas your-own mode requires you to supply and manage your own provider credentials directly for the integration.

What is the difference between managed and your-own OAuth provider modes?

Managed OAuth provider mode routes setup and authentication through the assistant's infrastructure, whereas your-own mode requires you to supply and manage your own provider credentials directly for the integration.

How do I handle scope updates when my OAuth permissions are insufficient?

For side-effect operations during authenticated request execution, the assistant OAuth CLI requires explicit confirmation before proceeding, ensuring that actions modifying data on third-party platforms are explicitly approved.

Do I need to confirm side-effect requests when making authenticated API calls?

For side-effect operations during authenticated request execution, the assistant OAuth CLI requires explicit confirmation before proceeding, ensuring that actions modifying data on third-party platforms are explicitly approved.

What is the best way to apply least privilege when selecting OAuth scopes?

The best way to apply least privilege is selecting only the specific OAuth scopes needed for the exact action you want the assistant to perform, avoiding broad permissions during the initial account connection and onboarding process.