request-debugger

HTTP request/response debugging and inspection tools

509 stars

Best use case

request-debugger is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

HTTP request/response debugging and inspection tools

Teams using request-debugger should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/request-debugger/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/specializations/sdk-platform-development/skills/request-debugger/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/request-debugger/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How request-debugger Compares

Feature / Agentrequest-debuggerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

HTTP request/response debugging and inspection tools

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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

```yaml
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