golang-context
Idiomatic context.Context usage in Golang — creation, propagation, cancellation, timeouts, deadlines, context values, and cross-service tracing. Apply when working with context.Context in any Go code.
86
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 a strong skill description that clearly identifies its domain (Go's context.Context), enumerates specific capabilities (creation, propagation, cancellation, timeouts, deadlines, values, tracing), and includes an explicit 'Apply when' trigger clause. It uses proper third-person voice and contains natural trigger terms that Go developers would use. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creation, propagation, cancellation, timeouts, deadlines, context values, and cross-service tracing. These are all distinct, well-defined operations related to context.Context. | 3 / 3 |
Completeness | Clearly answers both what ('Idiomatic context.Context usage — creation, propagation, cancellation, timeouts, deadlines, context values, and cross-service tracing') and when ('Apply when working with context.Context in any Go code') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'context.Context', 'Golang', 'Go code', 'cancellation', 'timeouts', 'deadlines', 'context values', 'tracing'. These cover the natural terms a developer would use when asking about Go context patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting context.Context in Go specifically. The combination of 'Golang', 'context.Context', and the enumerated sub-topics makes it very unlikely to conflict with other skills, even other Go-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent progressive disclosure and clear organization. Its main weakness is that the overview level is somewhat verbose (explaining what context.Context is) and lacks enough concrete code examples — most actionable content is deferred to reference files, leaving the main skill light on executable guidance. The best practices list is comprehensive but would benefit from being paired with more inline code snippets.
Suggestions
Remove or drastically shorten the opening paragraph explaining what context.Context is — Claude already knows this.
Add 1-2 more inline code examples for high-value patterns (e.g., WithTimeout with defer cancel, unexported context key type) rather than deferring all code to reference files.
Trim the deep dive descriptions to one-line summaries — the current paragraph-length descriptions add tokens without adding much navigational value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what context.Context is, which Claude already knows. The best practices summary is useful but some items are redundant (e.g., #6 and #8 overlap). The deep dive descriptions are somewhat verbose — they could be shorter link labels rather than full paragraph summaries. | 2 / 3 |
Actionability | There is one concrete code example (good vs bad propagation), but most guidance is rule-based without executable examples. The best practices list tells Claude what to do but doesn't show how for most items (e.g., context value keys, WithoutCancel, WithTimeout patterns). The detailed code is deferred to reference files. | 2 / 3 |
Workflow Clarity | This is a best-practices/pattern skill rather than a multi-step workflow skill. The single core principle (propagate context through the call chain) is unambiguous, the creation table clearly maps situations to actions, and the numbered rules provide clear sequencing guidance. No destructive or batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Excellent structure: concise overview with best practices summary and a quick-reference table at the top level, then clearly signaled one-level-deep references to three focused deep-dive documents, plus well-organized cross-references to related skills. | 3 / 3 |
Total | 10 / 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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
- Commit
b88f91d
- 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.