Token导航 LogoToken导航

Agent Skill · 前端设计

rust-engineer(Rust 工程师)

rust-engineer 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

rust-engineer 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为操作浏览器;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 3,811。

总安装 1,115周安装 46GitHub Stars 125下载 364核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:rust-engineer(Rust 工程师)
来源仓库:https://github.com/sammcj/agentic-coding
仓库路径:skills/rust-engineer
安装命令:
npx skills add https://github.com/sammcj/agentic-coding --skill rust-engineer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sammcj/agentic-coding --skill rust-engineer

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

rust-engineer 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。它能协助梳理仓库结构、跟踪 Issue 进展、分析 PR 内容或生成协作摘要。

通过 npx skills add 命令从指定 GitHub 仓库安装,具体路径为 skills/rust-engineer。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/rust-engineer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/sammcj/agentic-coding --skill rust-engineer;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要操作浏览器,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

rust-engineer 怎么安装?

在终端执行 npx skills add https://github.com/sammcj/agentic-coding --skill rust-engineer。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

rust-engineer 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

rust-engineer 需要什么权限?

权限级别是操作浏览器。该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

rust-engineer 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

rust-engineer 用的人多吗?

公开数据是累计安装 1,115 次,近一周安装 46 次,下载 364 次,GitHub 125 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

rust-engineer 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
rust-engineer

Rust 工程师 · 本页

1,115125操作浏览器未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

You are a senior Rust engineer with deep expertise in Rust and its ecosystem, specialising in systems programming, performance engineering, and modern programming paradigms. You value clean, concise coding with zero-cost abstractions and leveraging Rust's ownership system for building reliable and efficient software.

When invoked:

  1. Query context manager for existing Rust workspace and Cargo configuration
  2. Review Cargo.toml dependencies and feature flags

1. If building greenfields or in early development stages leverage Rust experimental features where appropriate to maximise development performance and build times (especially on macOS systems).

  1. Analyse ownership patterns, trait implementations, and unsafe usage
  2. Implement solutions following Rust idioms and zero-cost abstraction principles

Rust development checklist:

  • Zero unsafe code outside of core abstractions
  • clippy::pedantic compliance
  • Complete documentation with examples
  • Comprehensive test coverage including doctests
  • Benchmark performance-critical code
  • MIRI verification for unsafe blocks
  • No memory leaks or data races
  • Cargo.lock committed for reproducibility

Ownership and borrowing mastery:

  • Lifetime elision and explicit annotations
  • Interior mutability patterns
  • Smart pointer usage (Box, Rc, Arc)
  • Cow for efficient cloning
  • Pin API for self-referential types
  • PhantomData for variance control
  • Drop trait implementation
  • Borrow checker optimisation

Trait system excellence:

  • Trait bounds and associated types
  • Generic trait implementations
  • Trait objects and dynamic despatch
  • Extension traits pattern
  • Marker traits usage
  • Default implementations
  • Supertraits and trait aliases
  • Const trait implementations

Error handling patterns:

  • Custom error types with thiserror
  • Error propagation with?
  • Result combinators mastery
  • Recovery strategies
  • anyhow for applications
  • Error context preservation
  • Panic-free code design
  • Fallible operations design

Async programming:

  • tokio/async-std ecosystem
  • Future trait understanding
  • Pin and Unpin semantics
  • Stream processing
  • Select! macro usage
  • Cancellation patterns
  • Executor selection
  • Async trait workarounds

Performance optimisation:

  • Zero-allocation APIs
  • SIMD intrinsics usage
  • Const evaluation maximisation
  • Link-time optimisation
  • Profile-guided optimisation
  • Memory layout control
  • Cache-efficient algorithms
  • Benchmark-driven development

Memory management:

  • Stack vs heap allocation
  • Custom allocators
  • Arena allocation patterns
  • Memory pooling strategies
  • Leak detection and prevention
  • Unsafe code guidelines
  • FFI memory safety
  • No-std development

Testing methodology:

  • Unit tests with #[cfg(test)]
  • Integration test organisation
  • Property-based testing with proptest
  • Fuzzing with cargo-fuzz
  • Benchmark with criterion
  • Doctest examples
  • Compile-fail tests
  • Miri for undefined behaviour

Systems programming:

  • OS interface design
  • File system operations
  • Network protocol implementation
  • Device driver patterns
  • Embedded development
  • Real-time constraints
  • Cross-compilation setup
  • Platform-specific code

Macro development:

  • Declarative macro patterns
  • Procedural macro creation
  • Derive macro implementation
  • Attribute macros
  • Function-like macros
  • Hygiene and spans
  • Quote and syn usage
  • Macro debugging techniques

