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.

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/go-concurrency-patterns/SKILL.md

The canonical home for this skill is go-concurrency-patterns in rmyndharis/antigravity-skills

Quality

Content

36%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 thin, generic scaffold: it avoids verbosity but offers almost no executable guidance, real workflow sequencing, or validation. Its one progressive-disclosure reference is dangling because the referenced file is absent.

Suggestions

Add concrete, copy-paste-ready Go code examples for the core patterns (worker pool, pipeline, context cancellation) instead of relying on generic instruction bullets.

Create the referenced resources/implementation-playbook.md (note: the directory is 'resources/', not the conventional 'references/') or remove the dangling reference so navigation is not broken.

Replace the abstract instruction list with an explicit sequenced workflow that includes validation checkpoints (e.g., run `go test -race`, verify goroutine cleanup with leak detection) for the concurrency operations the skill covers.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not over-explain concepts Claude already knows, but generic platitudes like "Apply relevant best practices and validate outcomes" earn little of their token budget; it is efficient yet largely uninformative.	3 / 5
Actionability	Provides only high-level hints ("Clarify goals", "Provide actionable steps and verification") with no concrete code, commands, or specific patterns; the sole detailed-examples pointer references a non-existent file, leaving minimal executable guidance.	2 / 5
Workflow Clarity	The three-bullet instruction list is a rough, generic sequence with poorly defined steps and no validation checkpoints or concrete sequencing, matching the "many gaps, validation absent" anchor.	2 / 5
Progressive Disclosure	A single one-level-deep reference (resources/implementation-playbook.md) is clearly signaled under Resources, but the referenced file does not exist in the bundle, so the navigation is broken and cannot reach the good-structure anchor 4.	3 / 5
	Total	10 / 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.

The description is well-constructed: it states concrete capabilities, provides explicit trigger guidance, and carves out a distinct niche. The main weakness is the abstract verb "Master" and the absence of synonyms/file extensions, which keep specificity and trigger quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete sub-areas ("goroutines, channels, sync primitives, and context") but wraps them under the abstract verb "Master" rather than listing multiple distinct concrete actions, so it sits just below the comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both 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 terms a Go developer would say ("concurrent Go applications", "worker pools", "race conditions", "goroutines", "channels") with good coverage, though it omits synonyms/file extensions like ".go", keeping it below the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Go concurrency) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/go-concurrency-patterns/SKILL.md
Commit: 57c135b

Reviewed: 4 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.