Loading...
Loading...
Found 11 Skills
Implement secure authentication bridge between Better Auth (Next.js frontend) and FastAPI (Python backend) using JWKS JWT token verification. Use this skill when users need to (1) Integrate Better Auth with FastAPI backend, (2) Implement JWT authentication with JWKS verification, (3) Set up user isolation and authorization in FastAPI endpoints, (4) Configure frontend to send authenticated API requests, or (5) Troubleshoot Better Auth + FastAPI authentication issues.
Verify and validate JSON Web Tokens (JWTs) by checking signatures, expiration, claims, and structure. Use when the user wants to verify, validate, or check a JWT — e.g. "verify this token", "is this JWT valid", "check the signature", "validate this token against my JWKS", "is this token expired". Supports HMAC, RSA, and ECDSA with secrets, PEM keys, or JWKS endpoints.
Implement OAuth 2.1 / OIDC authentication using Better Auth with MCP assistance. Use when setting up a centralized auth server (SSO provider), implementing SSO clients in Next.js apps, configuring PKCE flows, or managing tokens with JWKS verification. Uses Better Auth MCP for guided setup. NOT when using simple session-only auth without OAuth/OIDC requirements.
Clerk auth with API Keys beta (Dec 2025), Next.js 16 proxy.ts (March 2025 CVE context), API version 2025-11-10 breaking changes, clerkMiddleware() options, webhooks, production considerations (GCP outages), and component reference. Prevents 15 documented errors. Use when: API keys for users/orgs, Next.js 16 middleware filename, troubleshooting JWKS/CSRF/JWT/token-type-mismatch errors, webhook verification, user type inconsistencies, or testing with 424242 OTP.
Build production-grade FastAPI backends with SQLModel, Dapr integration, and JWT authentication. Use when building REST APIs with Neon PostgreSQL, implementing event-driven microservices with Dapr pub/sub, scheduling jobs, or creating CRUD endpoints with JWT/JWKS verification. NOT when building simple scripts or non-microservice architectures.
Use Prisma Next with a Supabase project via `@prisma-next/extension-supabase` — wire `extensions: [supabasePack]`, declare cross-space FKs to `supabase:auth.AuthUser`, author RLS policies (`policy_select` / `policy_update` / `@@rls`, `auth.uid()` predicates), build `db.ts` with the `supabase()` factory, bind roles per request (`asUser(jwt)` / `asAnon()` / `asServiceRole()`), query `auth.*` / `storage.*` via the `db.asServiceRole().supabase` admin root, and validate JWTs (`jwksUrl` for current projects / `jwtSecret` for legacy HS256). Use for supabase, RLS, row level security, policy, role binding, anon, authenticated, service_role, auth.users, auth.uid(), JWT, JWKS, SUPABASE_JWKS_URL, SUPABASE_JWT_SECRET, SUPABASE.JWT_INVALID, SUPABASE.CONFIG_INVALID, RoleBoundDb, session pooler, supabase:auth.AuthUser, @prisma-next/extension-supabase.
Turso Cloud — fully managed SQLite-compatible database platform, accessed over the network. Use when connecting an application to a Turso Cloud database, creating or scoping auth tokens (JWT, fine-grained permissions, JWKS/external auth providers), or provisioning and managing cloud databases. Covers per-language SDKs (JavaScript/TypeScript, Python, Go, Rust), authentication & authorization, and marketplace integrations (Vercel).
Configure the embedded Agentforce Employee Agent so it replies inside the Microsoft Teams ITSM custom client ('Salesforce Employee Assist' / 'Ask AI Agent'). Use this for: 'set up employee agent in Teams', 'embed Agentforce agent in Teams', 'make the IT Service Employee Agent reply in Teams', 'Teams Ask AI Agent not responding', 'agent joins then leaves without replying', 'configure MIAW deployment for Teams employee agent', 'Teams embedded messaging agent setup'. Builds the whole stack headlessly (zero Setup-UI clicks): the Web messaging channel with User Verification ON, the Enhanced Chat User Verification Key Set (JWKS_URL) it requires, the Teams_AgentForce custom-client deployment, the routing flow to the agent, and the Agent Access permission set that lets the portal user reach the agent. DO NOT TRIGGER for enabling the Teams feature Salesforce Go page toggle (service-itsm-teams-configure) or for configuring notification preferences.
Build and configure a GraphQL API backed by Neo4j using @neo4j/graphql v7 (current) or v5 (LTS). Covers Neo4jGraphQL constructor, getSchema(), assertIndexesAndConstraints(), type definitions with @node, @relationship (IN/OUT/UNDIRECTED), @cypher for custom resolvers, @authorization/@authentication for JWT/JWKS security, auto-generated queries/mutations, OGM programmatic access, subscriptions via CDC, and Apollo Federation. Use when writing typeDefs, securing fields, or wiring Neo4j to Apollo Server. Does NOT handle raw Cypher outside resolvers — use neo4j-cypher-skill. Does NOT cover Spring Data Neo4j entity mapping — use neo4j-spring-data-skill.
Use for the Twingate Identity Firewall (IDFW) and the Twingate Gateway — protocol-level identity enforcement for SSH, the Kubernetes API, AND self-hosted/internal web apps, not just network-level access. LOAD whenever the user wants to grant, secure, SSO into, or audit access to a self-hosted or internal web application — including forwarding or injecting the logged-in user's identity into HTTP requests, or a per-user/request-level audit trail of who accessed an app. This is the Gateway acting as a Layer 7 reverse proxy that injects signed ES256 JWTs (Gateway Access Tokens) or trusted headers into web apps: JWKS verification, request-header injection, framework middleware (Express, Django, Next.js, Auth.js), and no-code SSO integrations (Grafana, Jenkins). Also use when the user deploys the Gateway; configures SSH privileged access with short-lived certificates; manages privileged / vendor / contractor access; configures Certificate Authorities (X.509 or SSH CA, local or HashiCorp Vault); routes kubectl through the Gateway; automates IDFW with Terraform or Ansible; or implements/reviews session recording (asciicast/.cast playback and archival, scanning recorded SSH or kubectl sessions for dangerous commands or leaked secrets, self-hosting a recording browse UI). If a question is about identity-aware access to an app or host — "can Twingate pass the user's identity to my app?", "audit who used this app", "SSO for my internal tool" — assume this skill is relevant and load it.
Use for the Twingate Identity Firewall (IDFW) and Twingate Gateway — protocol-level identity enforcement for SSH, the Kubernetes API, AND self-hosted/internal web apps, not just network access. LOAD when the user wants to grant, secure, SSO into, or audit a self-hosted/internal web app — identity forwarding/injection into HTTP requests, per-request audit trails. Gateway = Layer 7 reverse proxy injecting ES256 JWTs (Gateway Access Tokens) or trusted headers: JWKS verification, request-header injection, framework middleware (Express, Django, Next.js, Auth.js), no-code SSO (Grafana, Jenkins). Covers Gateway deployment; SSH privileged access with short-lived certs; vendor/contractor access; Certificate Authorities (X.509/SSH CA, local or Vault); kubectl via the Gateway; Terraform/Ansible automation; session recording (.cast playback, scanning for dangerous commands/leaked secrets). Assume this skill for "can Twingate pass the user's identity to my app?", "audit who used this app", or "SSO for my internal tool".