Rust Skill Creator
Generate a reusable agent skill from docs.rs or Rust std documentation so coding agents stop hallucinating crate APIs.
Overview
Rust Skill Creator is an agent skill for the Build phase that generates dynamic skills from Rust crate and standard-library documentation URLs.
Install
npx skills add https://github.com/zhanghandong/rust-skills --skill rust-skill-creatorWhat is this skill?
- Creates dynamic skills from third-party crates (tokio, serde, axum) or std modules
- Maps user phrases and crate names to docs.rs and doc.rust-lang.org URL patterns
- Agent mode runs /create-llms-for-skills and /create-skills-via-llms when the plugin is installed
- Standalone fallback path when related commands are unavailable
- Bilingual trigger keywords (English and Chinese) for discovery
- Skill version 2.1.0 documented in SKILL.md header
Adoption & trust: 631 installs on skills.sh; 1.2k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent keeps guessing crate APIs because you do not have a maintained SKILL.md grounded in docs.rs or std reference pages.
Who is it for?
Solo builders maintaining a Rust agent skill library who want tokio, serde, axum, or std module skills generated from real docs.
Skip if: Non-Rust stacks, one-off answers that do not need a reusable skill, or environments where you cannot fetch documentation URLs.
When should I use this skill?
User asks to create a Rust crate or std library skill (e.g., tokio, serde, axum, Send trait) or provides a Rust documentation URL.
What do I get? / Deliverables
You get a new Rust-focused agent skill sourced from official documentation, ready for agents to invoke on later implementation tasks.
- New SKILL.md for the specified crate or std module
- LLM-oriented doc extract aligned to the skill workflow
Recommended Skills
Journey fit
Skill packaging for Rust libraries happens while you are building agent tooling and integrations, not during launch or growth marketing. Agent-tooling is the right shelf because the output is a SKILL.md package agents invoke—not application business logic.
How it compares
Skill packaging from official Rust docs—not a crates.io MCP server or inline Copilot-only hints.
Common Questions / FAQ
Who is rust-skill-creator for?
Rust indie builders and agent users who want documented crate and std behavior captured once as a reusable skill for Claude Code, Cursor, or Codex.
When should I use rust-skill-creator?
During Build while adding agent-tooling—whenever you say create a tokio skill, create a Send trait skill, or provide a docs.rs URL to turn into SKILL.md.
Is rust-skill-creator safe to install?
It may fetch public documentation and run doc-to-skill commands; review the Security Audits panel on this Prism page and avoid piping private doc URLs through untrusted automation.
SKILL.md
READMESKILL.md - Rust Skill Creator
# Rust Skill Creator > **Version:** 2.1.0 | **Last Updated:** 2025-01-27 > > Create dynamic skills for Rust crates and std library documentation. ## When to Use This skill handles requests to create skills for: - Third-party crates (tokio, serde, axum, etc.) - Rust standard library (std::sync, std::marker, etc.) - Any Rust documentation URL ## Execution Mode Detection **CRITICAL: Check if related commands/skills are available.** This skill relies on: - `/create-llms-for-skills` command - `/create-skills-via-llms` command --- ## Agent Mode (Plugin Install) **When the commands above are available (full plugin installation):** ### Workflow #### 1. Identify the Target | User Request | Target Type | URL Pattern | |--------------|-------------|-------------| | "create tokio skill" | Third-party crate | `docs.rs/tokio/latest/tokio/` | | "create Send trait skill" | Std library | `doc.rust-lang.org/std/marker/trait.Send.html` | | "create skill from URL" + URL | Custom URL | User-provided URL | #### 2. Execute the Command Use the `/create-llms-for-skills` command: ``` /create-llms-for-skills <url> [requirements] ``` **Examples:** ```bash # For third-party crate /create-llms-for-skills https://docs.rs/tokio/latest/tokio/ # For std library /create-llms-for-skills https://doc.rust-lang.org/std/marker/trait.Send.html # With specific requirements /create-llms-for-skills https://docs.rs/axum/latest/axum/ "Focus on routing and extractors" ``` #### 3. Follow-up with Skill Creation After llms.txt is generated, use: ``` /create-skills-via-llms <crate_name> <llms_path> [version] ``` --- ## Inline Mode (Skills-only Install) **When the commands above are NOT available, create skills manually:** ### Step 1: Identify Target and Construct URL | Target | URL Template | |--------|--------------| | Crate overview | `https://docs.rs/{crate}/latest/{crate}/` | | Crate module | `https://docs.rs/{crate}/latest/{crate}/{module}/` | | Std trait | `https://doc.rust-lang.org/std/{module}/trait.{Name}.html` | | Std struct | `https://doc.rust-lang.org/std/{module}/struct.{Name}.html` | | Std module | `https://doc.rust-lang.org/std/{module}/index.html` | ### Step 2: Fetch Documentation ```bash # Using agent-browser CLI agent-browser open "<documentation_url>" agent-browser get text ".docblock" agent-browser close ``` **Or with WebFetch fallback:** ``` WebFetch("<documentation_url>", "Extract API documentation including types, functions, and examples") ``` ### Step 3: Create Skill Directory ```bash mkdir -p ~/.claude/skills/{crate_name} mkdir -p ~/.claude/skills/{crate_name}/references ``` ### Step 4: Generate SKILL.md Create `~/.claude/skills/{crate_name}/SKILL.md` with this template: ```markdown --- name: {crate_name} description: "Documentation for {crate_name} crate. Keywords: {keywords}" --- # {Crate Name} > **Version:** {version} | **Source:** docs.rs ## Overview {Brief description from documentation} ## Key Types ### {Type1} {Description and usage} ### {Type2} {Description and usage} ## Common Patterns {Usage patterns extracted from documentation} ## Examples ```rust {Example code from documentation} ``` ## Documentation - `./references/overview.md` - Main overview - `./references/{module}.md` - Module documentation ## Links - [docs.rs](https://docs.rs/{crate}) - [crates.io](https://crates.io/crates/{crate}) ``` ### Step 5: Generate Reference Files For each major module or type, create a reference file: ```bash # Fetch and save module documentation a