CtrlK
BlogDocsLog inGet started
Tessl Logo

go-concurrency-patterns

Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.

57

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/go-concurrency-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

43%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 concise and sectioned but lacks any executable Go-concurrency guidance, relying on generic template instructions and a broken reference to a non-existent playbook. It reads as a placeholder rather than actionable skill content.

Suggestions

Add at least one concrete, copy-paste-ready Go example (e.g. a worker pool with context cancellation) so the skill is actionable without the external file.

Create resources/implementation-playbook.md or remove the dangling references in 'Instructions' and 'Resources'; a broken path undermines progressive disclosure.

Replace the generic 'Instructions' bullets with a concrete, ordered workflow (build → instrument with -race → validate → graceful shutdown) including validation checkpoints for race debugging and shutdown.

DimensionReasoningScore

Conciseness

The body is lean and free of concept explanations Claude already knows, but the generic 'Do not use this skill when' and template 'Instructions' bullets are boilerplate that could be trimmed; not a 5 because of that filler.

4 / 5

Actionability

No executable code, commands, or concrete Go-concurrency patterns are provided — only high-level hints like 'Apply relevant best practices and validate outcomes', and the one concrete pointer ('open resources/implementation-playbook.md') targets a file that does not exist.

2 / 5

Workflow Clarity

The four 'Instructions' bullets are unordered hints rather than a sequenced workflow, with no validation checkpoints or feedback loops despite covering fragile topics like race conditions and graceful shutdown.

2 / 5

Progressive Disclosure

Sections are well organized and the reference is clearly signaled one level deep, but the referenced path 'resources/implementation-playbook.md' is missing (no resources/ directory), so the disclosure does not actually resolve.

3 / 5

Total

11

/

20

Passed

Description

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

A strong, well-structured description that clearly states both capabilities and trigger conditions in third person. Minor keyword-coverage gaps keep specificity and trigger_term_quality just below full marks.

DimensionReasoningScore

Specificity

Names the Go-concurrency domain plus concrete primitives (goroutines, channels, sync primitives, context) and concrete actions (building worker pools, debugging race conditions); falls short of 5 because 'Master' is generic and some sub-areas (pipelines, shutdown) appear only as triggers.

4 / 5

Completeness

Explicitly answers 'what' ('Master Go concurrency with goroutines, channels, sync primitives, and context') and 'when' ('Use when building concurrent Go applications, implementing worker pools, or debugging race conditions') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases like 'worker pools', 'race conditions', 'goroutines', and 'channels'; not a 5 because synonyms (parallelism) and file extensions (.go) are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear Go-concurrency niche with distinct triggers; minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
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.