tapauth

Create and retrieve OAuth tokens for multiple providers via browser approval.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/tapauth/skill --skill tapauth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tapauth
Source: https://github.com/tapauth/skill/tree/main
Command: npx skills add https://github.com/tapauth/skill --skill tapauth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Enables AI agents to obtain and manage user OAuth tokens without handling credentials, reducing risk and complexity in credential management.

Core Features & Use Cases

  • Create and approve per-provider grants via a simple CLI workflow
  • Retrieve tokens securely through a browser-based consent flow with in-memory usage
  • Integrate with OpenClaw's exec secrets provider for startup-time token resolution across multiple providers (GitHub, Google, Gmail, Linear, Notion, Vercel, Sentry, Asana, Discord, Slack, Apify)

Quick Start

Run scripts/tapauth.sh google calendar.readonly to create a grant and show the approval URL to the user.

Frequently Asked Questions about tapauth

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

FAQPage Schema
How do AI agents obtain OAuth tokens without handling user credentials?

AI agents obtain OAuth tokens by delegating authorization through a browser-based consent flow. This process creates per-user grants, allowing agents to retrieve and manage tokens securely without ever touching raw passwords or client secrets.

What is the process for creating a per-user OAuth grant for Google?

Creating a per-user OAuth grant involves running a CLI script that specifies the provider and scope, like Google calendar.readonly. This generates a unique approval URL for the user to authorize the agent's access in their browser.

Can I use OAuth token delegation with Slack, Notion, and Linear?

Yes, OAuth token delegation works with Slack, Notion, and Linear. The system supports multiple providers including GitHub, Google, Gmail, Vercel, Sentry, Asana, Discord, and Apify for creating per-user authorization grants.

Do I need curl installed to manage OAuth tokens via browser approval?

Yes, curl is required to manage OAuth tokens via browser approval. It serves as the sole dependency for executing the scripts that initiate the grant creation and token retrieval workflow.

How are retrieved OAuth tokens cached for in-memory usage by agents?

Retrieved OAuth tokens are cached using a persistent token cache mechanism. This allows AI agents to access them in-memory during execution, ensuring secure usage without repeatedly prompting the user for browser-based consent.

Does this OAuth workflow support startup-time token resolution for exec secrets?

Yes, this OAuth workflow supports startup-time token resolution by integrating with exec secrets providers. It uses absolute paths and safe polling to resolve tokens across multiple providers when the agent initiates.