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.
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…
$ npx skills add ed3dai/ed3d-plugins --skill howto-code-in-rust -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ed3dai/ed3d-plugins howto-code-in-rust --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "howto-code-in-rust" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/howto-code-in-rust into .claude/skills/howto-code-in-rust/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "howto-code-in-rust", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/howto-code-in-rustType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ed3dai/ed3d-plugins --skill howto-code-in-rust -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ed3dai/ed3d-plugins howto-code-in-rust --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ed3d-house-style/skills/howto-code-in-rust .agents/skills/howto-code-in-rust && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "howto-code-in-rust" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/howto-code-in-rust into .agents/skills/howto-code-in-rust/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "howto-code-in-rust", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ed3dai/ed3d-plugins --skill howto-code-in-rust -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ed3dai/ed3d-plugins howto-code-in-rust --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ed3d-house-style/skills/howto-code-in-rust .cursor/skills/howto-code-in-rust && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "howto-code-in-rust" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/howto-code-in-rust into .cursor/skills/howto-code-in-rust/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "howto-code-in-rust", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ed3dai/ed3d-plugins.git --path plugins/ed3d-house-style/skills/howto-code-in-rust--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ed3dai/ed3d-plugins --skill howto-code-in-rust -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ed3dai/ed3d-plugins howto-code-in-rust --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ed3d-house-style/skills/howto-code-in-rust .gemini/skills/howto-code-in-rust && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "howto-code-in-rust" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/howto-code-in-rust into .gemini/skills/howto-code-in-rust/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "howto-code-in-rust", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ed3dai/ed3d-plugins howto-code-in-rustInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ed3dai/ed3d-plugins --skill howto-code-in-rust -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ed3d-house-style/skills/howto-code-in-rust .github/skills/howto-code-in-rust && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "howto-code-in-rust" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/howto-code-in-rust into .github/skills/howto-code-in-rust/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "howto-code-in-rust", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ed3dai/ed3d-plugins --skill howto-code-in-rust -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ed3dai/ed3d-plugins howto-code-in-rust --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ed3d-house-style/skills/howto-code-in-rust .opencode/skills/howto-code-in-rust && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "howto-code-in-rust" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/howto-code-in-rust into .opencode/skills/howto-code-in-rust/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "howto-code-in-rust", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
howto-code-in-rustA 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. 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.
Read from SKILL.md and the folder at commit 0c90f4b. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
cargoFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
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.”
Just SKILL.md in plugins/ed3d-house-style/skills/howto-code-in-rust of ed3dai/ed3d-plugins.
Open the folder on GitHubat commit 0c90f4b
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Howto Code In Rust this skilled3dai/ed3d-plugins | 250 | — | ~2.8k | Automated safety check: Pass | None | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 | |
| Firecrawl Page Scrape Integrationfirecrawl/firecrawl | 189k | 1 repos | ~944 | Automated safety check: Pass | ISC | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 41k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Rust TDD Workflowrtk-ai/rtk | 83k | — | ~753 | Automated safety check: Notes | Apache-2.0 | |
| Rust Best Practicesfarm-fe/farm | 5.6k | 3 repos | ~1.1k | Automated safety check: Pass | MIT |
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.
firecrawl/firecrawl
Adds Firecrawl's /scrape endpoint to application code to pull markdown, HTML, links, screenshots or structured data from a single known URL.
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.
rtk-ai/rtk
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.
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
AprilNEA/OpenLogi
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.
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…
ed3dai/ed3d-plugins
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…
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…
ed3dai/ed3d-plugins
A skill your agent uses when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation
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…
ed3dai/ed3d-plugins
ALWAYS use this skill when writing or refactoring code. An agent skill from ed3dai/ed3d-plugins.
Works with
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.
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.
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.
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.
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.
Going by SKILL.md and its folder, Howto Code In Rust needs the command-line tools its instructions call (cargo).
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.
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.
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.
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.
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.
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.