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

89%

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

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 reference skill: a tight rule summary, a concrete decision table, one executable example, and clean one-level-deep references to real bundle files. The only weakness is light over-explanation in the intro and relying on references for most executable detail.

Suggestions

Trim the intro analogy ("Think of it as the 'session' of a request") and the rationale tails on a few summary rules; assume Claude already knows what context.Context is.

Add one or two more inline executable snippets for the most common patterns (e.g. WithTimeout defer-cancel, WithoutCancel for audit logging) so the body is actionable without requiring a reference hop.

Surface a brief "when in doubt" decision checklist tying the Creating Contexts table to the cancel()-on-all-paths rule, giving an explicit verify step for the leak-prone cases.

Dimension	Reasoning	Score
Conciseness	The 10-rule summary is lean and each rule's rationale is useful guidance rather than padding, but the intro analogy "Think of it as the 'session' of a request" and a few explanatory clauses (e.g. "the fixed position is what makes context-aware APIs recognizable at a glance") are mild over-explanation a competent reader doesn't need.	4 / 5
Actionability	Provides one complete, copy-paste-ready Go example (the bad/good propagation pair) and a concrete decision table naming exact API calls, but the body delegates most executable patterns to the reference files rather than showing them inline.	4 / 5
Workflow Clarity	Organization is clear and logically sequenced (summary → decision table → core principle with example → deep dives → cross-refs → linters), and the decision table acts as a selection flow; it is advisory rather than a destructive multi-step process, so the simple-skill path applies, though no explicit validate/verify checkpoint structure is present.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview with three well-signaled one-level-deep references — cancellation.md, values-tracing.md, http-services.md (all real files) — each with a descriptive blurb, plus cross-references to sibling skills; content is appropriately split and easy to navigate.	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: concrete capabilities, an explicit "Apply when" trigger clause with real scenarios, and a negative boundary that prevents false activation. Every dimension lands at the top anchor with no padding or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities — "propagation through API boundaries, cancellation, timeouts and deadlines, request-scoped values, context.WithoutCancel for background work outliving requests" — giving comprehensive coverage of the domain rather than generic actions.	5 / 5
Completeness	Explicitly answers both: what ("Idiomatic context.Context usage in Golang — ...") and when ("Apply when designing context propagation across layers, debugging leaked or unexpired contexts, choosing between context.Background/TODO/WithoutCancel, or storing values in context") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers the natural phrases a Go developer would say — "cancellation", "timeouts and deadlines", "leaked or unexpired contexts", "context.Background/TODO/WithoutCancel", "storing values in context" — including the specific API synonyms a user would name.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Go context.Context) with distinct triggers, and the negative boundary "Not for code that merely accepts ctx as first parameter" sharply reduces overlap with adjacent skills.	5 / 5
	Total	20 / 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: 19a0626

Reviewed: 1 day 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.