samber/developer-platform-skills
integration-error-observability
Design how a platform surfaces integration failures to the external developers and partners who built against it - per-integration request/event/delivery logs with replay, correlation IDs that survive from response header to support ticket, error-rate aggregation per API key or app split by 4xx/5xx/429, proactive partner notification with cooldowns against alert fatigue, and a provider-side fleet view of which integrations are breaking. Use whenever the user mentions a developer-facing error dashboard, exposing request logs to integrators, alerting partners about broken integrations, or cutting integration support tickets - even if they never say "observability". Do NOT use for platform-wide incident comms - use samber/developer-platform-skills@api-status-communication instead.
Installation
npx skills add https://github.com/samber/developer-platform-skills
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Azure Observability Services including Azure Monitor, Application Insights, Log Analytics, Aler…
86.2K installsBuilds, configures, debugs, and optimizes AWS observability with CloudWatch (Log Insights, Metr…
51 installsRedis observability guidance — which metrics to monitor (memory, connections, hit ratio, ops/se…
17 installsThis skill should be used when the user wants to "set up tracing", "monitor my agent", "configu…
1.8K installsInstruments code so production behavior is visible and diagnosable.
846 installsGolang everyday observability — the always-on signals in production. Covers structured logging …
273 installsAlso in this package
Other skills from samber/developer-platform-skills · top by installs.
npx skills add samber/developer-platform-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.