BeautifulRust
A Claude Code plugin that teaches Claude to write idiomatic, robust Rust
Runssource: GitHubPythonMITcommit a2b22682fa69
Python, MIT licensed. The project labels itself: claude code, claude plugin, claude skills, coding agent, rust and style guide.
BeautifulRust runs. An Argusic agent installed it in 8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 3 BeautifulRust skills install via the README command into ./agents/skills with a skills-lock.json and list with source morganlinton/BeautifulRust; python3 scripts/check-skill.py and the 25 unittest checks pass with 0 errors; scripts/check-lints.sh reports all 28 expected lints fired once a local rustup clippy toolchain is added.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- npx skills failed to start: import { styleText } from "node:util" — SyntaxError under the container's Node 18.19 (package requires Node 22.20+)3 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- python3 -m unittest discover -s tests exited 0 (25 tests OK); python3 scripts/check-skill.py printed '0 errors, 0 warnings'; npx skills add morganlinton/BeautifulRust -a codex -y --copy exited 0 and npx skills list shows all 3 skills with source morganlinton/BeautifulRust; diff -rq shows installed copies byte-identical to repo
- Model tokens used
- 285,573
- Exact commit tested
- a2b22682fa69
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Installed all 3 skills to both global and project copy modes; `diff -rq` shows installed trees by… - Final project install `skills list` confirms all 3 skills resolvable with source `morganlinton/Be… - Recorded one known gap: a Rust toolchain is not preinstalled and must be added with `rustup compo… **Next step** Run full `cargo test` / eval suites with bundled conformance fixtures (`scripts/check-lints.sh`, `t… exec /bin/sh -lc 'echo start; date -u +%H:%M:%S' in /work/repo succeeded in 0ms: start 07:22:18 tokens used 285,573
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 8 minutes to install, slower than the median of the 17 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 18 claude-code projects Argusic has installed and timed, BeautifulRust was the 13th fastest to reach a running state, and 17 of 18 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
claude-codeclaude-pluginclaude-skillscoding-agentruststyle-guide
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/beautifulrust)Questions
- Does BeautifulRust run?
- Yes. BeautifulRust runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test BeautifulRust?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a2b22682fa69. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test BeautifulRust?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does BeautifulRust take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does BeautifulRust need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing BeautifulRust?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does BeautifulRust compare with the alternatives?
- Of the 18 claude-code projects Argusic has installed and timed, BeautifulRust was the 13th fastest to reach a running state, and 17 of 18 reached one at all.
- Where is the evidence for BeautifulRust?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.