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.

59

Quality

68%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/go-concurrency-patterns/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

Well-structured and concise, but the body offers no concrete Go-concurrency guidance — only generic boilerplate steps and a dangling reference. Actionability is the primary weakness.

Suggestions

Replace the generic Instructions bullets with concrete Go-concurrency actions (e.g., worker-pool snippet, context-cancellation pattern, `go test -race` verification).

Add a real validation/verification checkpoint tied to concurrency risk, such as running `go test -race` and checking goroutine leaks, instead of the abstract "validate outcomes".

Create the referenced `resources/implementation-playbook.md` (or fix the path) so the signaled reference resolves to an actual file.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation, but the generic Instructions bullets ("Clarify goals...", "Apply relevant best practices...") are boilerplate not fully earning their tokens.

4 / 5

Actionability

Guidance is almost entirely abstract ("Apply relevant best practices and validate outcomes", "Provide actionable steps and verification") with no concrete Go code, commands, or specific patterns — only a pointer to an external file.

2 / 5

Workflow Clarity

A rough generic sequence is listed and validation is named ("validate outcomes", "verification"), but checkpoints are abstract and the steps are non-specific scaffolding rather than a real concurrency workflow.

3 / 5

Progressive Disclosure

Section structure is clean and a one-level-deep reference is signaled, but the referenced `resources/implementation-playbook.md` does not exist in any bundle directory, breaking navigation.

3 / 5

Total

12

/

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 description that clearly states capability and usage triggers with concrete Go-concurrency terms. Minor room to convert "Master...with X" into discrete actions for full specificity.

DimensionReasoningScore

Specificity

Lists several concrete primitives ("goroutines, channels, sync primitives, and context") but frames them as things to "Master" rather than discrete executable actions, leaving minor coverage gaps versus the comprehensive-action anchor at 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 phrases users would say ("building concurrent Go applications", "worker pools", "debugging race conditions") with good coverage, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Go concurrency) with distinct, domain-specific triggers, giving minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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