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

73

Quality

92%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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 strong, well-structured debugging skill that provides clear decision-making guidance, actionable commands, and excellent progressive disclosure through reference files. The workflow is well-sequenced with explicit validation checkpoints (Red Flags, Golden Rules). The main weakness is moderate verbosity in some sections — the emphatic tone ('NO FIXES WITHOUT ROOT CAUSE', 'NEVER', 'IS NOT ACCEPTABLE') and some elaborated rules could be tightened without losing clarity.

DimensionReasoningScore

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 'Research the Codebase' rule is somewhat wordy. However, it generally respects Claude's intelligence and doesn't over-explain Go fundamentals.

2 / 3

Actionability

The decision tree provides specific, executable commands (go test -race, curl pprof endpoints, GOTRACEBACK=all). Golden Rules give concrete techniques (git bisect, fmt.Println, write a failing test). The dependency installation command is copy-paste ready. The guidance is specific and directly usable rather than abstract.

3 / 3

Workflow Clarity

The skill provides a clear sequential workflow: Decision Tree → Golden Rules → General Methodology → escalation path. The numbered steps (1-6) at the top are well-sequenced. The 'one hypothesis at a time' rule and Red Flags section serve as validation checkpoints. The escalation guide (fmt.Println → logging → pprof → Delve) is explicit. The dual-mode approach (single-issue vs codebase hunt) is clearly delineated.

3 / 3

Progressive Disclosure

Excellent progressive disclosure with a concise overview in SKILL.md and 10 well-described reference files covering specific topics. Each reference file has a clear one-line description of what it contains and when to use it. References are one level deep and clearly signaled. Cross-references to other skills are well-organized at the bottom.

3 / 3

Total

11

/

12

Passed

Description

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 developers would actually say, explicitly states both what it does and when to use it, and carefully delineates its boundaries from related skills with cross-references. The negative scope boundaries ('Not for interpreting profiles...') are particularly effective for reducing conflict risk.

DimensionReasoningScore

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. Very comprehensive enumeration of capabilities.

3 / 3

Completeness

Clearly answers both 'what' (troubleshoot Go programs, find and fix root cause, covers specific tools and methodologies) and 'when' (explicit 'Use when encountering bugs, crashes, deadlocks, or unexpected behavior'). Also includes helpful negative boundaries directing users to related skills.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'bugs', 'crashes', 'deadlocks', 'unexpected behavior', 'something is wrong', 'Go code', 'Golang', 'debugging', 'pprof', 'Delve', 'race detection'. These are terms developers naturally use when encountering issues.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with explicit boundary-setting: clearly states it is NOT for interpreting profiles/benchmarking or optimization patterns, and cross-references the specific alternative skills. The focus on troubleshooting/debugging Go code is a clear niche.

3 / 3

Total

12

/

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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