Babysitter request-debugger
HTTP request/response debugging and inspection tools
install
source · Clone the upstream repo
git clone https://github.com/a5c-ai/babysitter
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/specializations/sdk-platform-development/skills/request-debugger" ~/.claude/skills/a5c-ai-babysitter-request-debugger && rm -rf "$T"
manifest:
library/specializations/sdk-platform-development/skills/request-debugger/SKILL.mdsource content
Request Debugger Skill
Overview
This skill implements comprehensive HTTP request/response debugging and inspection tools for SDKs, helping developers understand and troubleshoot API interactions.
Capabilities
- Log request/response details with formatting
- Redact sensitive data automatically
- Correlate logs with request IDs
- Support curl command export for reproduction
- Implement request timing breakdowns
- Capture retry attempts and failures
- Support HAR (HTTP Archive) export
- Enable request/response interception
Target Processes
- Error Handling and Debugging Support
- Logging and Diagnostics
- Developer Experience Optimization
Integration Points
- HTTP client interceptors
- Logging frameworks
- Debug proxies (Charles, mitmproxy)
- Browser DevTools protocols
- IDE debug integration
Input Requirements
- Redaction rules for sensitive data
- Logging level configurations
- Timing breakdown requirements
- Export format preferences
- Interception capabilities
Output Artifacts
- Debug interceptor middleware
- Request logger implementation
- Sensitive data redactor
- Curl command generator
- HAR exporter
- Timing breakdown utilities
Usage Example
skill: name: request-debugger context: logging: enabled: true level: debug prettyPrint: true redaction: headers: ["Authorization", "X-Api-Key"] body: ["password", "secret", "token"] features: curlExport: true harExport: true timingBreakdown: true retryLogging: true requestIdHeader: "X-Request-ID"
Best Practices
- Always redact sensitive data
- Include timing breakdowns
- Support reproducible curl export
- Log retry attempts with reasons
- Use structured logging format
- Enable selective debug activation