golang-troubleshooting
Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve debugger, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (see golang-benchmark skill) or applying optimization patterns (see golang-performance skill).
92
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific concrete capabilities, uses natural trigger terms a developer would use when encountering Go issues, clearly states both what it does and when to use it, and explicitly differentiates itself from related skills by naming them. The boundary-setting with cross-references to golang-benchmark and golang-performance skills is particularly well done.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve debugger, race detection, GODEBUG tracing, and production debugging. | 3 / 3 |
Completeness | Clearly answers both 'what' (troubleshoot Go programs, find and fix root cause, covers specific tools and techniques) and 'when' (encountering bugs, crashes, deadlocks, unexpected behavior). Also explicitly delineates boundaries by referencing related skills for benchmarking and performance optimization. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'bugs', 'crashes', 'deadlocks', 'unexpected behavior', 'Go code', 'Golang', 'something is wrong', 'debugging', 'race detection'. These are highly natural phrases a user would use when encountering issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit boundary-setting: 'Not for interpreting profiles or benchmarking (see golang-benchmark skill) or applying optimization patterns (see golang-performance skill).' This cross-referencing to related skills significantly reduces conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured debugging skill with excellent progressive disclosure and actionability. The decision tree is immediately useful, the golden rules provide a strong methodological framework, and references are clearly organized. The main weakness is moderate verbosity — some motivational/emphatic language and repeated admonitions could be trimmed to improve token efficiency without losing clarity.
Suggestions
Tighten the Golden Rules section by removing motivational language ('There is no later', 'IS NOT ACCEPTABLE') and reducing explanatory text — Claude doesn't need to be convinced, just instructed.
Condense the Red Flags section into a compact checklist format rather than expanded bullet points with explanations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining basic Go concepts, but some sections are verbose — the Red Flags section, Golden Rules elaborations, and repeated emphasis on 'NO FIXES WITHOUT ROOT CAUSE' could be tightened. The persona/thinking mode preamble and some motivational language ('There is no later') add tokens without adding actionable value. | 2 / 3 |
Actionability | The decision tree provides concrete, executable commands for each symptom category (e.g., `GOTRACEBACK=all ./app`, `go test -race ./...`, `curl localhost:6060/debug/pprof/goroutine?debug=2`). The golden rules give specific techniques like `git bisect`, writing failing tests, and using `fmt.Println` vs `slog`. Guidance is concrete and directly usable. | 3 / 3 |
Workflow Clarity | The skill provides a clear sequential workflow: decision tree → golden rules → methodology reference. The numbered steps at the top (1-6) establish an explicit sequence with validation checkpoints ('reproduce before you fix', 'one hypothesis at a time', 'never propose a fix you cannot explain'). The Red Flags section serves as a feedback loop for detecting when the process has gone wrong. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: the main file is a concise overview with a decision tree and golden rules, while 10 clearly-described reference files handle detailed topics. Each reference is one level deep with a descriptive summary of what it contains. Navigation is well-signaled through both the decision tree links and the Reference Files section. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- samber/cc-skills-golang
- Commit
e9761db
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.