coding-guidelines
Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT,…
Internal command support for dynamic Rust crate skill management. Use only when explicitly invoked by /sync-crate-skills, /clean-crate-skills, or /update-crate-skill.
$ npx -y skills add zhanghandong/rust-skills --skill core-dynamic-skills --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/core-dynamic-skillsContext preview
The summary Claude sees to decide when to auto-load this skill.
Internal command support for dynamic Rust crate skill management. Use only when explicitly invoked by /sync-crate-skills, /clean-crate-skills, or /update-crate-skill.
name: core-dynamic-skills description: "Internal command support for dynamic Rust crate skill management. Use only when explicitly invoked by /sync-crate-skills, /clean-crate-skills, or /update-crate-skill." disable-model-invocation: true argument-hint: "[--force] | <crate_name>" context: fork agent: general-purpose
> **Version:** 2.1.0 | **Last Updated:** 2025-01-27
Orchestrates on-demand generation of crate-specific skills based on project dependencies.
Dynamic skills are:
When entering a directory with Cargo.toml: 1. Detect Cargo.toml (single or workspace) 2. Parse dependencies list 3. Check which crates are missing skills 4. If missing: "Found X dependencies without skills. Sync now?" 5. If confirmed: run `/sync-crate-skills`
**CRITICAL: Check if agent and command infrastructure is available.**
Try to read: `../../agents/` directory Check if `/create-llms-for-skills` and `/create-skills-via-llms` commands work.
---
**When full plugin infrastructure is available:**
Cargo.toml
↓
Parse dependencies
↓
For each crate:
├─ Check ~/.claude/skills/{crate}/
├─ If missing: Check actionbook for llms.txt
│ ├─ Found: /create-skills-via-llms
│ └─ Not found: /create-llms-for-skills first
└─ Load skill1. **actionbook MCP** - Check for pre-generated llms.txt 2. **/create-llms-for-skills** - Generate llms.txt from docs.rs 3. **/create-skills-via-llms** - Create skills from llms.txt
/sync-crate-skills [--force]
1. Parse Cargo.toml for dependencies 2. For each dependency:
3. Report results
---
**When agent/command infrastructure is NOT available, execute manually:**
# Read dependencies cat Cargo.toml | grep -A 100 '\[dependencies\]' | grep -E '^[a-zA-Z]'
Or use Read tool to parse Cargo.toml and extract:
# List existing skills ls ~/.claude/skills/
Compare with dependencies to find missing skills.
For each missing crate:
# 1. Fetch crate documentation
agent-browser open "https://docs.rs/{crate}/latest/{crate}/"
agent-browser get text ".docblock"
# Save content
# 2. Create skill directory
mkdir -p ~/.claude/skills/{crate}
mkdir -p ~/.claude/skills/{crate}/references
# 3. Create SKILL.md
# Use template from rust-skill-creator inline mode
# 4. Create reference files for key modules
agent-browser open "https://docs.rs/{crate}/latest/{crate}/{module}/"
agent-browser get text ".docblock"
# Save to ~/.claude/skills/{crate}/references/{module}.md
agent-browser close**WebFetch fallback:**
WebFetch("https://docs.rs/{crate}/latest/{crate}/", "Extract API documentation overview, key types, and usage examples")For Cargo workspace projects:
# 1. Parse root Cargo.toml for workspace members
cat Cargo.toml | grep -A 10 '\[workspace\]'
# 2. For each member, parse their Cargo.toml
for member in members; do
cat ${member}/Cargo.toml | grep -A 100 '\[dependencies\]'
done
# 3. Aggregate and deduplicate dependencies
# 4. Generate skills for missing crates# Clean specific crate
rm -rf ~/.claude/skills/{crate_name}
# Clean all generated skills
rm -rf ~/.claude/skills/*# Remove old skill
rm -rf ~/.claude/skills/{crate_name}
# Re-generate (same as sync for single crate)
# Follow Step 3 above for the specific crate---
~/.claude/skills/
├── tokio/
│ ├── SKILL.md
│ └── references/
├── serde/
│ ├── SKILL.md
│ └── references/
└── axum/
├── SKILL.md
└── references/---
| Error | Cause | Solution | |-------|-------|----------| | Commands not found | Skills-only install | Use inline mode | | Cargo.toml not found | Not in Rust project | Navigate to project root | | docs.rs unavailable | Network issue | Retry or skip crate | | Permission denied | Directory issue | Check ~/.claude/skills/ permissions |
AI-powered Rust development assistant with meta-cognition framework
Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT,…
Internal support skill for actionbook MCP selectors used by Rust documentation research workflows. Use only when another rust-skills workflow explicitly…
Internal support skill for agent-browser CLI workflows used by rust-learner, docs-researcher, and crate-researcher. Use only when browser automation is…
Internal maintenance support for checking and fixing generated Rust skill documentation references. Use only when explicitly invoked by /fix-skill-docs.
Use when building CLI tools. Keywords: CLI, command line, terminal, clap, structopt, argument parsing, subcommand, interactive, TUI, ratatui, crossterm,…
Use when building cloud-native apps. Keywords: kubernetes, k8s, docker, container, grpc, tonic, microservice, service mesh, observability, tracing, metrics,…