Agent skill

Howto Code In Rust

by ed3dai in ed3dai/ed3d-plugins

A skill your agent uses when writing, reviewing, or modifying Rust code - covers error handling with thiserror+miette, type system patterns, async and serde conventions, testing crates, dependency…

No licenceAuto-check passed

Install Howto Code In Rust

skills CLI
$ npx skills add ed3dai/ed3d-plugins --skill howto-code-in-rust -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ed3dai/ed3d-plugins howto-code-in-rust --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ed3d-house-style/skills/howto-code-in-rust .claude/skills/howto-code-in-rust && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
howto-code-in-rust
GitHub stars
250
Token cost
~2.8k tokens
SKILL.md length
1,420 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
None found

At a glance

A skill your agent uses when writing, reviewing, or modifying Rust code - covers error handling with thiserror+miette, type system patterns, async and serde conventions, testing crates, dependency…

  • Modifying Rust code - covers error handling with thiserror+miette
  • SKILL.md covers Overview, Correctness over convenience, User-facing error quality and Type system patterns, plus 12 more sections
  • Calls cargo
  • Type system patterns

What it does

Howto Code In Rust is an agent skill from ed3dai/ed3d-plugins. Use when writing, reviewing, or modifying Rust code - covers error handling with thiserror+miette, type system patterns, async and serde conventions, testing crates, dependency pinning, and module organization

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Rust. The repository describes itself as: Ed's repo of Claude Code plugins, centered around a research-plan-implement workflow. Only a tiny bit cursed. If you're lucky.

When your agent uses it

  • Modifying Rust code - covers error handling with thiserror+miette
  • Type system patterns
  • Async and serde conventions
  • Dependency pinning

Example prompts

  • “/howto-code-in-rust”

What it can do on your machine

Read from SKILL.md and the folder at commit 0c90f4b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Howto Code In Rust loads about 2.8k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 1,420 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 1,420 words (~2,811 tokens).

“Rust house style. Applies whenever writing, reviewing, or modifying Rust code.”

— opening of SKILL.md by ed3dai
name
howto-code-in-rust

Read the full SKILL.md on GitHub

Files

Just SKILL.md in plugins/ed3d-house-style/skills/howto-code-in-rust of ed3dai/ed3d-plugins.

Open the folder on GitHubat commit 0c90f4b

Compare with similar skills

Howto Code In Rust next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Howto Code In Rust compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Howto Code In Rust this skilled3dai/ed3d-plugins250—~2.8kAutomated safety check: PassNone
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0
Firecrawl Page Scrape Integrationfirecrawl/firecrawl189k1 repos~944Automated safety check: PassISC
Migrate Core Code to Submodulestinyhumansai/openhuman41k—~2.6kAutomated safety check: PassGPL-3.0
Rust TDD Workflowrtk-ai/rtk83k—~753Automated safety check: NotesApache-2.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed
  • Adds Firecrawl's /scrape endpoint to application code to pull markdown, HTML, links, screenshots or structured data from a single known URL.

    189k GitHub starsUsed in 1 repo~944 tokens
    Data & AnalyticsAuto-check passed
  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    41k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated today
    Testing & QAAuto-check: notes
  • Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 4 days ago
    DevelopmentAuto-check: notes

More from ed3dai/ed3d-plugins

All 34 skills in this repo
  • Systematic Debugging

    ed3dai/ed3d-plugins

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis…

    250 GitHub starsUsed in 3 repos~2.4k tokens
    Auto-check passed
  • A skill your agent uses when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation…

    250 GitHub starsUsed in 2 repos~3.5k tokens
    Auto-check passed
  • Brainstorming

    ed3dai/ed3d-plugins

    A skill your agent uses when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning…

    250 GitHub starsUsed in 1 repo~4.3k tokens
    Auto-check passed
  • Writing Good Tests

    ed3dai/ed3d-plugins

    A skill your agent uses when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation

    250 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed
  • Writing Skills

    ed3dai/ed3d-plugins

    A skill your agent uses when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing…

    250 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • Coding Effectively

    ed3dai/ed3d-plugins

    ALWAYS use this skill when writing or refactoring code. An agent skill from ed3dai/ed3d-plugins.

    250 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Questions about Howto Code In Rust

What does Howto Code In Rust do?

A skill your agent uses when writing, reviewing, or modifying Rust code - covers error handling with thiserror+miette, type system patterns, async and serde conventions, testing crates, dependency…. Howto Code In Rust is an agent skill from ed3dai/ed3d-plugins.

When should I use Howto Code In Rust?

Howto Code In Rust fits situations like: modifying Rust code - covers error handling with thiserror+miette; type system patterns; async and serde conventions; dependency pinning.

How do I install Howto Code In Rust in Claude Code?

Run `npx skills add ed3dai/ed3d-plugins --skill howto-code-in-rust -a claude-code`. Or copy the skill folder (plugins/ed3d-house-style/skills/howto-code-in-rust in ed3dai/ed3d-plugins) into .claude/skills/howto-code-in-rust in your project. Claude Code loads it when a task matches its description.

How do I install Howto Code In Rust in Codex?

Run `npx skills add ed3dai/ed3d-plugins --skill howto-code-in-rust -a codex`. Or copy the skill folder (plugins/ed3d-house-style/skills/howto-code-in-rust in ed3dai/ed3d-plugins) into .agents/skills/howto-code-in-rust in your project. Codex loads it when a task matches its description.

Can I use Howto Code In Rust in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ed3dai/ed3d-plugins --skill howto-code-in-rust -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/howto-code-in-rust, .gemini/skills/howto-code-in-rust, .github/skills/howto-code-in-rust and .opencode/skills/howto-code-in-rust in your project.

What does Howto Code In Rust need to run?

Going by SKILL.md and its folder, Howto Code In Rust needs the command-line tools its instructions call (cargo).

Does Howto Code In Rust access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Howto Code In Rust safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Howto Code In Rust use?

No licence was found for Howto Code In Rust or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Howto Code In Rust use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Howto Code In Rust?

Skills that share tags, products or a category with Howto Code In Rust: Update V8 Version (openinterpreter/openinterpreter, 69k stars), Firecrawl Page Scrape Integration (firecrawl/firecrawl, 189k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 41k stars) and Rust TDD Workflow (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Howto Code In Rust?

ed3dai (a GitHub organization) maintains it in ed3dai/ed3d-plugins, which has 250 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on September 6, 2026.

Source: ed3dai/ed3d-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.