Integration Health Monitoring
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 \"integration health\". Not for migrating off another vendor's API. Do NOT use for live error dashboards (samber/developer-platform-skills@integration-error-observability), deprecation policy (samber/developer-platform-skills@api-versioning-policy) or key expiry design (samber/developer-platform-skills@api-auth-key-management).
Security AStatic scan found no risk patternsHow grading works ›
From the source SKILL.md
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.
What this skill does
Integration Health Monitoring is a community-contributed Claude Code skill in the crypto-keymgmt sub-category. It ships as a SKILL.md file that Claude Code auto-discovers under ~/.claude/skills/integration-health-monitoring/ and loads when your prompt matches the skill's trigger.
When to invoke it: 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 \"integration health\". Not for migrating off another vendor's API.
Who uses this skill
The Integration Health Monitoring Claude Code skill is built for security engineers, penetration testers, DevSecOps practitioners, and development teams hardening codebases and infrastructure. It's part of ClaudSkills (also referred to as Claude Skills or Claude Code Skills) — the open community-curated registry of 213,000+ SKILL.md files for Anthropic's Claude Code agent and the wider Claude ecosystem (Claude API, Claude Agent SDK).
How to install
Free
Manual install (2 steps)
mkdir -p ~/.claude/skills/integration-health-monitoring
curl -L https://claudskills.com/skills/integration-health-monitoring/SKILL.md \
-o ~/.claude/skills/integration-health-monitoring/SKILL.md
Or just download SKILL.md directly and drop it into ~/.claude/skills/integration-health-monitoring/. Claude Code auto-discovers it on next session.
Skills live at ~/.claude/skills/integration-health-monitoring/SKILL.md on macOS/Linux, or %USERPROFILE%\.claude\skills\integration-health-monitoring\SKILL.md on Windows. See the full install guide for step-by-step instructions.
Telegram
📱 Install from your phone or desktop Telegram
Open @claudskills_bot on Telegram, tap Open Desktop App, and the desktop app installs this skill for you. Or share the bot link with a colleague — they get the same one-tap install. Learn more →
Pro
One-click install via the desktop app
The ClaudSkills desktop app installs any skill directly into ~/.claude/skills/ with one click — no terminal required. Pro starts at $9/mo or $149 lifetime.
Pro
For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.
Frequently asked questions
How do I install the Integration Health Monitoring Claude Code skill?
Install via the ClaudSkills desktop app (one click) or copy
SKILL.md from the source repository to
~/.claude/skills/integration-health-monitoring/SKILL.md and restart Claude Code. Both flows are detailed at
claudskills.com/install/.
What does the Integration Health Monitoring skill do?
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 \"integration health\". Not for migrating off another vendor's API. Do NOT use for live error dashboards (samber/developer-platform-skills@integration-error-observability), deprecation policy (samber/developer-platform-skills@api-versioning-policy) or key expiry design (samber/developer-platform-skills@api-auth-key-management).
Is this skill free to install?
Yes. ClaudSkills is an open registry — every skill keeps its source repository's license, and manual install via copy is free. ClaudSkills Pro ($9/mo, $79/yr, or $149 one-time) adds one-click install via the desktop app and a multi-signal Quality Score.
When should I use the Integration Health Monitoring skill?
Use Integration Health Monitoring when your Claude Code task falls under the Security category — specifically in the crypto keymgmt area. Claude Code auto-discovers installed skills and invokes the right one based on the task description, so you can also ask Claude directly (e.g. "use Integration Health Monitoring" or describe the task and let Claude pick). Browse related skills at
/category/security/.
What is a Claude Code skill and how does the Integration Health Monitoring skill fit in?
A Claude Code skill is a
SKILL.md file that lives under
~/.claude/skills/<name>/ and tells the Claude Code CLI agent how to perform a specific task (instructions, prompts, allowed tools). Skills are auto-discovered at session start. Integration Health Monitoring is one of 67,000+ skills indexed in the open ClaudSkills catalog, classified under the Security category. Learn more at
/learn/what-is-a-claude-skill/.
Attribution & license
Cite this skill
If you reference this skill in a blog post, paper, or documentation, you can cite it as:
APA
samber. (2026). Integration Health Monitoring [Claude Code skill]. ClaudSkills. https://claudskills.com/skills/integration-health-monitoring/
BibTeX
@misc{integration-health-monitoring-2026,
author = {samber},
title = {Integration Health Monitoring [Claude Code skill]},
year = {2026},
publisher = {ClaudSkills},
url = {https://claudskills.com/skills/integration-health-monitoring/}
}
Embed this skill
Promote, attribute, or link this skill from your own README, blog post, or documentation. All three snippets are free to use — no sign-up, no API key. More distribution surfaces →
Badge
[](https://claudskills.com/skills/integration-health-monitoring/?utm_source=badge&utm_medium=readme&utm_campaign=skill_badge)
<script>
<script src="https://claudskills.com/embed/integration-health-monitoring.js" async></script>
<iframe>
<iframe src="https://claudskills.com/embed/integration-health-monitoring.html" width="100%" height="160" frameborder="0" loading="lazy" title="ClaudSkills: Integration Health Monitoring"></iframe>
Security scan
Grade A · scanned 2026-11-01 — free static scan against the OWASP Agentic Skills Top 10.
No risk patterns were found in any of the ten OWASP-aligned categories. How grading works ›
- ✓ Prompt injection
- ✓ Data exfiltration
- ✓ Supply chain
- ✓ Reverse shell
- ✓ Credentials
- ✓ Execution
- ✓ Filesystem
- ✓ Persistence
- ✓ Obfuscation
- ✓ Network
Show this grade on your repo (click to copy):
[](https://claudskills.com/skills/integration-health-monitoring/#security)
More Security skills
Browse all Security skills in the ClaudSkills registry, or explore these other picks from the same category:
Part of Acreator Store — Adam Lankamer's AI tools:
PerfectStudio ·
Ucaption ·
UTagger ·
AutoXPoster ·
TestYourSkills ·
AutomationFlows ·
Au Naturel ·
Telegram @acreatorstore