Request debugger

Skill a5c-ai/babysitter/library/specializations/sdk-platform-development/skills/request-debugger

Babysitter enforces obedience on agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration

Install

npx -y skills add a5c-ai/babysitter --skill request-debugger

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

HTTP request/response debugging and inspection tools

SKILL.md

2.2 KB, as published. Nobody here has run it

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