Name: golang-gopls
Rating: 73.6 (1 reviews)
Author: samber

golang-gopls

Golang semantic code intelligence via `gopls`, the official Go language server — go-to-definition, find references, call/implementation hierarchy, workspace symbol search, package API discovery, diagnostics, safe rename, refactors (extract/inline/fill/rewrite code actions), formatting, and generated tests. Reaches an agent via gopls's own MCP server (`go_*` tools), Claude Code's native `LSP` tool, or the `gopls` CLI. Use when navigating or refactoring Go code — jumping to a definition, finding call sites before a rename, understanding a file's or package's dependencies, running diagnostics after an edit, or extracting/inlining/renaming. Not for the published ecosystem — packages not in your `go.mod`, versions, licenses, importers — → See `samber/cc-skills-golang@golang-pkg-go-dev` skill (`godig`). Not for a whole-tree vulnerability audit → See `samber/cc-skills-golang@golang-security` skill (`govulncheck`).

Quality

92%

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

Quality

Content

92%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 tight, highly operational body: concrete tool names, fully sequenced read/edit workflows with mandatory validation and feedback loops, and clean one-level-deep references. Only slight conciseness loss from re-stating skill boundaries already covered by the description.

Suggestions

Trim the 'gopls vs godig vs Context7 vs govulncheck' section to a one-line pointer, since the description already carries the same boundary guidance.

Dimension	Reasoning	Score
Conciseness	Dense and operational with minimal padding and no basic-concept explanation, but the 'gopls vs godig vs Context7 vs govulncheck' section repeats boundary guidance already in the description — a minor trim opportunity.	4 / 5
Actionability	Concrete commands and named tools throughout ('claude mcp add gopls -- gopls mcp', 'go install ...gopls@latest', go_workspace, go_search, go_diagnostics, go_vulncheck, 'go test <changed-package-paths>') — fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	Sequenced read (4-step) and edit (7-step) workflows with explicit mandatory validation checkpoints and feedback loops — 'go_diagnostics on every changed file — mandatory', re-run after fixes, vulncheck only after diagnostics are clean.	5 / 5
Progressive Disclosure	Overview body with well-signaled, one-level-deep markdown links to real reference files (mcp.md, cli.md, matrix.md, features.md); detail appropriately split out, easy to navigate.	5 / 5
	Total	19 / 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.

An excellent description: concrete capability list, explicit use-when triggers, and explicit boundaries against two sibling skills. The only soft spot is trigger-term naturalness, which leans on LSP jargon and skips the .go extension.

Suggestions

Add the '.go' file extension and the phrase 'Go files' to the trigger clause so users who say 'find references in my .go files' land here.

Soften one or two LSP terms (e.g. 'call/implementation hierarchy' → 'call graph / interface implementations') to match how users actually phrase these requests.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'go-to-definition, find references, call/implementation hierarchy, workspace symbol search, package API discovery, diagnostics, safe rename, refactors (extract/inline/fill/rewrite), formatting, and generated tests' — comprehensive coverage matching the 5 anchor.	5 / 5
Completeness	Explicitly answers what ('Golang semantic code intelligence via gopls' with a capability list) and when (concrete 'Use when navigating or refactoring Go code — ...' trigger phrases).	5 / 5
Trigger Term Quality	Strong natural trigger phrases ('navigating or refactoring Go code', 'jumping to a definition', 'finding call sites before a rename') but leans on LSP jargon ('call/implementation hierarchy', 'workspace symbol search') and omits the .go file extension.	4 / 5
Distinctiveness Conflict Risk	Clear niche (the locally resolved build) with explicit boundary guidance redirecting to the godig and govulncheck sibling skills — minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: skills/golang-gopls/SKILL.md
Commit: 19a0626

Reviewed: 1 day 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.