OpenParable
Skip to content
← Back to skills

Request Debugger

Testing & Quality
request-debugger

Request Debugger is an Agent Skill for testing & quality published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

HTTP request/response debugging and inspection tools

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/specializations/sdk-platform-development/skills/request-debugger/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/request-debugger, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

  1. Always redact sensitive data
  2. Include timing breakdowns
  3. Support reproducible curl export
  4. Log retry attempts with reasons
  5. Use structured logging format
  6. Enable selective debug activation