Help partners diagnose failures before opening a ticket.
What it does
Designs integration-scoped logs, dashboards, identifiers, and notification rules so external developers can diagnose failures without opening support tickets.
When to use it
Use for developer-facing error dashboards, exposing request logs to integrators, notifying partners about broken integrations, or reducing integration support tickets.
How to use it
Give it an integration-visibility problem; it asks clarifying questions and develops a design for diagnostic surfaces and partner notifications.
Good to know
- edits its own instructions
What you need · 2
Coordinates error-payload design, including whether an identifier appears in the body, with this sibling skill; an installation requirement is unstated.
Hands off quota design and rate-limit headers while retaining responsibility for surfacing 429 errors; an installation requirement is unstated.
Access · 1
This skill
the agent's persistent memory
Stores design decisions in memory