How do I install the Rust Dev Guide skill?

Run npx skillmds@latest add systempromptio/rust-dev-guide in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Rust Dev Guide skill do?

Entry point for rust-development — routes to the right sub-skill for your task It is listed under Productivity on SkillMD.

Is Rust Dev Guide safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rust Dev Guide?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rust Dev Guide free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rust Dev Guide?

systempromptio (@systempromptio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rust Dev Guide by systempromptio — Agent Skill

Name: Rust Dev Guide
Author: systempromptio

File contents

Rust Development

Build Rust extensions, CLI binaries, and MCP servers for systemprompt.io. This plugin covers all Rust development from coding standards to specific extension types.

Skills

rust-coding-standards

Load when: writing any Rust code, reviewing code quality, authoring documentation, or working with content workflows. Covers: Idiomatic Rust patterns, code locations (extensions/*/src/), naming conventions, error handling, documentation standards, content workflows, quality patterns. This is the foundational skill — load it alongside any other skill.

extension-building

Load when: building or modifying library extensions (non-CLI, non-MCP Rust code). Covers: Extension architecture, traits, schemas, API routes, jobs, code review patterns. Reference implementation: extensions/web/. Core principle: Rust code = extension, YAML/Markdown = service. Never modify core/ (git submodule).

cli-extension-building

Load when: building standalone CLI tools that integrate with systemprompt. Covers: Clap-based CLI setup, manifest.yaml discovery, subprocess integration, argument parsing, output formatting. Reference implementation: extensions/cli/discord/. CLI extensions run as separate processes via systemprompt plugins run <name>.

mcp-building

Load when: building MCP (Model Context Protocol) servers. Covers: MCP server architecture, tool definitions, artifacts, UI resources, AI service integration, module.yml configuration. Reference implementation: extensions/mcp/systemprompt/. MCP servers live in /extensions/mcp/.

Task Router

I want to...	Load these skills
Write any Rust code	`rust-coding-standards`
Build a library extension	`extension-building` + `rust-coding-standards`
Build a CLI tool	`cli-extension-building` + `rust-coding-standards`
Build an MCP server	`mcp-building` + `rust-coding-standards`
Review Rust code quality	`rust-coding-standards`
Add API routes to an extension	`extension-building` + `rust-coding-standards`
Full extension build or review	All relevant skills + `rust-coding-standards`

Skill Dependencies

rust-coding-standards (always required for any Rust work)
        |
        +---> extension-building (library extensions)
        |
        +---> cli-extension-building (CLI binaries)
        |
        +---> mcp-building (MCP servers)

For any task: always load rust-coding-standards first. Then load the specific skill for your extension type.

---name: rust-dev-guidedescription: Entry point for rust-development — routes to the right sub-skill for your task---# Rust DevelopmentBuild Rust extensions, CLI binaries, and MCP servers for systemprompt.io. This plugin covers all Rust development from coding standards to specific extension types.---## Skills### rust-coding-standards**Load when:** writing any Rust code, reviewing code quality, authoring documentation, or working with content workflows.**Covers:** Idiomatic Rust patterns, code locations (`extensions/*/src/`), naming conventions, error handling, documentation standards, content workflows, quality patterns. This is the foundational skill — load it alongside any other skill.### extension-building**Load when:** building or modifying library extensions (non-CLI, non-MCP Rust code).**Covers:** Extension architecture, traits, schemas, API routes, jobs, code review patterns. Reference implementation: `extensions/web/`. Core principle: Rust code = extension, YAML/Markdown = service. Never modify `core/` (git submodule).### cli-extension-building**Load when:** building standalone CLI tools that integrate with systemprompt.**Covers:** Clap-based CLI setup, `manifest.yaml` discovery, subprocess integration, argument parsing, output formatting. Reference implementation: `extensions/cli/discord/`. CLI extensions run as separate processes via `systemprompt plugins run <name>`.### mcp-building**Load when:** building MCP (Model Context Protocol) servers.**Covers:** MCP server architecture, tool definitions, artifacts, UI resources, AI service integration, `module.yml` configuration. Reference implementation: `extensions/mcp/systemprompt/`. MCP servers live in `/extensions/mcp/`.---## Task Router| I want to... | Load these skills ||--------------|-------------------|| Write any Rust code | `rust-coding-standards` || Build a library extension | `extension-building` + `rust-coding-standards` || Build a CLI tool | `cli-extension-building` + `rust-coding-standards` || Build an MCP server | `mcp-building` + `rust-coding-standards` || Review Rust code quality | `rust-coding-standards` || Add API routes to an extension | `extension-building` + `rust-coding-standards` || Full extension build or review | All relevant skills + `rust-coding-standards` |---## Skill Dependencies```rust-coding-standards (always required for any Rust work) | +---> extension-building (library extensions) | +---> cli-extension-building (CLI binaries) | +---> mcp-building (MCP servers)```**For any task:** always load `rust-coding-standards` first. Then load the specific skill for your extension type.

Frequently asked questions

Rust Dev Guide