API Request Logger Skill for Structured Redaction Checks
Log duration, status, a clean path, and a correlation ID. Use synthetic markers to verify that query values and credentials stay out of logs.
中文Install in Claude Code
Use your local API, a structured logger, and test output you can capture. Use synthetic request identifiers and values.
- Get the complete `plugins/api-development/api-request-logger/skills/logging-api-requests` directory from the pinned GitHub commit.
- Copy it into the target project's `.claude/skills/`. Check `.claude/skills/logging-api-requests/SKILL.md`, start Claude Code at the project root, and call `/logging-api-requests`.
Example task
Call /products/mug-01?label=synthetic-private with a dummy authorization marker. Compare the response and log correlation IDs and inspect the logged status and duration.What to check
The JSON log includes requestId, clean path, status, and timing. Neither synthetic private value appears.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should I log the entire request object?
Allow only intended fields and add redaction tests. Complete request objects can include query data or credentials.