developer-troubleshooting-docs Skill (samber): Error Docs

Makes Claude turn support tickets and error logs into troubleshooting pages that developers find by pasting the error text.

Installs: 12.4K; on skills.sh
Stars: 7; on GitHub
Files: 6; besides SKILL.md
Updated: Nov 2026; last repo commit

developer-troubleshooting-docs works in ten steps. It collects evidence from tickets, issues and error telemetry, clusters it, decides for each cluster whether to document or fix the product, picks an entry shape, writes each entry with six parts, and suggests generating the error catalog from one source of truth. It then verifies entries, makes pages findable, sets a target and plans maintenance.

Claude can run scripts/error-cluster.py, which groups exported tickets into ranked clusters. SKILL.md says it is not for debugging a live incident and names docs-seo for search ranking.

Good for

Technical writers who answer the same support question every week
Developer-tool teams documenting error codes
Support leads building a known-issues page from tickets

Install developer-troubleshooting-docs

Claude Code

Copy this prompt.

Install the developer-troubleshooting-docs skill in Claude Code. Run this command:

/plugin marketplace add samber/developer-relations-skills
/plugin install developer-relations-skills@developer-relations-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.

Install the whole set, not one skill: the README says the skills reference each other, so picking one leaves those pointers going nowhere. The repo tree holds 93 skill folders. Fourteen of them bundle .py or .sh files; developer-troubleshooting-docs bundles one, scripts/error-cluster.py. The tree holds no hooks, agents or MCP config files.

From the project README. Source.

What's in the skill

When it loads

Turns support tickets, issue history and error telemetry into troubleshooting and error-reference pages a developer finds by pasting the error string - symptom, conditions, cause, fix and verification entries, an error-code catalog generated from one source of truth, and fixes wired back into the product's own error output. Use whenever the user mentions troubleshooting docs, documenting error codes, error message pages, a known-issues page, building an FAQ from support tickets, or "we answer the same question every week" - even if they only say "users keep hitting this error". Not for debugging a live incident. Do NOT use for docs search ranking - use samber/developer-relations-skills@docs-seo.

Sections in SKILL.md

Named methods this skill runs on
Interview
Step 1 - Collect the evidence
Step 2 - Cluster and rank
Step 3 - Gate each cluster on document-versus-fix
Step 4 - Choose each entry's shape
Step 5 - Write the entry
Step 6 - Generate the catalog instead of hand-maintaining it
Step 7 - Verify before publishing
Step 8 - Make the page findable
Step 9 - Set the target and measure
Step 10 - Maintain
Invocation examples and expected output
Failure modes
References

Key facts

Author: Samuel Berthe (named in SKILL.md metadata and plugin.json)
License: MIT (SKILL.md, plugin.json and the LICENSE file agree)
Version: 1.0.2 (SKILL.md metadata)
Installs on skills.sh: 12,379 (Nov 2, 2026)
GitHub stars: 7 for the whole samber/developer-relations-skills repo (Nov 2, 2026)
Last repo commit: Nov 1, 2026
What it includes: 7 files in the git tree including SKILL.md. 1 Python script.
Needs: SKILL.md lists nothing to install. The bundled scripts/error-cluster.py needs python3 and imports only the standard library
Part of: The developer-relations-skills plugin: 93 skill folders in the git tree
Works in: Claude Code, Claude.ai, Codex, Cursor and Gemini CLI, as the README documents

What it includes

Names four published frameworks so the choices can be checked
Read · Named methods
Questions 1-4 gate the work
Read · Interview
Takes exports from reported and unreported sources
Read · Step 1: collect evidence
Groups raw records into one cluster per failure
Runs scripts/error-cluster.py on your exported files; by hand over about 50 records if it cannot.
Runs code · Step 2: cluster and rank
Gates each cluster on whether the product should stop emitting the error
Read · Step 3: document or fix
Chooses a shape for each entry by what the reader arrives with
Write · Step 4: entry shape
Six parts in order, ending with verification
Write · Step 5: write the entry
Recommends one machine-readable source for code and docs
Write · Step 6: generate the catalog
Reproduce the failure, run the fix as written, and have a cold reader follow it
Read · Step 7: verify
Pages are built for people who paste the error string
Write · Step 8: make it findable
Sets expectations against a published ceiling
Write · Step 9: target and measure
Re-runs the clustering pass after publication and compares
Runs code · Step 10: maintain
Normalizes paths, IDs and numbers, then ranks clusters by record count
Reads CSV, JSON, JSONL or text files, or stdin, and prints TSV or JSON.
Runs code · error-cluster.py

From the official docs

Permissions

Low risk

developer-troubleshooting-docs is planning instructions plus one script, and it may save notes to devrel-context.md. Our advice: check that file before you commit it.

What it can do

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

Watch out for

It may save notes to devrel-context.md
SKILL.md tells Claude to keep task and project context in devrel-context.md when memory lives in a file, or in the memory system your tool already uses. Check the file before you commit it. github.com
It can run a Python script on your exports
error-cluster.py opens the files you name (or stdin), extracts error-like text and prints clusters. Tickets can hold customer details, so check what you export. github.com
Verification means running commands
Step 7 says to reproduce the failure and run the fix exactly as written. Review those commands before you let Claude run them on a real machine. github.com
The whole-set install adds 93 skills, 14 with scripts
The README says to install every skill. The git tree has 93 skill folders and 14 of them hold .py or .sh files. The tree holds no hooks, agents or MCP config files. github.com

Technical details

Turning on read-only	SKILL.md describes no read-only mode.
Sign-in and keys	SKILL.md names no account, key or token.
Scopes	Claude writes the plan or report in the conversation May save notes to devrel-context.md when memory lives in a file Can run python3 scripts/error-cluster.py on files you export Step 7 has Claude reproduce failures and run fixes as written

Questions

What does developer-troubleshooting-docs do?

It makes Claude turn support tickets, issue history and error telemetry into troubleshooting pages. Each entry has symptom, conditions, cause, fix and verification, and developers find it by pasting the error string.

How do I install it?

Use the install box at the top. The README says to install every skill in the repo because the skills point to each other, so the box shows whole-set routes.

Does it need Python?

Only for the optional clustering script. SKILL.md gives a by-hand pass over roughly the top 50 records for when you cannot run it. The script is run with python3.

Does it generate an error-code catalog?

It recommends generating the catalog from one machine-readable source that both the product and the docs read. It frames that as a one-off engineering task, not a docs task.

Can it help debug an outage right now?

No. Its description says it is not for debugging a live incident.

Is it safe to install?

Claude can run one Python script on exported ticket files you give it, and SKILL.md has Claude reproduce failures and run fixes as part of verification. Claude may also save notes to a devrel-context.md file. See the permissions section.

Information

updated Nov 2, 2026

Repository: samber/developer-relations-skills
Folder: skills/developer-troubleshooting-docs

samber/developer-relations-skills skills.sh

Sources

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

Show all 7

README · github.com
marketplace.json · github.com
plugin.json · github.com
developer-troubleshooting-docs SKILL.md · github.com
LICENSE · github.com
skills.sh listing · skills.sh
developer-troubleshooting-docs scripts/error-cluster.py · github.com