oauth-setup

Automate OAuth onboarding for Google and Meta accounts in ppc-manager.

3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/anthril/official-claude-plugins --skill oauth-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oauth-setup
Source: https://github.com/anthril/official-claude-plugins/tree/main/plugins/ppc-manager/skills/oauth-setup
Command: npx skills add https://github.com/anthril/official-claude-plugins --skill oauth-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end OAuth onboarding for Google (GTM, GA4, Google Ads) and Meta accounts within the ppc-manager plugin, enabling secure, encrypted token vault integration and seamless multi-account setup.

Core Features & Use Cases

  • Browser-based OAuth flows for Google and Meta accounts, including token exchange and vault storage.
  • Phase-driven setup including Google prerequisites, account linking, and token validation, suitable for fresh installs and refresh scenarios.
  • Use Case: You install ppc-manager for the first time and need to connect multiple Google and Meta accounts, then validate and normalise tokens across the vault.

Quick Start

Run the oauth-setup flow to connect your Google and Meta accounts and store the credentials securely.

Frequently Asked Questions about oauth-setup

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

FAQPage Schema
How do I set up OAuth for Google and Meta accounts in ppc-manager?

The OAuth setup process handles Google GTM, GA4, and Ads alongside Meta ads by using browser-based flows and local loopback redirects. It applies to fresh installations, multi-account expansions, and token refresh workflows.

Can I connect multiple Google and Meta accounts during initial OAuth onboarding?

The setup uses local loopback redirects and vault encryption to securely capture and store tokens for each connected account. This ensures encrypted token vault integration across all linked Google and Meta profiles.

Do I need to manually refresh OAuth tokens for Google Ads and Meta ads?

Token validation runs via token_validator.py to check credential integrity across the vault. It normalizes tokens and confirms a consistent ok-status summary for all connected Google and Meta accounts.

What is the best way to validate OAuth tokens after connecting Google and Meta accounts?

Browser-based OAuth flows handle token exchange directly with Google and Meta APIs. The system then applies vault encryption and local loopback redirects to securely store and validate the resulting tokens.

Why does OAuth setup use local loopback redirects for Google and Meta authentication?

OAuth setup uses local loopback redirects to securely capture authentication tokens during the browser-based exchange process. This approach ensures tokens are directly encrypted into the vault without exposing credentials to external endpoints.