32 skills · sorted by relevance
Configure OAuth 2.0 authorization for web and mobile apps or service communication. Choose suitable flows, implement PKCE to protect authorization codes, limit permissions, and manage token storage, renewal, and revocation with security checks.
Trace OAuth and OIDC sign-in flows in a CTF sandbox, from redirects through token exchange to application acceptance. Show where tokens become a recognized identity or permission, and preserve the smallest reproducible flow.
Choose an authentication flow for a Zoom integration, define scopes that control access, and understand token renewal. Use the reference examples and error tables to investigate failed authorization or token requests.
Build Zoom meeting features into native iOS apps with guidance on standard or custom interfaces, authentication, joining meetings, and starting them as a host. Reference materials also cover app lifecycle handling and troubleshooting.
Design authentication and access permissions for web apps, mobile apps, and backend services using OAuth 2.0 and OpenID Connect. Get guidance on authorization flows, token validation, secure storage, renewal, and revocation.
Assess authorized single sign-on systems using SAML, OIDC, and OAuth2. Map the login flow, check signatures, redirects, and token validation, then document reproducible findings and their impact, including identity or tenant confusion.
Build Zoom meeting features into native macOS apps, using either the default interface or a custom one. The skill guides authentication, host start and join flows, and meeting feature controls, with references for setup and troubleshooting.
Embed Zoom meetings in native Android apps with guidance on authentication, joining and starting meetings, and SDK integration. Begin with the default interface, then move to a custom interface once authentication, permissions, and meeting state changes are stable.
Fix OAuth PKCE "Session not found" or "No code verifier" errors in SPAs after redirect from external auth server. Use when: (1) OAuth callback fails with session/verifier not found despite flow starting correctly, (2) PKCE code_verifier stored in sessionStorage is missing after redirect back from auth server, (3) Error only happens in production or cross-origin redirects, not in local dev. Root cause: sessionStorage is lost when the browser opens a new tab, changes browsing context, or certain browsers clear it during cross-origin navigation. Fix: use localStorage instead (clean up after exchange).
The English summary is being prepared. Showing the original description.
Configure secure OAuth 2.0 authorization flows including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant. This skill covers flow selection, PKCE implementation, token
The English summary is being prepared. Showing the original description.
Configure secure OAuth 2.0 authorization flows including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant. This skill covers flow selection, PKCE implementation, token
The English summary is being prepared. Showing the original description.
Configure secure OAuth 2.0 authorization flows including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant. This skill covers flow selection, PKCE implementation, token
The English summary is being prepared. Showing the original description.
Connect a remote Hermes gateway to MCP servers that require OAuth, a browser-based authorization process. The skill covers dashboard access, manual token setup when needed, and diagnosis of expired tokens or revoked sessions.
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for OAuth, OIDC, redirect flows, state or nonce handling, PKCE, token exchange, refresh logic, claim mapping, and accepted login paths. Use when the user asks to trace redirects, callback parameters, scopes, state, nonce, PKCE, refresh tokens, consent, or explain how an OAuth or OIDC chain turns into accepted identity or privilege. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
The English summary is being prepared. Showing the original description.
Design and build Apify integrations for workflow platforms, AI agents, AI frameworks, or applications. Follow guidance for authentication, asynchronous cloud task execution, result retrieval, spending limits, error handling, testing, and release preparation.
Make your local gbrain accessible to other devices and cloud agents through MCP, a connection interface for AI tools. Set up Tailscale access, assign limited permissions to each client, configure authentication, and verify connections.
Adds user authentication to web and mobile apps with Amazon Cognito (user pools and identity pools) and the AWS Amplify client auth libraries. Covers sign-up/sign-in flows and the login page (Cognito-hosted UI / managed login), MFA, password policies, OAuth 2.0 / OIDC flows (auth-code + PKCE, client credentials), social/SAML federation, tokens (ID/access/refresh, rotation, revocation, storage), Cognito Lambda triggers, identity pools (temp AWS creds), and gating API Gateway (or ALB) routes to signed-in users via Cognito/JWT authorizers. Applies when adding a login or sign-up page, configuring a user pool or app client, choosing user pool vs identity pool, wiring social/SAML, refreshing tokens, requiring sign-in on an API Gateway or ALB, or debugging redirect_uri/token/MFA/CORS/federation errors. Does NOT cover Amplify Gen2 backend definitions (defineAuth, npx ampx → aws-amplify), IAM/STS/Identity Center (→ aws-iam), or API Gateway/Lambda resource config beyond the authorizer (→ aws-serverless).
The English summary is being prepared. Showing the original description.
Authentication and authorization patterns including OAuth2, JWT, RBAC, session management, and PKCE flows
The English summary is being prepared. Showing the original description.
OAuth and OIDC misconfiguration testing playbook. Use when reviewing redirect URI handling, state and nonce validation, PKCE, token audience, callback binding, and identity-provider trust flaws.
The English summary is being prepared. Showing the original description.
Emulated Microsoft Entra ID (Azure AD) OAuth 2.0 / OpenID Connect for local development and testing. Use when the user needs to test Microsoft sign-in locally, emulate Entra ID OIDC discovery, handle Microsoft token exchange, configure Azure AD OAuth clients, work with Microsoft Graph /me, or test PKCE/client credentials flows without hitting real Microsoft APIs. Triggers include "Microsoft OAuth", "Entra ID", "Azure AD", "emulate Microsoft", "mock Microsoft login", "test Microsoft sign-in", "Microsoft OIDC", "local Microsoft auth", or any task requiring a local Microsoft OAuth/OIDC provider.
The English summary is being prepared. Showing the original description.
OIDC flows, PKCE implementation, token refresh strategies, social login integration, and secure session management.
The English summary is being prepared. Showing the original description.
OAuth 2.0 and OpenID Connect authentication with secure flows. Use for third-party integrations, SSO systems, token-based API access, or encountering authorization code flow, PKCE, token refresh, scope management errors.
The English summary is being prepared. Showing the original description.
Implement OAuth 2.0 authentication flows including authorization code with PKCE, client credentials, and device code for secure API integration. Use when the user requests oauth 2 0 setup or provides relevant inputs for this workflow.
The English summary is being prepared. Showing the original description.
Automate Canva from an agent — via the AI Connector MCP server (generate, find, edit, export designs in natural language) or the Connect REST API (OAuth 2.0 + PKCE, brand template autofill, asset uploads, exports, folders, comments). Use when: connecting an agent to Canva, batch-producing social posts or decks from a brand template and a spreadsheet, exporting designs to PDF/PNG/PPTX/MP4, uploading assets into a Canva account, building a Canva integration, or when the user mentions "Canva", "brand template", "autofill", "Connect API", or "mcp.canva.com".
The English summary is being prepared. Showing the original description.