CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-verification

Prepare and verify ruv-FANN Cargo/npm release candidates, pinned Rune builds, frozen source, real artifact provenance, clean consumers, dependency order, and immutable receipts. Use for Rune integration, build reproduction, CI/CD, release readiness, archive contents, version migrations, or candidate validation; it does not authorize publication.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

The content is a tightly written, command-rich verification workflow with strong sequencing, validation checkpoints, and error-recovery guidance, supported by well-placed one-level-deep references. Minor improvements are possible: trim repeated authorization boundary statements and add concrete commands to the plugin-packaging section.

DimensionReasoningScore

Conciseness

The body is dense and operational with no explanations of concepts Claude already knows — e.g., "The driver snapshots source into an isolated directory, preserves live locks and performs ordinary Cargo archive verification." It falls short of anchor 5 because boundary statements repeat (publication non-authorization appears as "it does not authorize publication", "Never publish merely because verification passed", and the opening authorization paragraph), and a few long passages could be tightened.

4 / 5

Actionability

Most sections give copy-paste-ready commands with flags ("python3 scripts/verify-release.py --output \"/path/to/new-forecast-candidates\" --workspace neuro-divergent --reuse-targets", "npm run validate:package", "npm pack --dry-run") and explicit success criteria ("Success requires `verified: true`, zero failing commands"). Anchor 4 rather than 5 because the Claude plugin section lacks concrete commands ("run the bundled helper tests", "validate the Claude manifest") and stays at the hint level.

4 / 5

Workflow Clarity

A clear multi-stage sequence (freeze/inventory → Rune build → Cargo archive → Node packages → plugin → acceptance) with explicit validation gates, negative checks ("Negative checks must reject stale source, a modified plan and object corruption"), and an error-recovery feedback loop ("If a command fails, preserve its exact error and failed receipt, fix the underlying issue and use a new output directory for a fresh run"). This matches anchor 5, and the destructive/batch cap does not apply since validation is pervasive.

5 / 5

Progressive Disclosure

Both bundle references are real, clearly signaled, and one level deep: "Use [the Rune procedure](references/rune.md)" and "Keep an [evidence bundle](references/evidence.md)", and their content (detailed Rune procedure, evidence field checklist) is appropriately split out of the main workflow. The 85-line body is well-sectioned, matching anchor 5's clear overview with well-signaled references.

5 / 5

Total

18

/

20

Passed

Description

87%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 description that clearly states what the skill does and when to use it, with concrete trigger terms and a well-defined niche. The only weakness is that capability coverage is slightly narrower than the body's actual scope and a few natural synonyms are missing.

DimensionReasoningScore

Specificity

"Prepare and verify ruv-FANN Cargo/npm release candidates, pinned Rune builds, frozen source, real artifact provenance, clean consumers, dependency order, and immutable receipts" lists several concrete, domain-specific capabilities, but relies on a single verb governing a noun list and omits body-covered scope such as plugin packaging, audits, and browser/WASM checks. This matches anchor 4 (several specific actions, minor gaps) rather than 5 (comprehensive coverage).

4 / 5

Completeness

The description explicitly answers both questions: the "what" is the multi-part prepare/verify capability list, and the "when" is a concrete "Use for..." clause enumerating seven trigger scenarios, plus an explicit boundary ("it does not authorize publication"). This matches anchor 5: both what and when clearly and explicitly stated with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use for Rune integration, build reproduction, CI/CD, release readiness, archive contents, version migrations, or candidate validation" provides good natural keyword coverage a release-engineering user would plausibly say. It falls short of anchor 5 because common variations like "publish", "cut a release", or "crate/npm packaging" are absent, but it is clearly above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

Project-specific naming ("ruv-FANN Cargo/npm release candidates, pinned Rune builds") carves out a clear niche with distinct triggers, so conflict risk with other skills is minimal. This matches anchor 5 rather than 4, which reserves for overlap risk with closely related skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

ruvnet/ruv-FANN

Path

plugins/ruv-fann/skills/release-verification/SKILL.md

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.