Agent skill · software engineering · jeremylongshore
klingai-debug-bundle
Set up logging and debugging for Kling AI API integrations. Use when
Why this skill is useful
Adds a complete logging and debugging client for Kling AI API integrations, including structured logging and request tracing scripts.
What it needs
Requires npm installed locally. Requires kling-ai account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Kling AI Debug Bundle Overview Structured logging, request tracing, and diagnostic tools for Kling AI API integrations. Captures request/response pairs, task lifecycle events, and timing metrics for every call to https://api.klingai.com/v1. Debug-Enabled Client Usage Structured Log Entry Format Quick Diagnostic Script Task Inspector Prerequisites A non-production or approved staging account, a bounded diagnostic budget, and synthetic or rights-cleared media for reproduction. Do not debug with customer images or identifiable people unless the incident owner has documented consent. A secret manager for Kling credentials and a redaction policy covering JWTs, access keys, source URLs, prompts, masks, output URLs, and provider response bodies. A private, access-controlled log sink with a short retention period, plus an owner-approved canary and rollback procedure before any replay or regeneration. Instructions 1. Reproduce only with a synthetic or rights-cleared fixture in staging, and assign a correlation ID before making a request. 2. Apply redaction to request bodies, response bodies, exception text, headers, URLs, prompts, and generated-media references before logging or exporting a bundle. 3. Use bounded polling and retry budgets. Do not replay a policy rejection, exceed the approved credit budget, or replay a request against an unapproved destination. 4. Keep diagnostic output private and watermarked until the incident owner approves it. Quarantine generated media, remove temporary links, and restore the prior approved artifact if a replay changes state. 5. Verify log deletion at the retention deadline and retain only the aggregate, redacted receipt needed for incident follow-up. Output Produce a redacted diagnostic bundle containing a correlation ID, endpoint path, HTTP status, latency, retry count, opaque task ID, policy result, budget result, and a hash of relevant fixtures. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/klingai-debug-bundle--82c697