CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rust-pro

Create and review Rust 1.75+ systems code with ownership-safe async patterns and production error handling. Use when building or debugging Rust services that need performance and reliability.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./Skills/agent-ops/rust-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 body has sound bones — a sequenced procedure with validation feedback loops and specific ownership/error rules — but is diluted by generic boilerplate sections, a single self-contradicting code example, no concrete validation commands, and a broken reference path. Tightening to Rust-specific guidance would lift the weakest dimensions.

Suggestions

Fix the reference path: the body cites 'Infrastructure/references/deep-guidance.md' but the file lives at 'references/deep-guidance.md', making the skill's only deep-guidance pointer unusable.

Replace the example's Result<u16, String> with a domain error enum so the sample code follows the skill's own 'no stringly-typed errors' rule, and add the concrete validation commands the Procedure mandates (e.g., cargo check, cargo clippy, cargo test).

Remove the Table of Contents and the generic 'Philosophy'/'Constraints'/'Anti-patterns' boilerplate in favor of Rust-specific guidance, cutting duplicated content like the 'Read when' line that also appears inside deep-guidance.md.

DimensionReasoningScore

Conciseness

Bullet guidance is terse, but a Table of Contents on a ~100-line doc plus generic 'Philosophy', 'Constraints', and 'Anti-patterns' boilerplate ('Redact secrets, tokens, credentials', 'Prefer safe, reversible edits over broad refactors') add tokens without Rust-specific value, and the 'Read when' line duplicates text inside deep-guidance.md. Mostly efficient, but several sections could be trimmed — not anchor 2's heavily padded profile, but clearly above anchor 4.

3 / 5

Actionability

One executable example exists ('pub fn parse_port...') but it is trivial and contradicts the skill's own rule ('domain-specific error enums over stringly-typed errors') by returning Result<u16, String>, and the mandated validation steps name no actual commands (cargo check/clippy/test). Concrete guidance is present but incomplete, matching anchor 3 rather than anchor 4's 'minor gaps'.

3 / 5

Workflow Clarity

'Procedure' gives a clear 3-step sequence and 'Validation' adds fail-fast and re-run-after-fix feedback loops ('Re-run checks after fixes and record residual risk'), but the checkpoints are vague ('run the relevant local checks') with no concrete commands — anchor 4's 'clear sequence with most checkpoints; minor validation gaps'.

4 / 5

Progressive Disclosure

The single deep reference is well signaled ('Open deep guidance... Read when...') and one level deep, but the body points to 'Infrastructure/references/deep-guidance.md' while the actual bundle file is at 'references/deep-guidance.md' — the broken path makes the only deep-guidance pointer non-navigable, and the other bundle files are unmentioned. Structure is present but the navigation defect sits between anchors 3 and 4, landing at 3.

3 / 5

Total

13

/

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: third-person voice, concrete capabilities, and an explicit 'Use when' trigger clause covering both building and debugging. Minor gaps in keyword synonyms (Cargo, borrow-checker) keep trigger-term coverage just short of comprehensive.

DimensionReasoningScore

Specificity

Names the domain ('Rust 1.75+ systems code') and several concrete actions ('create and review', 'ownership-safe async patterns', 'production error handling'), matching the 'several specific actions; minor gaps' anchor rather than anchor 5's comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what ('Create and review Rust 1.75+ systems code with ownership-safe async patterns and production error handling') and when ('Use when building or debugging Rust services that need performance and reliability') with concrete trigger phrases, matching anchor 5.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present ('Rust services', 'building or debugging Rust'), but common variations like Cargo, crates, or borrow-checker are missing, fitting anchor 4's 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

'Rust 1.75+', 'ownership-safe async patterns', and 'production error handling' carve a clear niche with distinct triggers and minimal overlap risk with other 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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/agent-ops/rust-pro/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.