integration-error-observability Skill (samber): Show Partners Their Errors

Makes Claude design what outside developers can see when their integration breaks: logs, correlation IDs, error rates and alerts.

Installs: 9.6K; on skills.sh
Stars: 9; on GitHub
Files: 5; besides SKILL.md
Updated: Nov 2026; last repo commit

integration-error-observability makes Claude design how a platform shows integration failures to the external developers and partners who built on it. It covers per-integration logs with replay, correlation IDs that reach support, error rates per API key or app, alert posture and a provider-side fleet view.

It starts when you mention a developer-facing error dashboard, exposing request logs to integrators, alerting partners about broken integrations, or cutting integration support tickets. Claude asks 8 opening questions, then works through 6 steps. The skill bundles no scripts.

Good for

Platform teams whose partners file tickets they could have answered from a log
Teams building a developer-facing request log
Partner engineers who need to see which apps are failing

Install integration-error-observability

Claude Code

Copy this prompt.

Install the integration-error-observability skill in Claude Code. Run this command:

/plugin marketplace add samber/developer-platform-skills
/plugin install developer-platform-skills@developer-platform-skills

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Pick one route, not both, or you get every skill twice. The README asks you to install the whole set, not just integration-error-observability, because the skills reference each other and a lone skill leaves those hand-offs with nowhere to go. The plugin adds all 61 skills in the repo (counted from the repo tree). Its manifests list no hooks, agents or MCP servers.

From the project README. Source.

What's in the skill

When it loads

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.

Sections in SKILL.md

Clarifying questions
Integration ownership
Workflow
1. Audit what an integrator can see today
2. Expose per-integration failure detail
3. Make the correlation ID reach support
4. Aggregate error rates per integration identity
5. Decide the notification posture
6. Build the provider-side fleet view
Failure modes
Measurement
Invocation examples
References

Key facts

Author: Samuel Berthe
License: MIT
Version: 1.0.3
Installs on skills.sh: 9,552 (Nov 2, 2026)
GitHub stars: 9 (Nov 2, 2026)
skills.sh audits: Gen Agent Trust Hub pass; Socket pass; Snyk pass (Nov 2, 2026)
Last repo commit: Nov 1, 2026
What installs: 6 files including SKILL.md: evals/evals.json and 4 reference files. It bundles no scripts.
Needs: The other skills in the repo; the README says to install the whole set
Works in: Claude Code, Claude.ai, Codex, Cursor, Gemini CLI, and other agents through the skills CLI

What it includes

Asks 8 questions in one batch before designing anything.
Try: “Our partners find out their integration is broken when their customers complain - design what we should be showing them.”
Opening questions
Checks the last 20 integration tickets for what integrators could have seen themselves.
Audit what an integrator can see today
Designs request, event and delivery logs per integration, with replay.
Expose per-integration failure detail
Carries the correlation ID from response header to support ticket.
Make the correlation ID reach support
Tags requests by API key or app at ingestion and splits 4xx from 5xx.
Aggregate error rates per integration
Ranks alert styles by value; a threshold alert with a cooldown ranks first.
Decide the notification posture
Gives your partner team a view ranked by blast radius, not raw error count.
Build the provider-side fleet view
Advises saving decisions to developer-platform-context.md when memory is a file.
Write · Remember decisions (optional)

From the official docs

Permissions

Low risk

This skill is written advice that bundles no scripts. The one thing it may write is a decisions file, so check what Claude saves.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It may save decisions to a file
SKILL.md advises using developer-platform-context.md when memory lives in a file, and calls it an advisory reference. Check or delete that file if you do not want decisions kept. github.com
The plugin route adds all 61 skills
The README asks you to install every skill in the repo, and the repo has 61. The plugin manifests list no hooks, agents or MCP servers, and the repo tree holds none. github.com
Folder holds Markdown and one JSON file
This skill's folder has 6 files: SKILL.md, evals/evals.json and 4 reference files. It has no .py, .sh or .js file. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Turning on read-only	No read-only setting is documented. Decline the memory-file suggestion if you want no files written.
Scopes	Asks you opening questions and works from your answers and anything you share, such as specs or docs May save settled decisions to a file named developer-platform-context.md if your memory lives in a file

Questions

How do I install integration-error-observability?

Use the install box above. The README asks you to install all 61 skills in the repo, not just this one, because the skills point to each other. In Claude Code that is the plugin route, and elsewhere the skills CLI or the client's own route installs the set.

Does integration-error-observability work in Claude.ai, Codex or Cursor?

The README documents installs for Claude.ai, Claude Code, Codex, Cursor and Gemini CLI. It also lists the skills CLI, which it calls universal for Agent Skills-compatible tools. The Claude.ai route adds the whole repo as a plugin marketplace.

Does it need an API key or any setup?

SKILL.md sets no environment variable and the folder bundles no scripts. It does ask for details of your own API or product in its opening questions.

Is integration-error-observability safe to use?

The folder holds Markdown and one JSON file, and no scripts. SKILL.md does suggest saving settled decisions to developer-platform-context.md when your memory lives in a file, so check what Claude writes. Our advice: treat the design it produces as a draft for your team to review before you publish it.

integration-error-observability vs api-status-communication?

This skill covers per-integration views of failures. SKILL.md sends platform-wide incident communication to api-status-communication.

Is this about my own internal monitoring?

It is about what external integrators and partners can see about their own failures. It starts the audit from your support tickets rather than an architecture diagram, and step 6 adds a separate view for your own partner and support teams.

Information

updated Nov 2, 2026

Repository: samber/developer-platform-skills
Folder: skills/integration-error-observability

samber/developer-platform-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6

README · github.com
integration-error-observability SKILL.md · github.com
integration-error-observability folder · github.com
api-status-communication SKILL.md · github.com
marketplace.json · github.com
plugin.json · github.com