CtrlK
BlogDocsLog inGet started
Tessl Logo

golang-popular-libraries

Recommends production-ready Golang libraries and frameworks. Apply when the user explicitly asks for library suggestions, wants to compare alternatives, needs to choose a library for a specific task, or when a new dependency is being added to the project.

65

Quality

80%

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/golang-popular-libraries/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 recommendation skill that defers detail to three clearly signaled reference files and gives concrete decision guidance. The main gap is the absence of explicit validation checkpoints in the recommendation workflow, though the task is non-destructive.

Suggestions

Add an explicit validation step to the General Guidelines workflow (e.g., 'Before recommending, verify the candidate on pkg.go.dev: check imported-by count, latest release date, and known vulnerabilities') to turn the implicit vetting into a checkpointed sequence.

Dedupe the stdlib-first and pkg.go.dev cross-reference points that recur across Core Philosophy, General Guidelines, and Cross-References to tighten the body.

Add one short worked example of a recommendation decision (requirement → stdlib check → candidate vet → recommendation) to make the workflow fully concrete.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but repeats the stdlib-first and pkg-go-dev cross-reference points across Philosophy, Guidelines, and Cross-References; trimming that redundancy would reach the fully lean 5.

4 / 5

Actionability

Gives concrete decision criteria and specific tools (imported-by count, godig, gopls, Context7 fallback) rather than vague direction; minor gaps in worked examples keep it just below fully executable 5.

4 / 5

Workflow Clarity

General Guidelines lists a clear numbered sequence (assess → check stdlib → prioritize maturity → complexity → dependencies) but has no validation checkpoints, fitting the 'steps listed, checkpoints missing' anchor; this is a non-destructive recommendation skill so the destructive cap does not apply.

3 / 5

Progressive Disclosure

SKILL.md is a concise overview with well-signaled one-level-deep references to three real files (stdlib.md, libraries.md, tools.md) plus cross-references to sibling skills, with content appropriately split and easy to navigate.

5 / 5

Total

16

/

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 what it does and when to use it with natural trigger phrases, written in proper third person. It is distinctively scoped to the Go ecosystem with minimal conflict risk.

DimensionReasoningScore

Specificity

Names the domain (Golang libraries/frameworks) and several concrete actions — 'Recommends', 'compare alternatives', 'choose a library' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the comprehensive 5.

4 / 5

Completeness

Explicitly answers 'what' ('Recommends production-ready Golang libraries and frameworks') and 'when' with a concrete 'Apply when...' clause listing multiple trigger conditions, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users say ('library suggestions', 'compare alternatives', 'new dependency is being added') with good coverage; a few synonyms/extensions are missing so it sits just below the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

Clear Golang niche with distinct, specific triggers (library comparison, dependency addition) and minimal overlap risk with other skills, matching the top anchor.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
samber/cc-skills-golang
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.