neva-language

Use for Neva source or snippets: authoring, refactoring, debugging, or review.

Quality

86%

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

87%

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

A tight, actionable reference skill with concrete commands and clean sectioning. The main gap is workflow clarity: editing guidance lacks an explicit ordered sequence with a validation feedback loop.

Suggestions

Convert the editing guidance into an ordered workflow (discover CLI → read style guide → edit → validate) with an explicit validate-fix-retry loop.

Make the validation checkpoint concrete, e.g. specify the compile/run command to execute rather than "compiling or running them".

Dimension	Reasoning	Score
Conciseness	Lean body with no filler or explanation of what Neva is; every bullet delivers actionable guidance, assuming Claude's competence.	3 / 3
Actionability	Provides copy-paste-ready commands (`neva --help`, `go run ./cmd/neva --help`, `neva doc [package/path] [.] <pattern>`) and concrete repo paths (`docs/user/style_guide.md`, `internal/compiler/parser/neva.g4`).	3 / 3
Workflow Clarity	Validation is mentioned ("validate changed Neva programs by compiling or running them") but steps are unordered bullets with no explicit sequence or validate-fix-retry feedback loop.	2 / 3
Progressive Disclosure	Under 50 lines with no bundle files needed; organized into clearly labeled "CLI Discovery" and "Rules" sections, which per the rubric earns a 3 for simple skills.	3 / 3
	Total	11 / 12 Passed

Description

85%

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 concise, specific description with an explicit trigger and a clear niche. Its only weakness is limited keyword variation, which slightly weakens trigger-term coverage.

Suggestions

Broaden trigger terms to include natural variations such as ".neva files", "Neva code", or "Neva programs" so users phrase the request more ways.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — "authoring, refactoring, debugging, or review" — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	The "Use for Neva source or snippets" clause gives an explicit trigger (when) and the action list gives what, satisfying both halves.	3 / 3
Trigger Term Quality	"Neva source or snippets" surfaces the core trigger and a couple of forms, but misses common variations like ".neva files", "Neva code", or "Neva programs".	2 / 3
Distinctiveness Conflict Risk	"Neva" is a distinctive language name giving a clear niche; unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: nevalang/neva
Path: .codex/skills/neva-language/SKILL.md
Commit: a0a5c5f

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.