credential-switch

Switch active brand credential profiles with validation and audit logging.

Updated May 18, 2026
One-click install
npx skills add https://github.com/ajayatwal1105-emerson/digital-marketing-pro --skill credential-switch-ajayatwal1105-emerson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: credential-switch
Source: https://github.com/ajayatwal1105-emerson/digital-marketing-pro/tree/main/skills/credential-switch
Command: npx skills add https://github.com/ajayatwal1105-emerson/digital-marketing-pro --skill credential-switch-ajayatwal1105-emerson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Switching between multiple brand clients can accidentally point requests at the wrong ad account or analytics workspace, causing misrouted spend, incorrect reporting, or cross-client data leakage.

Core Features & Use Cases

  • Multi-client credential switching with guardrails: Moves the active brand and active credential profile together so downstream MCP/platform operations use the correct client.
  • Quick or full validation of access: Checks env vars and token validity (quick mode) or performs live connectivity/token checks (full mode) before proceeding.
  • Operational safety checks: Detects in-progress executions that could be disrupted by a context switch and warns with specifics.
  • Audit-ready switch logging: Writes a timestamped entry to a switch log including previous/new brand, validation results, and any warnings for traceability.
  • Use case: An agency managing monthly reporting for Acme and running paid media for Beta can switch credentials, validate required integrations, and then generate accurate reports without risking cross-account actions.

Quick Start

Use credential-switch to switch to brand slug AcmeCorp and run quick validation by requesting: Switch brand credentials to AcmeCorp.

Frequently Asked Questions about credential-switch

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

FAQPage Schema
How do I switch API keys and OAuth tokens safely across multiple marketing clients?

Switching brand credentials safely involves moving the active brand and credential profile together atomically, ensuring downstream ad, analytics, or CRM platform operations use the correct client context and preventing cross-client data leakage.

What happens to in-progress executions when I switch brand context for multi-client agency workflows?

When switching brand context, operational safety checks detect in-progress executions that could be disrupted by the context switch and issue specific warnings to prevent misrouted spend or incorrect reporting.

How do I validate OAuth tokens before switching to a new client profile?

You can validate OAuth tokens using quick mode to check environment variables and token validity, or full mode to perform live connectivity checks, ensuring the new credential profile is active and functional before proceeding.

Does credential switching provide audit logging for multi-client ad and analytics operations?

Yes, credential switching writes a timestamped audit log entry capturing the previous and new brand, validation results, and warnings, providing full traceability for multi-client ad and analytics operations.

Can I use credential switching for scheduled reporting across different CRM and ad accounts?

Yes, credential switching is designed for scheduled reporting scenarios where API keys and tokens must match the selected brand context, allowing you to coordinate ad, analytics, and CRM operations across different client accounts safely.