Samuel BertheCreator of Go library lo, 21k+ GitHub stars580 installs on skills.shDeveloper Troubleshooting Docs
Turns support tickets, issue history and error telemetry into troubleshooting and error-reference...
3 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
From the samber public repository. Edge did not write or edit this skill.
What it does
- 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.
Why Samuel Berthe
Go open source author. Each fact links its public source.
- Created samber/lo, 21k+ stars
His Lodash-style Go generics library lo has 21k+ GitHub stars.
GitHub - Packaged in Ubuntu
lo ships as an Ubuntu source package, golang-github-samber-lo.
Ubuntu packages - 3k+ stars on his Go skills
His Golang agent skills collection has 3k+ GitHub stars.
GitHub
Public sources, checked Oct 26, 2026.
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads Developer Troubleshooting Docs.
3 static scans, 0 counted findings.
Security state at 2026-09-30: reviewed. Static scans check the code, not how well the skill works.
State definitionsSkill details
Security scansReviewed
3 static scans, 0 counted findings. Security state at 2026-09-30: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.1. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: .
Cisco skill-scanner (Edge-run): cisco-skill-scanner/2.1.0. Scope: Local static, YARA, pipeline and behavioral analyzers; no LLM or AI Defense analysis. Raw findings: 1.
Semgrep Edge rules (Edge-run): semgrep/1.178.0+edge-rules.c15016a36fd3+offline-v1. Scope: Six Edge-authored static rules with Semgrep CE; offline execution and metrics disabled. Semgrep-maintained rules excluded. Raw findings: .
- Edge static checks
- Pass · 0 counted findings · 2026-09-27
- Cisco skill-scanner
- Pass · 0 counted findings · 2026-09-27
- Semgrep Edge rules
- Pass · 0 counted findings · 2026-09-27
Creator, source & licencesamber
From the samber public repository. Edge did not write or edit this skill.
- Repository
- samber/developer-relations-skills
- Skill file
- View source at revision
- Revision
- 693ce4f68cefbff4667f0e279d37bb4345763c9a
- Package hash
- sha256:de54871527f7b86cc7c315a313452986f70d526caded5bf26b873eed4364ad74
- Licence
- MIT
- Description
- 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.
Quoted from the skill’s own description
Questions about Developer Troubleshooting Docs
What does Developer Troubleshooting Docs do?
Turns support tickets, issue history and error telemetry into troubleshooting and error-reference... Published by Samuel Berthe (samber/developer-relations-skills).
Is Developer Troubleshooting Docs safe to use?
Edge security state: Reviewed (3 Edge-run static scans, scanned Sep 30, 2026). The Evidence tab shows the scan.
How do I use Developer Troubleshooting Docs in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.
Similar skills

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow re…

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;`/page/<token>…

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or…

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when draft…

Read and write Google Docs.

Builds a pre-negotiation concession plan for a pricing or contract conversation - every tradeable lever priced by cost-to-us vs value-to-the…

Build a knowledge base from web content with Firecrawl. Use for local reference docs, RAG-ready chunks, fine-tuning datasets, documentation…