CtrlK
BlogDocsLog inGet started
Tessl Logo

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 `samber/cc-skills-golang@golang-benchmark` skill) or applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill).

72

Quality

88%

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

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

The body is a well-structured overview with concrete commands, a clear sequenced workflow with red-flag feedback loops, and clean one-level-deep references to 10 verified files. The main lever is tightening repeated root-cause maxims and surfacing a few more executable commands inline.

Suggestions

Consolidate the repeated 'no fixes without root cause' messaging so it appears once (e.g., in Rule 5) rather than restated in the intro and Red Flags, to tighten conciseness.

Inline one or two concrete Delve/GODEBUG example commands in the body's escalation guidance so actionability does not depend solely on the reference files.

Consider a short 'verify the fix' checkpoint line in the Golden Rules (beyond the decision-tree summary) to make the validate-fix-retry loop explicit in the body itself.

DimensionReasoningScore

Conciseness

Dense, directive prose that assumes Go knowledge and a compact decision tree, but the no-root-cause/maxim themes are restated across the intro, rule 5, and the Red Flags section, leaving minor tightening possible.

4 / 5

Actionability

Concrete commands appear in the decision tree (go build, GOTRACEBACK=all, go test -race, curl pprof endpoint, dlv install), but much of the body is methodology/principle with executable detail deferred to reference files, leaving minor gaps.

4 / 5

Workflow Clarity

A clear numbered workflow (decision tree → golden rules → methodology → red flags → incremental escalation) with explicit recovery feedback loops ('3+ fix attempts → re-read code', 'each fix reveals a new problem → return to Step 1').

5 / 5

Progressive Disclosure

The body is an overview that one-level-deep references 10 verified reference files, each clearly signaled with a one-line description in the Reference Files section, with no nested references.

5 / 5

Total

18

/

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.

The description is precise, third-person, and explicitly covers both what the skill does and when to use it, with strong negative boundary guidance to sibling skills. Trigger term coverage is strong though not exhaustive of every synonym.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — root-cause fixing, debugging methodology, pprof setup/capture, Delve, race detection, GODEBUG tracing, production debugging — giving comprehensive coverage, matching the 5 anchor.

5 / 5

Completeness

Explicitly answers what (troubleshoot and find/fix root cause, with covered topics) and when ('Use when encountering bugs, crashes, deadlocks...'; 'Start here for any something is wrong situation') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural symptom terms like 'bugs, crashes, deadlocks, or unexpected behavior in Go code' and 'something is wrong' are good, but a few natural synonyms/variations are missing relative to the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Clear Go-troubleshooting niche reinforced by explicit negative boundary guidance pointing benchmarking and optimization to separate skills, giving minimal conflict risk.

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.

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