菜单
Debugs authentication token errors (JWT validation, OAuth token issues, expiry, signature, refresh flows). Do NOT use for CORS, session auth, or authorization logic.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | authentication-token-debugging |
| description | Debugs authentication token errors (JWT validation, OAuth token issues, expiry, signature, refresh flows). Do NOT use for CORS, session auth, or authorization logic. |
| version | 1.1.0 |
| time_saved | Manual: 1-3h | With skill: 10-20m |
| license | Proprietary — Personal Use Only |
| category | debugging |
| complexity | Intermediate |
| tokens | ~3500 |
| tags | ["jwt","oauth","token","authentication","debugging","security"] |
| author | vheins |
Diagnose and fix token-related failures including expiry, signature errors, and claim mismatches.
| Variable | Type | Req | Description |
|---|---|---|---|
tech_stack | string | Yes | e.g., "Node.js + jsonwebtoken" |
token_type | string | Yes | JWT, OAuth2, API Key, etc. |
error_message | string | Yes | e.g., "TokenExpiredError" |
token_payload | string | No | Decoded payload (omit sensitive data) |
httpOnly cookies, and explicit claim verification.| Case | Strategy |
|---|---|
| No Payload | Provide decode command; describe validation flow failure points. |
| Clock Skew | Recommend clockTolerance settings in validation libraries. |
| Key Rotation | Recommend JWKS endpoint integration for dynamic keys. |
flowchart TD
A([Start: Token Debugging]) --> B[Parse inputs]
B --> C{Payload available?}
C -- No --> D[Provide decode command]
D --> E[Describe validation flow]
C -- Yes --> F[Classify Error]
F --> G{Type?}
G -- TokenExpired --> H[Check exp vs now/clock skew]
G -- InvalidSignature --> I[Verify keys/rotation]
G -- InvalidAud/Iss --> J[Update generation]
G -- RefreshExpired --> K[Implement rotation/revocation]
G -- Malformed --> L[Validate base64url/segments]
H & I & J & K & L --> M[Root Cause Analysis]
M --> N[Apply targeted fix]
N --> O[Security Hardening]
O --> P[Write tests]
P --> Q([Output: 5 Sections + Fix + Tests])
@upstash/context7-mcp: Library documentation and examples.| Version | Date | Description |
|---|---|---|
| 1.1.0 | 2026-03-20 | Restructured: moved examples, references, added compatibility/license |
| 1.0.0 | 2026-03-20 | Initial release |
Use to implement a REST or GraphQL API endpoint from a specification or description, including request validation, error handling, and accompanying tests. Activate for building a new API route, resolver, or handler end-to-end. Do NOT use for API design/contract creation, documentation generation, or frontend API consumption.
Use to implement background job processing with a queue, worker, retry with exponential backoff, dead letter queue, and monitoring. Activate when the request involves offloading work from the request cycle (emails, reports, data processing). Do NOT use for real-time event streaming, webhook handling, or scheduled cron jobs.
Use to scaffold a new project from scratch — generating directory structure, configuration files, entry points, and a README skeleton. Activate when starting a new project, service, or package and needing a production-ready starting point. Do NOT use for adding features to existing projects, generating tests, or CI/CD configuration.
Use to design and implement a caching layer for data that is expensive to compute or fetch. Activate for cache-aside, write-through, or write-behind patterns, TTL strategy, and cache invalidation logic. Do NOT use for database query optimization, CDN configuration, or HTTP response caching headers.
Use to generate a CI/CD pipeline configuration for building, testing, and deploying an application. Activate for GitHub Actions, GitLab CI, CircleCI, or similar pipeline tools for any tech stack. Do NOT use for infrastructure provisioning, Dockerfile creation, or deployment strategy design.
Use to generate production-ready code for a new feature, function, class, or module from a description. Activate for writing new code from scratch with error handling, inline documentation, and a self-review checklist. Do NOT use for refactoring existing code, code review, or test generation.