CtrlK
BlogDocsLog inGet started
Tessl Logo

verify

Prove a RuView result is real — run the deterministic SHA-256 proof and the witness bundle (ADR-028), and lint any claim for MEASURED-vs-CLAIMED honesty.

68

Quality

83%

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.

The body is lean, action-oriented, and well-structured with executable commands and explicit validation checkpoints including a re-verify feedback loop, fully matching the rubric's strong anchors across all dimensions.

DimensionReasoningScore

Conciseness

The ~30-line body is dense and purposeful — 'feeds a reference signal through the production pipeline and hashes the output against expected_features.sha256' — with no padding or explanation of concepts Claude already knows, matching the lean-and-efficient anchor.

3 / 3

Actionability

Provides copy-paste-ready executable commands — 'ruview_verify', 'bash scripts/generate-witness-bundle.sh', 'cd dist/witness-bundle-ADR028-*/ && bash VERIFY.sh', 'ruview_claim_check {text}' — with expected outputs, fitting the fully-executable anchor.

3 / 3

Workflow Clarity

Sequences the witness bundle generation-then-verify flow with explicit checkpoints ('Must print VERDICT: PASS', 'must be 7/7 PASS') and a regenerate-then-re-verify feedback loop, satisfying the validation-and-recovery anchor for this validation-focused skill.

3 / 3

Progressive Disclosure

A simple, single-purpose skill under 50 lines with no bundle files, organized into four clearly labeled sections (deterministic proof, witness bundle, claim honesty, firmware-specific), meeting the simple-skills allowance for full marks on well-organized structure.

3 / 3

Total

12

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and clearly differentiated within its niche, but relies on project-internal jargon for triggers and omits an explicit 'Use when...' clause, which caps its completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when verifying a RuView result, preparing a release-grade attestation, or before quoting any accuracy claim').

Soften reliance on internal jargon by pairing terms like 'ADR-028 witness bundle' with natural phrasing users would actually say, such as 'verify results' or 'check claims'.

Clarify 'RuView' for users who may not know it is the project, or expand the trigger to reference 'release validation' or 'proof of correctness'.

DimensionReasoningScore

Specificity

Names three concrete actions — 'run the deterministic SHA-256 proof', 'the witness bundle (ADR-028)', and 'lint any claim for MEASURED-vs-CLAIMED honesty' — matching the multiple-specific-actions anchor rather than the partial score-2 anchor.

3 / 3

Completeness

Clearly states what the skill does but lacks an explicit 'Use when...' trigger, and the rubric caps completeness at 2 when trigger guidance is missing or only implied.

2 / 3

Trigger Term Quality

Has some natural phrasing ('Prove a RuView result is real', 'lint any claim') but leans heavily on project-internal jargon (RuView, ADR-028, witness bundle) with missing common variations, fitting the some-keywords-but-incomplete anchor rather than full natural coverage.

2 / 3

Distinctiveness Conflict Risk

The niche is sharply defined around RuView verification, ADR-028 witness bundles, and MEASURED-vs-CLAIMED linting, making it unlikely to fire for unrelated skills — matching the clear-niche anchor.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
ruvnet/RuView
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.