Back to catalog
Human reviewedDevelopment

Skill dossier

rust-engineer

Source declaration

Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.

The author's original description, preserved in English. It describes intent, not verified performance.

Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Writes and reviews idiomatic Rust covering ownership, traits, error handling with thiserror and tokio async, validated with clippy, fmt and tests.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Designs lifetimes and borrowing, annotating lifetimes where inference is insufficient.
  • Creates trait hierarchies with generics and associated types.
  • Minimizes unsafe code and documents each unsafe block's safety invariants.
  • Runs cargo clippy, cargo fmt --check and cargo test and fixes warnings.

Limitations & scope

  • Written for Rust 2021 edition.
  • Advice to avoid unwrap in production may need judgment in tests and examples.
  • This review did not compile or lint the example snippets.

Relevant for

  • Rust developers fighting the borrow checker
  • Teams designing trait-based APIs
  • Engineers building tokio services

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
47.6 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/rust-engineer/references/async.mdReference10.4 KB
skills/rust-engineer/references/error-handling.mdReference7.9 KB
skills/rust-engineer/references/ownership.mdReference5.9 KB
skills/rust-engineer/references/testing.mdReference9.6 KB
skills/rust-engineer/references/traits.mdReference7.6 KB
skills/rust-engineer/SKILL.mdInstruction6 KB

SKILL.md frontmatter

{
  "name": "rust-engineer",
  "description": "Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "language",
    "triggers": "Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "test-master"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze ownership

    Design lifetime relationships and borrowing patterns for the task.

  2. 02
    Action

    Implement safely

    Write idiomatic Rust with minimal unsafe and documented safety invariants.

  3. 03
    Decision

    Validate and fix

    Run clippy, fmt check and tests; fix all warnings before finalising.

  4. 04
    Output

    Deliver Rust code

    Provide types, implementation, error handling, tests and a short design explanation.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

166 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Note

File modification is described or implemented

156 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 156 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

10 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 10 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Inspect any unsafe blocks or FFI bindings it produces, as the skill itself requires documented safety invariants for them.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/rust-engineer # .claude/skills/rust-engineer
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/rust-engineer/SKILL.md.
  2. Review the license, prerequisites and all bundled resources.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Check that SKILL.md for rust-engineer is discoverable at the destination, then ask Claude Code to use it on a small test task.

Prerequisites

  • Written for Rust 2021 edition.
  • Advice to avoid unwrap in production may need judgment in tests and examples.
  • This review did not compile or lint the example snippets.

Example prompts

Representative task

Use the rust-engineer skill to add a thiserror-based AppError to this crate, replace unwrap calls with proper error handling, then run cargo clippy --all-targets --all-features and cargo test.

Inspect before use

Read the rust-engineer skill files at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/rust-engineer/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Concrete validation commands for lints, format and tests.
  • Requires documenting safety invariants for unsafe.

Considerations

  • The skill's own Summary example slices a string by byte index and could panic.
  • cargo bench is only suggested if present.
Research conclusion

A sound Rust workflow with real validation commands; verify its example code before copying.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/rust-engineer
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.