CtrlK
BlogDocsLog inGet started
Tessl Logo

go

Use for Go changes in Neva: authoring, refactoring, debugging, or review.

80

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary concise instruction skill: every line is an actionable rule or pointer, it defers detail to the right external docs, and it avoids teaching Claude things it already knows. No bundle files exist, so disclosure is judged on organization and signaled references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, offering rules and pointers (gofmt, .golangci.yml, go.mod) without explaining what Go is or how libraries work.

3 / 3

Actionability

Concrete, specific guidance throughout — "Always run `gofmt`", "Never ignore errors, including assignment to `_`", "Add doc comments for new exported Go functions" — with no vague direction; absence of full code blocks is fine for this instruction-only skill.

3 / 3

Workflow Clarity

As a simple rule-based skill it gives an unambiguous flow — read `AGENTS.md` before editing, apply the rules, run gofmt and respect lints — which qualifies for 3 under the simple-skill carve-out.

3 / 3

Progressive Disclosure

Well under 50 lines and organized into clear `## Rules` and `## Runtime` sections, with one-level-deep, clearly signaled references to `AGENTS.md` and `docs/developer/runtime-functions.md` rather than inline walls of text.

3 / 3

Total

12

/

12

Passed

Description

100%

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 tight, well-formed description that names concrete actions, includes an explicit trigger clause, and is clearly scoped to Go work in Neva. It answers what and when without padding or buzzwords.

DimensionReasoningScore

Specificity

"authoring, refactoring, debugging, or review" lists multiple specific concrete actions rather than vague language, matching the anchor for listing several concrete actions.

3 / 3

Completeness

"Use for Go changes in Neva: authoring, refactoring, debugging, or review" explicitly answers both what it does and when to use it via an explicit "Use for" trigger clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

"Go changes", "refactoring", "debugging", and "review" are natural terms users would actually say when requesting this skill, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

Scoping to "Go changes in Neva" carves out a clear niche with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nevalang/neva
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.