CtrlK
BlogDocsLog inGet started
Tessl Logo

golang-popular-libraries

Golang library and framework selection — vetted production-ready options by category (web, database, testing, logging, messaging), new and experimental stdlib packages, standard-library-first tradeoffs, and maturity signals (maintenance, license, importer counts). Apply when the user 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. Not for a specific library's API once chosen (→ See that library's dedicated skill, e.g. `samber/cc-skills-golang@golang-samber-lo`), nor for go.mod mechanics, upgrades, or vulnerability audits (→ See `samber/cc-skills-golang@golang-dependency-management` skill).

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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-organized advisory skill with strong progressive disclosure and a clear recommendation workflow. Slightly motivational prose and reliance on external pointers (rather than inline code) keep conciseness and actionability just below the top anchor.

DimensionReasoningScore

Conciseness

Lean prose that assumes Go competence and avoids explaining basics; not 5 because the 'Core Philosophy' bullets and the 'Remember: The best library is often no library at all' line are mildly motivational rather than strictly load-bearing.

4 / 5

Actionability

Gives concrete, executable guidance — 'Use a module's imported-by count on pkg.go.dev', named tools (godig, gopls), 'prefer it over Context7'; not 5 because the body itself contains no copy-paste code or commands, relying on pointers to reference files and sibling skills.

4 / 5

Workflow Clarity

A clear numbered recommendation sequence (assess → check stdlib → prioritize maturity → consider complexity → think about dependencies) with a 'MUST check' pre-recommendation gate; not 5 because there are no explicit validate→fix→retry feedback loops, though none are strictly required for this advisory skill.

4 / 5

Progressive Disclosure

Body is a concise overview pointing to three real, well-labeled one-level-deep reference files (stdlib.md, libraries.md, tools.md), plus clearly signaled '→ See' cross-references to sibling skills — easy to navigate with no nesting.

5 / 5

Total

17

/

20

Passed

Description

92%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, specific description with explicit 'what' and 'when' guidance and clear boundary carve-outs against sibling skills. Trigger term coverage is good but could add a few more natural synonyms.

DimensionReasoningScore

Specificity

Lists concrete selection scope — 'vetted production-ready options by category (web, database, testing, logging, messaging)' plus explicit maturity signals ('maintenance, license, importer counts') — covering multiple specific categories; not merely 4 because coverage is comprehensive rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both what (selection of vetted options, stdlib packages, maturity signals) and when ('Apply when the user asks for library suggestions...'), with concrete trigger phrases plus explicit 'Not for' boundaries.

5 / 5

Trigger Term Quality

Includes natural phrases users say ('library suggestions', 'compare alternatives', 'choose a library for a specific task', 'new dependency is being added'); not 5 because some common synonyms (e.g. 'which package', 'best Go library for X') are absent.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (library/framework selection) and explicitly distinguishes it from sibling skills via 'Not for... → See' boundaries, minimizing conflict risk.

5 / 5

Total

19

/

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.