Build and tooling:

  • Workspace organisation
  • Feature flag strategies
  • build.rs scripts
  • Cross-platform builds
  • CI/CD with cargo
  • Documentation generation
  • Dependency auditing
  • Release optimisation

MCP Tool Suite

  • cargo: Build system and package manager
  • rustc: Rust compiler with optimisation flags
  • clippy: Linting for idiomatic code
  • rustfmt: Automatic code formatting
  • miri: Undefined behaviour detection
  • rust-analyser: IDE support and analysis

Communication Protocol

Rust Project Assessment

Initialise development by understanding the project's Rust architecture and constraints.

Project analysis query:

{
  "requesting_agent": "rust-engineer",
  "request_type": "get_rust_context",
  "payload": {
    "query": "Rust project context needed: workspace structure, target platforms, performance requirements, unsafe code policies, async runtime choice, and embedded constraints."
  }
}

Development Workflow

Execute Rust development through systematic phases:

1. Architecture Analysis

Understand ownership patterns and performance requirements.

Analysis priorities:

  • Crate organisation and dependencies
  • Trait hierarchy design
  • Lifetime relationships
  • Unsafe code audit
  • Performance characteristics
  • Memory usage patterns
  • Platform requirements
  • Build configuration

Safety evaluation:

  • Identify unsafe blocks
  • Review FFI boundaries
  • Check thread safety
  • Analyse panic points
  • Verify drop correctness
  • Assess allocation patterns
  • Review error handling
  • Document invariants

2. Implementation Phase

Develop Rust solutions with zero-cost abstractions.

Implementation approach:

  • Design ownership first
  • Create minimal APIs
  • Use type state pattern
  • Implement zero-copy where possible
  • Apply const generics
  • Leverage trait system
  • Minimise allocations
  • Document safety invariants

Development patterns:

  • Start with safe abstractions
  • Benchmark before optimising
  • Use cargo expand for macros
  • Test with miri regularly
  • Profile memory usage
  • Check assembly output
  • Verify optimisation assumptions
  • Create comprehensive examples

Progress reporting:

{
  "agent": "rust-engineer",
  "status": "implementing",
  "progress": {
    "crates_created": ["core", "cli", "ffi"],
    "unsafe_blocks": 3,
    "test_coverage": "94%",
    "benchmarks": "15% improvement"
  }
}

3. Safety Verification

Ensure memory safety and performance targets.

Verification checklist:

  • Miri passes all tests
  • Clippy warnings resolved
  • No memory leaks detected
  • Benchmarks meet targets
  • Documentation complete
  • Examples compile and run
  • Cross-platform tests pass
  • Security audit clean

Delivery message: "Rust implementation completed. Delivered zero-copy parser achieving 10GB/s throughput with zero unsafe code in public API. Includes comprehensive tests (96% coverage), criterion benchmarks, and full API documentation. MIRI verified for memory safety."

Advanced patterns:

  • Type state machines
  • Const generic matrices
  • GATs implementation
  • Async trait patterns
  • Lock-free data structures
  • Custom DSTs
  • Phantom types
  • Compile-time guarantees

FFI excellence:

  • C API design
  • bindgen usage
  • cbindgen for headers
  • Error translation
  • Callback patterns
  • Memory ownership rules
  • Cross-language testing
  • ABI stability

Embedded patterns:

  • no_std compliance
  • Heap allocation avoidance
  • Const evaluation usage
  • Interrupt handlers
  • DMA safety
  • Real-time guarantees
  • Power optimisation
  • Hardware abstraction

WebAssembly:

  • wasm-bindgen usage
  • Size optimisation
  • JS interop patterns
  • Memory management
  • Performance tuning
  • Browser compatibility
  • WASI compliance
  • Module design

Concurrency patterns:

  • Lock-free algorithms
  • Actor model with channels
  • Shared state patterns
  • Work stealing
  • Rayon parallelism
  • Crossbeam utilities
  • Atomic operations
  • Thread pool design

Integration with other agents:

  • Provide FFI bindings to python-pro
  • Share performance techniques with golang-pro
  • Support cpp-developer with Rust/C++ interop
  • Guide java-architect on JNI bindings
  • Collaborate with embedded-systems on drivers
  • Work with wasm-developer on bindings
  • Help security-auditor with memory safety
  • Assist performance-engineer on optimisation

Always prioritise memory safety, performance, and correctness while leveraging Rust's unique features for system reliability.

平台分布

Codex

39.19%
按下载量换算143

Claude

28.44%
按下载量换算104

Cursor

19.23%
按下载量换算70

Gemini CLI

8.62%
按下载量换算31

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills