メニュー
Diagnoses API timeouts, identifies slow components via tracing, and provides retry/timeout strategies. DO NOT use for network infrastructure, DB query optimization, or general profiling.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | api-timeout-debugging |
| description | Diagnoses API timeouts, identifies slow components via tracing, and provides retry/timeout strategies. DO NOT use for network infrastructure, DB query optimization, or general profiling. |
| version | 1.1.0 |
| time_saved | Manual: 1–3 hours | With skill: 15–30 minutes |
| license | Proprietary — Personal Use Only |
| category | debugging |
| complexity | Intermediate |
| tokens | ~3500 |
| tags | ["api","timeout","retry","tracing","debugging","http"] |
| author | vheins |
Diagnose API timeouts using trace data to identify slow components and implement remediation strategies (retries, breakers, budget adjustments).
| Variable | Type | Req | Description |
|---|---|---|---|
tech_stack | string | Yes | e.g., "Node.js + Axios + Express" |
timeout_symptoms | string | Yes | Endpoint, duration, frequency, user impact |
trace_data | string | No | Distributed trace or span timings |
context | string | Yes | Arch, downstream deps, config, recent changes |
| Case | Strategy |
|---|---|
| No Trace Data | Activate OTel setup path; provide manual timing templates. |
| Expected Slowness | Recommend transition to async jobs with polling/webhooks. |
| Cascading Timeouts | Identify root service; implement decreasing timeout budgets downstream. |
flowchart TD
A[tech_stack + timeout_symptoms + context] --> B{Trace data available?}
B -- No --> C[Add OpenTelemetry / manual timestamps]
C --> D[List timeout config points to check]
B -- Yes --> E[Classify Timeout Type]
E --> F[Identify Slow Component]
F --> G[Root Cause Analysis]
G --> H[Apply Fix: timeout values + retry + circuit breaker]
H --> I[Before/After Code]
D --> J[Output: Diagnostic Path + Recommendations]
I --> K[Output: 5-Section Report + Monitoring Alerts]
@upstash/context7-mcp: Library documentation and examples.| Version | Date | Description |
|---|---|---|
| 1.1.0 | 2026-03-20 | Restructured: examples/ and references/, added compatibility/license |
| 1.0.0 | 2026-03-20 | Initial release |