Fortify Development
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
Act on behalf of your user in any third-party software that supports OAuth 2.0
Install Vellum OAuth Integrations
$ npx skills add vellum-ai/vellum-assistant --skill vellum-oauth-integrations -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-oauth-integrations --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vellum-oauth-integrations .claude/skills/vellum-oauth-integrations && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vellum-oauth-integrations" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-oauth-integrations into .claude/skills/vellum-oauth-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-oauth-integrations", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-oauth-integrationsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vellum-ai/vellum-assistant --skill vellum-oauth-integrations -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-oauth-integrations --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vellum-oauth-integrations .agents/skills/vellum-oauth-integrations && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vellum-oauth-integrations" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-oauth-integrations into .agents/skills/vellum-oauth-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-oauth-integrations", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vellum-ai/vellum-assistant --skill vellum-oauth-integrations -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-oauth-integrations --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vellum-oauth-integrations .cursor/skills/vellum-oauth-integrations && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vellum-oauth-integrations" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-oauth-integrations into .cursor/skills/vellum-oauth-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-oauth-integrations", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vellum-ai/vellum-assistant.git --path skills/vellum-oauth-integrations--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vellum-ai/vellum-assistant --skill vellum-oauth-integrations -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-oauth-integrations --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vellum-oauth-integrations .gemini/skills/vellum-oauth-integrations && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vellum-oauth-integrations" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-oauth-integrations into .gemini/skills/vellum-oauth-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-oauth-integrations", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vellum-ai/vellum-assistant vellum-oauth-integrationsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vellum-ai/vellum-assistant --skill vellum-oauth-integrations -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vellum-oauth-integrations .github/skills/vellum-oauth-integrations && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vellum-oauth-integrations" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-oauth-integrations into .github/skills/vellum-oauth-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-oauth-integrations", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vellum-ai/vellum-assistant --skill vellum-oauth-integrations -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-oauth-integrations --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vellum-oauth-integrations .opencode/skills/vellum-oauth-integrations && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vellum-oauth-integrations" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-oauth-integrations into .opencode/skills/vellum-oauth-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-oauth-integrations", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vellum-oauth-integrations- GitHub stars
- 1.4k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 729 words
- Files
- 36 (incl. references)
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Act on behalf of your user in any third-party software that supports OAuth 2.0
- Tasks that involve OAuth and OpenID Connect
- SKILL.md covers Using OAuth Integrations, The Assistant OAuth CLI, Viewing Available OAuth… and Managed vs Your-Own Mode, plus 1 more section
- Calls jq
What it does
Vellum OAuth Integrations is an agent skill from vellum-ai/vellum-assistant. Act on behalf of your user in any third-party software that supports OAuth 2.0
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 37 other files, including reference files (for example `references/CONFIGURING_APPLICATIONS.md`, `references/CONNECTING_ACCOUNTS.md` and `references/MAKING_REQUESTS.md`). Compatibility notes: Designed for Vellum personal assistants
It sits in Backend & APIs, covering OAuth and OpenID Connect. The repository describes itself as: An AI Assistant that’s easy to setup, does your work 24/7, knows your preferences and gets better over time. The licence is MIT.
When your agent uses it
- Tasks that involve OAuth and OpenID Connect
Example prompts
- “/vellum-oauth-integrations”
Requirements
- Compatibility (from SKILL.md): Designed for Vellum personal assistants
What it can do on your machine
Read from SKILL.md and the folder at commit 33cc983. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Vellum personal assistants
From compatibility in the SKILL.md frontmatter.
Context cost
Vellum OAuth Integrations loads about 1.5k tokens when it runs, and up to ~39k if it reads all its reference files. Until then it costs about 26 tokens; SKILL.md has 729 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from vellum-ai/vellum-assistant at commit 33cc983, republished under its MIT licence (© vellum-ai). 729 words, ~1,460 tokens.
Download SKILL.mdSave it as
.claude/skills/vellum-oauth-integrations/SKILL.md (or your agent's skills folder). This skill also uses 35 other files; get the full folder from GitHub.- name
- vellum-oauth-integrations
- description
- Act on behalf of your user in any third-party software that supports OAuth 2.0
- compatibility
- Designed for Vellum personal assistants
- metadata.emoji
- 🔌
Using OAuth Integrations
Integrating with a third-party software via OAuth is typically used to perform actions on behalf of the user. It involves having the user log in using their own credentials, specifying the scopes that they want to provide, and then afterwards, API requests can be made on their behalf.
Important: Avoid reaching for an OAuth integration if your intent is to act as yourself rather than as your user.
The Assistant OAuth CLI
You are provided with the assistant oauth CLI for performing all necessary oauth-related actions.
Important: When in doubt how a command works or how to do something, read the references at the bottom. Never guess at how the CLI works. Read references and use the --help flag for any command you're about to run.
Viewing Available OAuth Providers
Vellum assistants can natively integrate with any application that supports OAuth 2.0. Many OAuth providers come pre-configured and ready to use. You can view them by running:
assistant oauth providers listYou can also search for specific providers. Here's an example that searches for the "google" provider:
assistant oauth providers list --provider-key googleManaged vs Your-Own Mode
All providers support "your-own" mode and some support "managed" mode.
Default: Managed Mode
"managed" mode relies on a first-class integration with the Vellum Platform. Managed mode is typically easier to set up and get going, often only requiring the user to log in with no additional configuration needed before they can begin using the integration. Managed mode is the recommended method for most users, especially those that are less technical or newer to their Vellum assistant.
When a task needs a managed OAuth connection, present it in chat with ui_show using surface_type: "oauth_connect" instead of sending the user to Settings or trying to open the OAuth flow from shell. See Connecting Accounts for the exact surface shape.
Note that using managed mode:
- Requires an account with the Vellum Platform
- May result in billable usage
- Requires that requests to the third party are sent through Vellum's servers
Your-Own Mode
"your-own" mode requires that the user creates their own OAuth application directly with the third-party and then enter the application's Client ID and Client Secret into Vellum.
Your-own mode is typically best if:
- Vellum does not have a first-party integration with the provider and managed mode is not supported
- The user is more tech-savvy and comfortable setting up OAuth apps
- The user does not want to create an account with the Vellum Platform
- The user is more sensitive to potential billing implications
- The user is sensitive to their data going to the Vellum Platform
Show full SKILL.md (307 more words)Show less
How to Choose
Default to managed mode whenever the provider supports it. Check support with:
assistant oauth providers get <provider-key> --json | jq -r '.managedServiceConfigKey'If this returns a non-null value, managed mode is supported and should be your starting recommendation. Only fall back to your-own mode if:
- The provider does not support managed mode (
managedServiceConfigKeyis null), OR - The user explicitly wants their own OAuth app (e.g. they're running self-hosted, they're privacy-sensitive, they're configuring a per-assistant Slack app), OR
- The user already has a working your-own connection — don't re-recommend managed mid-flow for already-connected providers.
Do not present managed and your-own as equivalent choices to a fresh user. Lead with managed, then offer your-own as an alternative if they push back.
Differentiating & Setting a Provider's Mode
You can determine whether a given provider supports managed mode based on the details returned by:
# Find the provider of interest in the list response
assistant oauth providers list
# Or, return just the provider of interest with their details
assistant oauth providers get <provider-key>You can determine what mode the provider is currently set to use with:
assistant oauth mode <provider-key>You can update which mode a given provider should use with:
assistant oauth mode <provider-key> --set "managed"|"your-own"Troubleshooting
Permission / Insufficient Scope Errors
If an API request returns a 403 Forbidden, 401 Unauthorized, or a message about missing scopes, the connection likely doesn't have the scopes needed for that action. See Updating Scopes for how to disconnect and reconnect with the required scopes.
Reference
For detailed information on the following topics, see the reference files:
- Registering New OAuth Providers - How to register a new OAuth provider that doesn't come with Vellum's defaults
- Configuring a New OAuth Application - How to configure a user-managed OAuth Application for providers whose mode is set to "your-own"
- Connecting Accounts - How to direct the user to log in and create a new OAuth connection
- Updating Scopes - How to update the scopes on an existing connection when additional permissions are needed
- Making Requests on Behalf of the User - How to make requests and take actions on behalf of the user once they have connected their account
© vellum-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 35 other files (references) in skills/vellum-oauth-integrations of vellum-ai/vellum-assistant.
- SKILL.md
- references/CONFIGURING_APPLICATIONS.md
- references/CONNECTING_ACCOUNTS.md
- references/MAKING_REQUESTS.md
- references/REGISTERING_PROVIDERS.md
- references/UPDATING_SCOPES.md
- references/provider-app-setups/airtable-path-b.md
- references/provider-app-setups/airtable.md
- references/provider-app-setups/asana-path-b.md
- references/provider-app-setups/asana.md
- references/provider-app-setups/discord-path-b.md
- references/provider-app-setups/discord.md
- references/provider-app-setups/dropbox-path-b.md
- references/provider-app-setups/dropbox.md
- references/provider-app-setups/figma-path-b.md
- references/provider-app-setups/figma.md
- references/provider-app-setups/github-path-b.md
- references/provider-app-setups/github.md
- references/provider-app-setups/google-path-b.md
- … and 17 more
Open the folder on GitHubat commit 33cc983
Compare with similar skills
Vellum OAuth Integrations next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vellum OAuth Integrations this skillvellum-ai/vellum-assistant | 1.4k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Fortify Developmentcoollabsio/coolify | 63k | 4 repos | ~1.9k | Automated safety check: Pass | MIT | |
| OmniRoute Provider Managementdiegosouzapw/OmniRoute | 75k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Antipattern Preventiondoorkeeper-gem/doorkeeper | 5.5k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Cognitoitsmostafa/aws-agent-skills | 1.2k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Notion Worker Third-Party Auth Guidemakenotion/workers-template | 439 | 1 repos | ~3.5k | Automated safety check: Notes | MIT |
Similar skills
OmniRoute Provider Management
diegosouzapw/OmniRoute
Manages AI provider connections, API keys, OAuth flows and connection tests through OmniRoute's REST API across its 327-provider catalog.
Antipattern Prevention
doorkeeper-gem/doorkeeper
Avoid common Ruby and Rails antipatterns that degrade maintainability and performance.
Cognito
itsmostafa/aws-agent-skills
AWS Cognito user authentication and authorization service. An agent skill from itsmostafa/aws-agent-skills.
- Official
Notion Worker Third-Party Auth Guide
makenotion/workers-template
Decides whether a Notion Worker should use a brokered credential, a plaintext environment secret, or OAuth to authenticate against a non-Notion service.
Stripe Best Practices
kanchengw/cnllm
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…
More from vellum-ai/vellum-assistant
All 108 skills in this repoVellum GitHub App Setup
vellum-ai/vellum-assistant
Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity.
Discord App Setup
vellum-ai/vellum-assistant
Connect a Discord bot to the assistant via the Discord Gateway with guided application creation and intent configuration
Sentry App Setup
vellum-ai/vellum-assistant
Create and configure a Sentry internal integration so the assistant can manage issues, alerts, and releases under its own identity
Memory Corpus Ingest
vellum-ai/vellum-assistant
Ingest a large dataset into memory as a skimmed map. An agent skill from vellum-ai/vellum-assistant.
Plugin Builder
vellum-ai/vellum-assistant
A skill your agent uses when the user wants to build, scaffold, ship, or edit a Vellum plugin that bundles multiple surfaces (hooks, tools, skills, and more) into one installable package.
Slack App Setup
vellum-ai/vellum-assistant
Connect a Slack app to the Vellum Assistant via Socket Mode.
Related
Categories
Questions about Vellum OAuth Integrations
What does Vellum OAuth Integrations do?
Act on behalf of your user in any third-party software that supports OAuth 2.0. Vellum OAuth Integrations is an agent skill from vellum-ai/vellum-assistant.
When should I use Vellum OAuth Integrations?
Vellum OAuth Integrations fits situations like: tasks that involve OAuth and OpenID Connect.
How do I install Vellum OAuth Integrations in Claude Code?
Run `npx skills add vellum-ai/vellum-assistant --skill vellum-oauth-integrations -a claude-code`. Or copy the skill folder (skills/vellum-oauth-integrations in vellum-ai/vellum-assistant) into .claude/skills/vellum-oauth-integrations in your project. Claude Code loads it when a task matches its description.
How do I install Vellum OAuth Integrations in Codex?
Run `npx skills add vellum-ai/vellum-assistant --skill vellum-oauth-integrations -a codex`. Or copy the skill folder (skills/vellum-oauth-integrations in vellum-ai/vellum-assistant) into .agents/skills/vellum-oauth-integrations in your project. Codex loads it when a task matches its description.
Can I use Vellum OAuth Integrations in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vellum-ai/vellum-assistant --skill vellum-oauth-integrations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vellum-oauth-integrations, .gemini/skills/vellum-oauth-integrations, .github/skills/vellum-oauth-integrations and .opencode/skills/vellum-oauth-integrations in your project.
What does Vellum OAuth Integrations need to run?
Going by SKILL.md and its folder, Vellum OAuth Integrations needs the command-line tools its instructions call (jq). Compatibility (from SKILL.md): Designed for Vellum personal assistants.
Does Vellum OAuth Integrations access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vellum OAuth Integrations safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vellum OAuth Integrations use?
Vellum OAuth Integrations is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vellum OAuth Integrations use?
About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 37k tokens, read only when the agent opens those files.
What are the alternatives to Vellum OAuth Integrations?
Skills that share tags, products or a category with Vellum OAuth Integrations: Fortify Development (coollabsio/coolify, 63k stars), OmniRoute Provider Management (diegosouzapw/OmniRoute, 75k stars), Antipattern Prevention (doorkeeper-gem/doorkeeper, 5.5k stars) and Cognito (itsmostafa/aws-agent-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vellum OAuth Integrations?
vellum-ai (a GitHub organization) maintains it in vellum-ai/vellum-assistant, which has 1,408 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.
Source: vellum-ai/vellum-assistant on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.