integration-error-observability SKILL.md skillA
integration-error-observability from samber/developer-platform-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/developer-platform-skills/integration-error-observability@v1.0.3Pins v1.0.3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/developer-platform-skills
- Path
skills/integration-error-observability/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.3, committed Oct 25, 2026
- First version recorded
- Aug 31, 2026
- Size
- 28,283 bytes
- Repository stars
- 9
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Integration Error Observability You are designing what an external developer can find out about their own broken integration, without opening a support ticket. The deliverable is a visibility surface plus a notification practice: logs and dashboards scoped to one integrator, correlation identifiers that survive into support, per-integration error aggregation, and the rules for when the platform reaches out first. The asymmetry is the whole problem. When a partner's integration fails, the platform usually knows first and knows more - it holds the request, the status code, the delivery attempt and the timestamp - while the partner holds only a silent queue and an angry customer. Every design decision below either closes that gap or leaves the partner reverse-engineering your platform from the outside. …
Read the whole file at its exact version.
How to install
mdr add samber/developer-platform-skills/integration-error-observability@sha256:6015aa8b72ad386fThe line at the top of this page pins the label v1.0.3, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kokxr2md6hcuu4kz)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 31, 2026 and Oct 25, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.3 latest | 2026-10-25 | 4e87402 | 28,283 B | A | view · diff |
| v1.0.2 | 2026-10-24 | ef50f0b | 28,277 B | A | view · diff |
| v1.0.1 | 2026-09-27 | 3f8efdb | 28,050 B | A | view · diff |
| v1.0.0 | 2026-08-31 | 5e9c352 | 27,647 B | A | view · diff |
| v1.0.0 | 2026-08-31 | 6b1056c | 27,648 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (28283 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
samber/developer-platform-skills · 9 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kokxr2md6hcuu4kz GET https://markdownregistry.com/api/v1/resolve?ref=samber/developer-platform-skills/integration-error-observability GET https://markdownregistry.com/api/v1/blob/6015aa8b72ad386f6bc4ed9ef00e3c71cefa24a505f2d1a51b151d185a439212
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.