integration-health-monitoring SKILL.md skillA
integration-health-monitoring 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-health-monitoring@v1.0.0Pins v1.0.0 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-health-monitoring/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 24, 2026
- Size
- 23,498 bytes
- Repository stars
- 9
- License
- MIT
Find third-party integrations on your platform that will break on a known date - version drift, deprecated-endpoint usage, SDK end of life, expiring or dormant credentials - reach their owners, and decide when a deprecated surface is safe to turn off. Use whenever the user mentions version drift, who still calls a deprecated endpoint, partners on old API versions, chasing integrations before a sunset, brownouts, or retiring an API surface third parties call, even without saying…
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 Health Monitoring You are finding the integrations that work today and will break on a date you already know - a sunset, an SDK end of life, a credential expiry, a payload-version retirement - and getting each one's owner to move first. The deliverable is a census that names every integration at risk and the person who can fix it, a notification loop that reaches that person, and a gate that says when it is safe to turn the old surface off. Integrations failing right now belong to `samber/developer-platform-skills@integration-error-observability`. The deprecation policy itself - notice windows, headers, fall-forward or hard cutoff - belongs to `samber/developer-platform-skills@api-versioning-policy`. This skill executes that policy one integration at a time. The recurring failure is counting calls instead of owners. A sunset at "99% of traffic migrated" still breaks every integration in the remaining 1%, and the providers who broke them could not say who they were or how to reach them. ## Interview Ask before building anything. Batch them: this is an operational task, not a strategy interview. …
Read the whole file at its exact version.
How to install
mdr add samber/developer-platform-skills/integration-health-monitoring@sha256:877ffe472daa839cThe line at the top of this page pins the label v1.0.0, 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_iz27w2q6yk7njf4w)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 24, 2026.
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 (23498 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_iz27w2q6yk7njf4w GET https://markdownregistry.com/api/v1/resolve?ref=samber/developer-platform-skills/integration-health-monitoring GET https://markdownregistry.com/api/v1/blob/877ffe472daa839cfaaba61671bf6f5c7999299968f5618bab52edfc41dcf626
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.