CtrlK
BlogDocsLog inGet started
Tessl Logo

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).

72

Quality

89%

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

78%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-structured troubleshooting skill: lean overview, copy-paste decision-tree commands, sequenced methodology, and clean one-level-deep references that all resolve. The main weakness is mild editorial padding in the Golden Rules and behavioral (rather than executable) validation checkpoints.

Suggestions

Tighten the Golden Rules rationales: drop or shorten editorial sentences like 'rushing leads to cascading failures that take longer to resolve' and the band-aid resurface explanation so each rule stays one line.

Add one or two concrete executable validation checkpoints to the main workflow (e.g. an explicit 'go test ./... must pass before declaring fixed' step) to push workflow_clarity toward explicit validation rather than behavioral stop-signals.

Surface 1-2 inline minimal reproductions or one-line command examples for the highest-frequency categories (nil pointer, race) so the body is self-sufficient for the most common cases without requiring a reference hop.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's intelligence (no basic-concept explanations), but a few rule rationales are editorial padding — e.g. 'rushing leads to cascading failures that take longer to resolve' and the band-aid resurface explanation — that could be trimmed.

4 / 5

Actionability

The Quick Decision Tree gives copy-paste commands (e.g. 'go build ./... 2>&1', 'GOTRACEBACK=all ./app', 'curl localhost:6060/debug/pprof/goroutine?debug=2'), but most Golden Rules are behavioral guidance and the bulk of executable detail is deferred to reference files, leaving minor gaps inline.

4 / 5

Workflow Clarity

A clear 6-step numbered process and sequenced Golden Rules with a Red Flags feedback loop ('stop and return to Step 1') are present, but the checkpoints are behavioral rather than executable validation steps, so it sits just below the explicit-validate anchor.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with a decision tree and a dedicated Reference Files section; all 10 referenced files (methodology, common-go-bugs, pprof, etc.) exist and are one level deep with clear, descriptive signaling.

5 / 5

Total

17

/

20

Passed

Description

100%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.

An exemplary description: third-person voice, concrete capabilities, natural trigger terms, and explicit what/when guidance with clear boundaries against sibling skills. No meaningful gaps to address.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas — 'debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging' — giving comprehensive coverage rather than vague abstractions.

5 / 5

Completeness

Explicitly answers both what ('Troubleshoot Golang programs systematically - find and fix the root cause') and when ('Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrasing is covered with synonyms — 'bugs, crashes, deadlocks, races, or unexpected behavior' plus the colloquial "'something is wrong' situation" — matching what a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Go troubleshooting) with explicit 'Not for...' boundary guidance redirecting benchmarking, optimization, and design to sibling skills, minimizing wrong-skill triggering.

5 / 5

Total

20

/

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
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.