CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

golang-troubleshooting

Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill), applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill), or designing new code (→ See `samber/cc-skills-golang@golang-safety` skill for defensive coding, `samber/cc-skills-golang@golang-concurrency` skill for concurrency design).

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered skill body: an actionable decision tree front and center, terse but concrete rules, a built-in self-correction checklist, and a clean ten-file reference layer with accurate per-file summaries. Only minor trimming of duplicated statements (escalation and reproduce-first each appear twice) keeps it from full token efficiency.

DimensionReasoningScore

Conciseness

The body is efficient — no explanations of concepts Claude already knows, a compact symptom-to-command decision tree, and terse golden rules. It is not a 5 because of small redundancies: the escalation principle appears both as intro step 5 ("Escalate tools incrementally") and Golden Rule 7 ("Start Simple"), and "reproduce before you fix" is repeated across intro step 2 and Rule 2.

4 / 5

Actionability

The decision tree maps every common symptom to a copy-paste command — "go build ./... 2>&1, go vet ./...", "GOTRACEBACK=all ./app", "go test -race ./...", "curl localhost:6060/debug/pprof/goroutine?debug=2" — and the body includes concrete install ("go install github.com/go-delve/delve/cmd/dlv@latest") and analysis flags ("go build -gcflags=\"-m\""). This matches the fully-executable anchor with common cases covered.

5 / 5

Workflow Clarity

A clear six-step sequence opens the guide, the "Red Flags" section is an explicit feedback loop ("If any of these are happening, stop and return to Step 1"), and the cycle "Read the Error → Reproduce → Measure One Thing → Fix → Verify" gives a validation checkpoint. This matches the anchor for clear sequence with explicit validation, error-recovery loops, and a checklist; score 4 would require missing checkpoints, which are present.

5 / 5

Progressive Disclosure

The body is a genuine overview — decision tree, rules, red flags — and all ten reference files are one level deep, each cited with a one-sentence content summary in the Reference Files section and linked by symptom from the decision tree. Every referenced path was verified to exist and none nest further. This matches the clear-overview, well-signaled, one-level-deep anchor; it is above score 4, which permits organization gaps.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capability list, explicit use-when triggers in the user's natural vocabulary, and unusually good negative boundary guidance that routes adjacent tasks to sibling skills. The only gap is a handful of missing trigger synonyms (panic, hangs, flaky tests).

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — "debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging" — matching the anchor for comprehensive, specific concrete actions. It sits above the score-4 anchor (which allows minor coverage gaps) because the capability list spans the full debugging toolchain rather than a subset.

5 / 5

Completeness

Both halves are explicit: what ("Troubleshoot Golang programs systematically - find and fix the root cause" plus the capability list) and when ("Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code"). This matches the anchor that clearly answers what AND when with concrete trigger phrases; it cannot be lower since neither half is vague or implied.

5 / 5

Trigger Term Quality

Good natural trigger coverage — "bugs, crashes, deadlocks, races, or unexpected behavior" are phrases users genuinely say — plus the meta-trigger "any 'something is wrong' situation". It falls short of the score-5 anchor (comprehensive synonyms and file extensions) because common variations like "panic", "hang", "flaky test", or the `.go` extension are absent.

4 / 5

Distinctiveness Conflict Risk

A clear troubleshooting niche with explicit negative boundaries — "Not for interpreting profiles or benchmarking", "applying optimization patterns", "designing new code" — each redirecting to a named sibling skill. This is the minimal-conflict ideal; it is above score 4, which tolerates overlap with closely related skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

samber/cc-skills-golang

Path

skills/golang-troubleshooting/SKILL.md

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.