CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rust-fail-closed-hardening

Use when constructing a domain type with invariants, validating untrusted or numeric input, building subprocess argv, sharing state behind a lock, writing a predicate that gates a release/admission decision, or auditing safe Rust for the silent ways it produces and propagates a wrong value. Greenfield has no reference oracle to catch a wrong-but-non-crashing result — so the wrong value must be made un-constructable, rejected at the boundary, and never allowed to poison state. Fail closed.

Quality

85%

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

75%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 dense, expert-level checklist that consistently shows the wrong pattern and its fix in code, with a clear audit workflow and named regression validations. The main gaps are structural rather than substantive: no bundle files offload the provenance/detail material, and the workflow is distributed across sections instead of one ordered procedure.

Suggestions

Move the field-provenance material (bead-ID citations like ft-l5z7z/bd99c6c and the 9.8k-commit origin paragraph) into a references/field-evidence.md file, keeping SKILL.md to the patterns and fixes — this trims conciseness overhead and fixes the dangling docs/audit-checklist.md mention.

Add a single ordered audit procedure at the top (e.g., 1. identify types/boundaries in the file, 2. apply patterns 1-8, 3. file findings, 4. fix, 5. pin the named regression per contract) so the workflow reads as one checkpointed sequence rather than prose spread across sections.

Complete the code fragments minimally (define MAX_THRESHOLD, Invalid, or note they are illustrative) and add a short executable example for sections 4 and 7, which currently rely on prose alone.

DimensionReasoningScore

Conciseness

The body assumes Rust competence (no basic-concept explanations) and every section teaches a distinct non-obvious pattern with minimal-code illustrations. Minor trimmable material remains: the field-origin paragraph ("9.8k-commit... 24 passes, 56 bugs") and dense inline bead-ID citations like "anchors ft-l5z7z, ft-mnua0, ft-n9btw, ft-t9ydu" earn tokens without guiding the model's next action, which keeps it below the lean 5 anchor.

4 / 5

Actionability

Concrete, correct-looking Rust snippets accompany most patterns (the private-field constructor, the is_finite entry-point rejection, saturate-then-clamp, unwrap_or_else poison recovery, the "--" sentinel), and specific regression cases are named ("the cap at MAX+1, the -x-as-positional case, the NaN-is-rejected case, the cold-default-is-false case"). Not a 5 because several snippets are fragments referencing undefined items (MAX_THRESHOLD, Invalid, cap) and sections 4 and 7 are prose guidance without executable examples.

4 / 5

Workflow Clarity

The 'audit discipline' section sequences the process (run the checklist file-by-file, file a finding before fixing, fix, pin a regression encoding the new contract) with explicit validation cases and a feedback loop ("inject a violation and assert it's caught"). It falls short of the 5 anchor because the sequence lives in prose across sections rather than one enumerated, checkpointed procedure the model can follow start to finish.

4 / 5

Progressive Disclosure

The body is well organized into eight numbered pattern sections plus a closing discipline section, with no nested references and clear navigation. It does not reach 5 because the bundle contains no reference files at all — all ~225 lines are inlined in SKILL.md (the field-provenance citations are prime candidates for a references/ file), and "docs/audit-checklist.md" is cited as provenance but does not exist in the bundle.

4 / 5

Total

16

/

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 with an explicit 'Use when' clause carrying six concrete triggers and a crisp statement of the skill's fail-closed philosophy. Trigger coverage and the what/when pairing are excellent; only the breadth of stated capabilities and a few domain synonyms keep specificity and trigger quality at 4.

DimensionReasoningScore

Specificity

The description lists six concrete scenarios ("constructing a domain type with invariants", "building subprocess argv", "sharing state behind a lock", "writing a predicate that gates a release/admission decision") plus the core action "auditing safe Rust for the silent ways it produces and propagates a wrong value". It stops short of a 5 because the capability coverage rests mostly on trigger contexts rather than an equally explicit list of what the skill does.

4 / 5

Completeness

It explicitly answers both questions: "Use when constructing... validating... building... sharing... writing... or auditing safe Rust" gives concrete trigger phrases, and the second sentence states what it does — makes wrong values "un-constructable, rejected at the boundary, and never allowed to poison state". This matches the 5 anchor exactly; the 4 anchor's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

Natural phrases a user would say are well covered: "validating untrusted or numeric input", "subprocess argv", "release/admission decision", "fail closed". A few natural synonyms for this domain (e.g., "hardening", "overflow", "NaN") are missing, keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — safe-Rust fail-closed hardening of domain types, boundaries, locks, and gates — with triggers unlikely to fire for unrelated skills. No overlap risk with generic Rust, testing, or review skills.

5 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

igouss/gitweb-rs

Path

.claude/skills/rust-fail-closed-hardening/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.