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.
Validate Rust work after substantial Rust code changes by running just check, just clippy, then just format.
AGPL-3.0Auto-check: notes
Install Rust Validation
$ npx skills add macro-inc/macro --skill rust-validation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install macro-inc/macro rust-validation --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/macro-inc/macro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.pi/skills/rust-validation .claude/skills/rust-validation && 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 "rust-validation" agent skill from https://github.com/macro-inc/macro/tree/main/.pi/skills/rust-validation into .claude/skills/rust-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-validation", 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/macro-inc/macro/tree/main/.pi/skills/rust-validationType 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 macro-inc/macro --skill rust-validation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install macro-inc/macro rust-validation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macro-inc/macro.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.pi/skills/rust-validation .agents/skills/rust-validation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rust-validation" agent skill from https://github.com/macro-inc/macro/tree/main/.pi/skills/rust-validation into .agents/skills/rust-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-validation", 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 macro-inc/macro --skill rust-validation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install macro-inc/macro rust-validation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macro-inc/macro.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.pi/skills/rust-validation .cursor/skills/rust-validation && 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 "rust-validation" agent skill from https://github.com/macro-inc/macro/tree/main/.pi/skills/rust-validation into .cursor/skills/rust-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-validation", 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/macro-inc/macro.git --path .pi/skills/rust-validation--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 macro-inc/macro --skill rust-validation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install macro-inc/macro rust-validation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macro-inc/macro.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.pi/skills/rust-validation .gemini/skills/rust-validation && 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 "rust-validation" agent skill from https://github.com/macro-inc/macro/tree/main/.pi/skills/rust-validation into .gemini/skills/rust-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-validation", 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 macro-inc/macro rust-validationInstalls 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 macro-inc/macro --skill rust-validation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/macro-inc/macro.git skills-src && mkdir -p .github/skills && cp -r skills-src/.pi/skills/rust-validation .github/skills/rust-validation && 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 "rust-validation" agent skill from https://github.com/macro-inc/macro/tree/main/.pi/skills/rust-validation into .github/skills/rust-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-validation", 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 macro-inc/macro --skill rust-validation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install macro-inc/macro rust-validation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macro-inc/macro.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.pi/skills/rust-validation .opencode/skills/rust-validation && 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 "rust-validation" agent skill from https://github.com/macro-inc/macro/tree/main/.pi/skills/rust-validation into .opencode/skills/rust-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-validation", 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.
Facts
- Skill name
rust-validation- GitHub stars
- 4.6k
- Token cost
- ~396 tokens
- SKILL.md length
- 186 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Validate Rust work after substantial Rust code changes by running just check, just clippy, then just format.
- SKILL.md covers Working Directory, Validation Commands and Final Response
- Calls just
What it does
Rust Validation is an agent skill from macro-inc/macro. Validate Rust work after substantial Rust code changes by running just check, just clippy, then just format. Use before the final response after a significant Rust implementation or cleanup task; batch edits first instead of running after every small change.
Its SKILL.md is about 400 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: Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory. The licence is AGPL-3.0.
Example prompts
- “/rust-validation”
Requirements
- Pre-approved tools (allowed-tools): Bash, Read, Edit, Glob, Grep
What it can do on your machine
Read from SKILL.md and the folder at commit 39f3c91. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadEditGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
just
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
Rust Validation loads about 396 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 186 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.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Edit, Glob, Grep
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
The full file from macro-inc/macro at commit 39f3c91, republished under its AGPL-3.0 licence (© macro-inc). 186 words, ~396 tokens.
Download SKILL.mdSave it as
.claude/skills/rust-validation/SKILL.md (or your agent's skills folder).- name
- rust-validation
- description
- Validate Rust work after substantial Rust code changes by running `just check`, `just clippy`, then `just format`. Use before the final response after a significant Rust implementation or cleanup task; batch edits first instead of running after every small change.
- allowed-tools
- Bash, Read, Edit, Glob, Grep
- disable-model-invocation
- true
Rust Validation
Use this skill when you have changed Rust code or Rust build inputs and are nearing the end of a substantial implementation, refactor, or bug-fix task.
Do not run these commands after every individual edit. Batch related edits first, then validate once at the end of a major work pass or before handing the task back to the user.
Working Directory
Run validation from the repository root. If the root justfile or one of the required recipes is missing, stop and tell the user what prevented validation instead of inventing alternate commands.
Validation Commands
Run these commands one at a time, in this exact order:
just rust-check
just clippy
just format
just hakariIf just rust-check or just clippy fails, do not continue to later commands. Inspect the failure, fix it if it is in scope, then rerun the full sequence starting at just rust-check.
If just format changes files, review the resulting changes before the final response.
Final Response
Briefly report whether validation passed and list the commands that ran. If validation was skipped because no Rust code was changed, or because the user explicitly asked to skip it, say so.
© macro-inc, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .pi/skills/rust-validation of macro-inc/macro.
Open the folder on GitHubat commit 39f3c91
Compare with similar skills
Rust Validation 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 |
|---|---|---|---|---|---|---|
| Rust Validation this skillmacro-inc/macro | 4.6k | — | ~396 | Automated safety check: Notes | AGPL-3.0 | |
| 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 |
Similar skills
Firecrawl Page Scrape Integration
firecrawl/firecrawl
Adds Firecrawl's /scrape endpoint to application code to pull markdown, HTML, links, screenshots or structured data from a single known URL.
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.
Rust TDD Workflow
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.
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
OpenLogi macOS Permissions Triage
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.
More from macro-inc/macro
All 19 skills in this repoMintlify API
macro-inc/macro
Interact with the Mintlify REST API to manage deployments, trigger builds, and query documentation site metadata programmatically.
Add Tour
macro-inc/macro
Add or change an in-app feature tour (a view's guided flyover) in the web app.
Define Feature Flag
macro-inc/macro
Define a frontend feature flag with defineFlag and wire its readers.
Run App
macro-inc/macro
Run the Macro app on Cursor Cloud and pick up edits. An agent skill from macro-inc/macro.
Add SDK Endpoint
macro-inc/macro
Wrap a new backend endpoint in the TypeScript SDK (packages/sdk), or record it as skipped.
Cloud Storage Hexagonal Architecture
macro-inc/macro
Enforce hexagonal architecture in the Rust backend. An agent skill from macro-inc/macro.
Related
Works with
Questions about Rust Validation
What does Rust Validation do?
Validate Rust work after substantial Rust code changes by running just check, just clippy, then just format. Rust Validation is an agent skill from macro-inc/macro. Validate Rust work after substantial Rust code changes by running just check, just clippy, then just format.
How do I install Rust Validation in Claude Code?
Run `npx skills add macro-inc/macro --skill rust-validation -a claude-code`. Or copy the skill folder (.pi/skills/rust-validation in macro-inc/macro) into .claude/skills/rust-validation in your project. Claude Code loads it when a task matches its description.
How do I install Rust Validation in Codex?
Run `npx skills add macro-inc/macro --skill rust-validation -a codex`. Or copy the skill folder (.pi/skills/rust-validation in macro-inc/macro) into .agents/skills/rust-validation in your project. Codex loads it when a task matches its description.
Can I use Rust Validation 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 macro-inc/macro --skill rust-validation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rust-validation, .gemini/skills/rust-validation, .github/skills/rust-validation and .opencode/skills/rust-validation in your project.
What does Rust Validation need to run?
Going by SKILL.md and its folder, Rust Validation needs the command-line tools its instructions call (just). Its frontmatter pre-approves these tools: Bash, Read, Edit, Glob, Grep.
Does Rust Validation 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 Rust Validation safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Rust Validation use?
Rust Validation is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Rust Validation use?
About 396 tokens (SKILL.md is roughly 1.6k 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 Rust Validation?
Skills that share tags, products or a category with Rust Validation: 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 Rust Validation?
macro-inc (a GitHub organization) maintains it in macro-inc/macro, which has 4,578 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.
Source: macro-inc/macro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.