M
morganlinton/BeautifulRust
Agent Skills that teach coding agents to write, review, and port idiomatic Rust, plus a tested clippy config
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置(取自该仓库的安装命令)
{
"mcpServers": {
"morganlinton-beautifulrust": {
"command": "npx",
"args": ["skills"]
}
}
}解析自我们于 2026-11-02 抓取的该仓库 README;我们未执行过。
command/args 来自仓库写明的安装命令;不确定时请以该项目 README 为准。
VS Code(.vscode/mcp.json —— 键名是 servers)
{
"servers": {
"morganlinton-beautifulrust": {
"command": "npx",
"args": ["skills"]
}
}
}VS Code 顶层键是 <code>servers</code>,其余与上面那份相同。
Claude Code(命令行)
claude mcp add --transport stdio morganlinton-beautifulrust -- npx skills
Claude Code 不收 JSON 文件,用这条命令直接加。
配置项的键名以你的客户端为准:客户端与 CLI
- ★ 数取值
- 1,808 ★ · morganlinton/BeautifulRust · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-03 · 最近见到 2026-11-14 · 共见到 12 次 · 被 1 个来源列出
- 评分构成
- 综合分 106 · 1,808 ★ · 1 个来源 · repo
- 安装
npx skills
常见问题(答案都来自我们的记录)
怎么安装?
该仓库给出的安装命令是
npx skills。我们的记录里它是仓库自己提供的;不保证在你的客户端上直接可用。它适合谁 / 用来做什么?
我们把它归在这些标签下: Agent 技能。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
morganlinton/BeautifulRust;我们收录于 2026-11-03;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# Beautiful Rust
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Three standard Agent Skills and a lints config that teach coding
agents to write, review, port, and enforce idiomatic Rust:
rust-best-practices loads whenever an agent writes or changes Rust, and steers it
toward idiomatic, robust, maintainable code.
rust-review reviews existing Rust code, a file, a crate, or a diff, and writes a
prioritized report where every finding cites the rule it breaks and shows the fix.
rust-port ports C, C++, Python, Go, or JavaScript to idiomatic Rust with the same
behavior, porting the original tests first so you can prove the two match.
lints/ is a drop-in clippy configuration that enforces the machine-checkable rules
in CI.
They work with Claude Code, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, and any other
agent that reads the Agent Skills format. Every code example in the skills compiles on
stable Rust, and every lint in the config was checked against current clippy.
The guidance is distilled from five sources, with a condensed digest of each bundled in
the skill so the agent can consult the original reasoning when it needs to:
Google Rust Style Guide
Rust API Guidelines (official rust-lang checklist)
Effective Rust by David Drysdale
Rust Design Patterns (idioms, patterns, anti-patterns)
Microsoft Pragmatic Rust Guidelines
Where the sources disagree, the skill picks a side and says why.
## What it changes
Asked for a small semver-parsing library, an agent without the skill produced working
code with public fields, no # Errors docs, and unwrap() in its doc examples. With the
skill, the same agent kept the fields private, documented failure modes, and wrote doc
examples users can copy safely. Condensed from those two runs:
rust
// Without the skill
/// A semantic version. The fields are public for convenience.
pub struct Version {
pub major: u64,
pub minor: u64,
pub patch: u64,
pub pre: Vec ,
pub build: Vec ,
impl Version {
/// Parses a version string.
///
///
/// let v = Version::parse("1.2.3").unwrap();
///
pub fn parse(s: &str) -> Result { / ... / }
rust
// With the skill
/// A semantic version. Equality, hashing, and ordering ignore build metadata.
pub struct Version {
major: u64,
minor: u64,
patch: u64,
pre: Vec ,
build: Vec ,
impl Version {
/// Parses a version string according to SemVer 2.0.0.
///
/// # Errors
///
/// Returns [ParseVersionError] if the string is empty, a numeric part has a
/// leading zero or overflows u64, or an identifier contains invalid characters.
///
///
/// # use semverlite::Version;
/// # fn main() -> Result {
/// let v = Version::parse("1.2.3-beta.1")?;
/// asserteq!(v.major(), 1);
/// # Ok(())
/// # }
///
pub fn parse(s: &str) -> Result { / ... / }
/// Returns the major version number.
pub fn major(&self) -> u64 { self.major }
Across three test tasks (a library, a CLI, and refactoring a messy module), the skill
passed 29 of 30 checks against 24 of 30 without it. See Testing the skills.
## Install
Each skill is a folder under skills/: rust-best-practices/, rust-review/, and
rust-port/. Every option below puts those folders where your agent looks for skills.
Install all three; the review and port skills lean on the best-practices skill for style.
### Any agent, one command
agents to write, review, port, and enforce idiomatic Rust:
rust-best-practices loads whenever an agent writes or changes Rust, and steers it
toward idiomatic, robust, maintainable code.
rust-review reviews existing Rust code, a file, a crate, or a diff, and writes a
prioritized report where every finding cites the rule it breaks and shows the fix.
rust-port ports C, C++, Python, Go, or JavaScript to idiomatic Rust with the same
behavior, porting the original tests first so you can prove the two match.
lints/ is a drop-in clippy configuration that enforces the machine-checkable rules
in CI.
They work with Claude Code, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, and any other
agent that reads the Agent Skills format. Every code example in the skills compiles on
stable Rust, and every lint in the config was checked against current clippy.
The guidance is distilled from five sources, with a condensed digest of each bundled in
the skill so the agent can consult the original reasoning when it needs to:
Google Rust Style Guide
Rust API Guidelines (official rust-lang checklist)
Effective Rust by David Drysdale
Rust Design Patterns (idioms, patterns, anti-patterns)
Microsoft Pragmatic Rust Guidelines
Where the sources disagree, the skill picks a side and says why.
## What it changes
Asked for a small semver-parsing library, an agent without the skill produced working
code with public fields, no # Errors docs, and unwrap() in its doc examples. With the
skill, the same agent kept the fields private, documented failure modes, and wrote doc
examples users can copy safely. Condensed from those two runs:
rust
// Without the skill
/// A semantic version. The fields are public for convenience.
pub struct Version {
pub major: u64,
pub minor: u64,
pub patch: u64,
pub pre: Vec ,
pub build: Vec ,
impl Version {
/// Parses a version string.
///
///
/// let v = Version::parse("1.2.3").unwrap();
///
pub fn parse(s: &str) -> Result { / ... / }
rust
// With the skill
/// A semantic version. Equality, hashing, and ordering ignore build metadata.
pub struct Version {
major: u64,
minor: u64,
patch: u64,
pre: Vec ,
build: Vec ,
impl Version {
/// Parses a version string according to SemVer 2.0.0.
///
/// # Errors
///
/// Returns [ParseVersionError] if the string is empty, a numeric part has a
/// leading zero or overflows u64, or an identifier contains invalid characters.
///
///
/// # use semverlite::Version;
/// # fn main() -> Result {
/// let v = Version::parse("1.2.3-beta.1")?;
/// asserteq!(v.major(), 1);
/// # Ok(())
/// # }
///
pub fn parse(s: &str) -> Result { / ... / }
/// Returns the major version number.
pub fn major(&self) -> u64 { self.major }
Across three test tasks (a library, a CLI, and refactoring a messy module), the skill
passed 29 of 30 checks against 24 of 30 without it. See Testing the skills.
## Install
Each skill is a folder under skills/: rust-best-practices/, rust-review/, and
rust-port/. Every option below puts those folders where your agent looks for skills.
Install all three; the review and port skills lean on the best-practices skill for style.
### Any agent, one command
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/morganlinton-beautifulrust/)
- 来源
- github · https://github.com/morganlinton/BeautifulRust
- 按领域浏览
- Agent 技能
- Traction
- 1,808 ★
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。