effective-go

Apply Go best practices, idioms, and conventions from golang.org/doc/effective_go. Use when writing, reviewing, or refactoring Go code to ensure idiomatic, clean, and efficient implementations.

Quality

82%

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

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.

A concise, well-organized conventions skill that delegates detailed error-handling code to a one-level-deep reference file. It is held back only by minor redundancy with the description and the absence of inline code examples illustrating the rules.

Suggestions

Remove the duplicated intro sentence and "When to Apply" list (already in the description), and mention the effective_go URL once instead of three times.

Add one short contrasting code snippet (idiomatic vs. non-idiomatic) for the highest-value rules like naming or interface design to lift actionability.

Optionally sequence the application guidance (e.g. apply gofmt first, then check naming, then review error handling) to clarify workflow across the three trigger activities.

Dimension	Reasoning	Score
Conciseness	Lean, terse bullets that assume Go competence and avoid explaining basics. Not a 5 because the intro line and "When to Apply" section restate the description, and the effective_go URL appears three times, all trimmable.	4 / 5
Actionability	Concrete, specific rules ("Always use gofmt", "MixedCaps for exported names", "accept interfaces, return concrete types", "1-3 methods ideal") give actionable guidance. Not a 5 because the body has no executable code examples illustrating idiomatic vs. non-idiomatic patterns.	4 / 5
Workflow Clarity	Clear, well-organized sections for a single-purpose conventions skill with no destructive operations (so no validation cap applies). Not a 5 because how to apply the conventions across writing vs. reviewing vs. refactoring is not sequenced.	4 / 5
Progressive Disclosure	Clean overview body with a well-signaled, one-level-deep real bundle reference ("See `references/error-handling.md` for comprehensive error handling patterns..."), with detailed code patterns appropriately split into that file. Matches the anchor-5 structure.	5 / 5
	Total	17 / 20 Passed

Description

78%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 well-structured description that clearly states both capability and trigger conditions with natural keywords. Its main weakness is generic action phrasing ("apply best practices") rather than concrete capabilities, and broad triggers that could overlap related Go skills.

Suggestions

Replace generic action verbs with concrete capabilities, e.g. "Enforces gofmt formatting, idiomatic naming (MixedCaps), small interfaces, and channel-based concurrency patterns".

Add the "golang" synonym and ".go" file extension to broaden natural trigger coverage.

Tighten the "Use when" clause to reference Effective-Go-specific contexts (e.g. "when seeking idiomatic Go conventions from the Effective Go guide") to reduce overlap with other Go skills.

Dimension	Reasoning	Score
Specificity	Names the Go domain and a few actions ("Apply Go best practices, idioms, and conventions") plus use-case activities (writing, reviewing, refactoring), but the stated actions are generic rather than concrete. Not a 4 because the actions lack the specificity of anchor-4 examples like "extracts text, fills forms, converts pages".	3 / 5
Completeness	Explicitly answers both what ("Apply Go best practices, idioms, and conventions...") and when ("Use when writing, reviewing, or refactoring Go code") with concrete trigger phrases, matching the anchor-5 pattern exactly.	5 / 5
Trigger Term Quality	Includes natural user phrases ("Go best practices", "idioms", "conventions", "writing/reviewing/refactoring Go code") with good coverage. Not a 5 because it omits common synonyms/extensions like "golang" and ".go".	4 / 5
Distinctiveness Conflict Risk	Clearly Go-specific niche with distinct triggers, but "writing, reviewing, or refactoring Go code" is broad enough to risk minor overlap with other Go-focused skills. Not a 5 because the triggers are not tightly scoped to a unique niche.	4 / 5
	Total	16 / 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: freightCognition/linehaulai-claude-marketplace
Path: plugins/golang-orchestrator/skills/effective-go/SKILL.md
Commit: 88571a6

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