CtrlK
BlogDocsLog inGet started
Tessl Logo

rust-expert

Rust programming expert for ownership, lifetimes, async/await, traits, and unsafe code

66

Quality

78%

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 ./crates/openfang-skills/bundled/rust-expert/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is a well-organized, highly actionable Rust reference with concrete APIs, crates, and signatures, appropriately scoped for a single-purpose persona skill. Its main weakness is mild verbosity where it explains Rust concepts Claude already knows, which could be trimmed for token efficiency.

Suggestions

Trim restatements of widely-known Rust semantics (e.g. the Pin-not-moved explanation, lifetime-elision rules) to keep only the decision guidance, improving conciseness without losing actionability.

DimensionReasoningScore

Conciseness

The body is a tight, well-structured reference rather than a verbose wall, but several lines restate Rust knowledge Claude already has (e.g. 'understand that Pin guarantees the future will not be moved after polling begins', lifetime-elision rules, what tokio::select! does), so it could be tightened by trimming concept explanations.

2 / 3

Actionability

It gives concrete, specific guidance throughout — named APIs (tokio::spawn, tokio::select!, tokio::sync::mpsc), named crates (thiserror/anyhow), concrete attributes (#[derive(thiserror::Error)], #[error("...")]), and copy-paste-ready signatures (fn field(mut self, val: T) -> Self, fn build(self) -> Result<Foo>, struct UserId(String)) — and per the code-vs-instruction note, absence of full runnable blocks is not penalized for an actionable instruction skill.

3 / 3

Workflow Clarity

This is a single-purpose persona/principles skill rather than a multi-step process, and per the simple-skills note workflow clarity can score 3 when the content is clear and well-organized; its sections (Principles, Techniques, Patterns, Pitfalls) are unambiguous and need no validation checkpoints since it performs no destructive or batch operations.

3 / 3

Progressive Disclosure

At ~34 lines with no need for external references, it satisfies the under-50-lines rule: progressive disclosure scores 3 with just well-organized sections, and the body is cleanly split into clearly labeled sections with no nested references.

3 / 3

Total

11

/

12

Passed

Description

72%

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, uses natural Rust trigger terms, and occupies a clear niche, but it lacks an explicit 'Use when...' trigger clause so it answers 'what' without clearly answering 'when'. Adding a usage-trigger clause would raise its completeness and specificity.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when writing, debugging, or reviewing Rust code involving ownership, lifetimes, async/await, traits, or unsafe blocks.'

Reframe the topic list as concrete actions performed (e.g. 'Diagnoses ownership/borrow errors, annotates lifetimes, refactors async code') to strengthen specificity beyond a domain-plus-topics phrasing.

DimensionReasoningScore

Specificity

The description names the Rust domain and several concrete capability areas ("ownership, lifetimes, async/await, traits, and unsafe code"), but frames them as areas of expertise rather than performed actions (no verbs like 'extract'/'fill'/'merge'), matching the score-2 anchor of naming domain and some actions without being comprehensive.

2 / 3

Completeness

It answers 'what' (a Rust expert for the listed topics) but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline the missing 'when' caps completeness at 2.

2 / 3

Trigger Term Quality

It surfaces exactly the natural terms a Rust user would say when needing help — "ownership", "lifetimes", "async/await", "traits", and "unsafe code" — giving good coverage of natural user vocabulary.

3 / 3

Distinctiveness Conflict Risk

"Rust programming expert" is a clear niche anchored to Rust-specific topic triggers that are unlikely to fire for or conflict with other skills.

3 / 3

Total

10

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
RightNow-AI/openfang
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.