golang-context

Idiomatic context.Context usage in Golang — propagation through API boundaries, cancellation, timeouts and deadlines, request-scoped values, context.WithoutCancel for background work outliving requests. Apply when designing context propagation across layers, debugging leaked or unexpired contexts, choosing between context.Background/TODO/WithoutCancel, or storing values in context. Not for code that merely accepts ctx as first parameter.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%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, concise overview that defers detail to real reference files and sibling skills. Its main weakness is that the core guidance is a ruleset rather than an executable workflow with validation checkpoints.

Suggestions

Trim the introductory framing ('Think of it as the session of a request...') to push conciseness from 4 to 5, since Claude already understands context.Context.

Add a short, concrete worked example or checklist for a common end-to-end flow (e.g., HTTP handler → service → DB) with a verification step, to raise workflow clarity above 3.

Surface 1-2 inline code snippets for the highest-value patterns (e.g., WithTimeout with deferred cancel, unexported key types) so the most common actionable cases don't require opening a reference file.

Dimension	Reasoning	Score
Conciseness	Lean summary table, decision matrix, and a single bad/good code example with minimal padding; the opening 'session of a request' framing lightly re-explains a concept Claude knows, keeping it just below a 5.	4 / 5
Actionability	The 'Creating Contexts' decision table and the executable bad/good Go snippet give concrete guidance, while deeper actionable detail is appropriately deferred to the referenced deep-dive files; minor gaps remain inline.	4 / 5
Workflow Clarity	The 11-item best-practices summary is a clear sequenced checklist, but this is a ruleset rather than a multi-step workflow and lacks validation checkpoints; no destructive/batch cap applies, so it sits at the midpoint.	3 / 5
Progressive Disclosure	A clean overview in SKILL.md points via well-signaled 'Deep Dives' to three real one-level-deep reference files (cancellation.md, values-tracing.md, http-services.md), with cross-references to sibling skills for easy navigation.	5 / 5
	Total	16 / 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 specific, well-triggered, and clearly scoped, answering both what and when while explicitly drawing a boundary against misfiring. It is a strong, concise description with only minor room for additional synonymous trigger phrasings.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'propagation through API boundaries, cancellation, timeouts and deadlines, request-scoped values, context.WithoutCancel' — giving comprehensive coverage of what the skill addresses.	5 / 5
Completeness	Explicitly answers both what ('Idiomatic context.Context usage...') and when ('Apply when designing... debugging... choosing... or storing values in context') with concrete trigger phrases plus an explicit 'Not for...' boundary.	5 / 5
Trigger Term Quality	Strong natural triggers ('designing context propagation across layers', 'debugging leaked or unexpired contexts', 'choosing between context.Background/TODO/WithoutCancel') with good keyword coverage, though a few synonymous phrasings users might say are absent.	4 / 5
Distinctiveness Conflict Risk	A clear Go context.Context niche with distinct triggers and an explicit exclusion ('Not for code that merely accepts ctx as first parameter'), minimizing overlap with adjacent Go skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: samber/cc-skills-golang
Path: skills/golang-context/SKILL.md
Commit: 30cdf15

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.