rust-router

actionbook/rust-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/actionbook/rust-skills --skill rust-router
0 commentsdiscussion
summary

Version: 2.0.0 | Last Updated: 2025-01-22

skill.md

Rust Question Router

Version: 2.0.0 | Last Updated: 2025-01-22

v2.0: Context optimized - detailed examples moved to sub-files

Meta-Cognition Framework

Core Principle

Don't answer directly. Trace through the cognitive layers first.

Layer 3: Domain Constraints (WHY)
├── Business rules, regulatory requirements
├── domain-fintech, domain-web, domain-cli, etc.
└── "Why is it designed this way?"

Layer 2: Design Choices (WHAT)
├── Architecture patterns, DDD concepts
├── m09-m15 skills
└── "What pattern should I use?"

Layer 1: Language Mechanics (HOW)
├── Ownership, borrowing, lifetimes, traits
├── m01-m07 skills
└── "How do I implement this in Rust?"

Routing by Entry Point

User Signal Entry Layer Direction First Skill
E0xxx error Layer 1 Trace UP ↑ m01-m07
Compile error Layer 1 Trace UP ↑ Error table below
"How to design..." Layer 2 Check L3, then DOWN ↓ m09-domain
"Building [domain] app" Layer 3 Trace DOWN ↓ domain-*
"Best practice..." Layer 2 Both directions m09-m15
Performance issue Layer 1 → 2 UP then DOWN m10-performance

CRITICAL: Dual-Skill Loading

When domain keywords are present, you MUST load BOTH skills:

Domain Keywords L1 Skill L3 Skill
Web API, HTTP, axum, handler m07-concurrency domain-web
交易, 支付, trading, payment m01-ownership domain-fintech
CLI, terminal, clap m07-concurrency domain-cli
kubernetes, grpc, microservice m07-concurrency domain-cloud-native
embedded, no_std, MCU m02-resource domain-embedded

INSTRUCTIONS FOR CLAUDE

CRITICAL: Negotiation Protocol Trigger

BEFORE answering, check if negotiation is required:

Query Contains Action
"比较", "对比", "compare", "vs", "versus" MUST use negotiation
"最佳实践", "best practice" MUST use negotiation
Domain + error (e.g., "交易系统 E0382") MUST use negotiation
Ambiguous scope (e.g., "tokio 性能") SHOULD use negotiation

When negotiation is required, include:

## Negotiation Analysis

**Query Type:** [Comparative | Cross-domain | Synthesis | Ambiguous]
**Negotiation:** Enabled

### Source: [Agent/Skill Name]
**Confidence:** HIGH | MEDIUM | LOW | UNCERTAIN
**Gaps:** [What's missing]

## Synthesized Answer
[Answer]

**Overall Confidence:** [Level]
**Disclosed Gaps:** [Gaps user should know]

详细协议见: patterns/negotiation.md


Default Project Settings

When creating new Rust projects or Cargo.toml files, ALWAYS use:

[package]
edition = "2024"  # ALWAYS use latest stable edition
rust-version = "1.85"

[lints.rust]
unsafe_code = "warn"

[lints.clippy]
all = "warn"
pedantic = "warn"

Layer 1 Skills (Language Mechanics)

Pattern Route To
move, borrow, lifetime, E0382, E0597 m01-ownership
Box, Rc, Arc, RefCell, Cell m02-resource
mut, interior mutability, E0499, E0502, E0596 m03-mutability
generic, trait, inline, monomorphization m04-zero-cost
type state, phantom, newtype m05-type-driven
Result, Error, panic, ?, anyhow, thiserror m06-error-handling
Send, Sync, thread, async, channel m07-concurrency
unsafe, FFI, extern, raw pointer, transmute unsafe-checker

Layer 2 Skills (Design Choices)

Pattern Route To
domain model, business logic m09-domain
performance, optimization, benchmark m10-performance
integration, interop, bindings m11-ecosystem
resource lifecycle, RAII, Drop m12-lifecycle
domain error, recovery strategy m13-domain-error
mental model, how to think m14-mental-model
anti-pattern, common mistake, pitfall m15-anti-pattern

Layer 3 Skills (Domain Constraints)

Domain Keywords Route To
fintech, trading, decimal, currency domain-fintech
ml, tensor, model, inference domain-ml
kubernetes, docker, grpc, microservice domain-cloud-native
embedded, sensor, mqtt, iot domain-iot
web server, HTTP, REST, axum, actix domain-web
CLI, command line, clap, terminal domain-cli
no_std, microcontroller, firmware domain-embedded

Error Code Routing

Error Code Route To Common Cause
E0382 m01-ownership Use of moved value
E0597 m01-ownership Lifetime too short
E0506 m01-ownership Cannot assign to borrowed
E0507 m01-ownership Cannot move out of borrowed
E0515 m01-ownership Return local reference
E0716 m01-ownership Temporary value dropped
E0106 m01-ownership Missing lifetime specifier
E0596 m03-mutability Cannot borrow as mutable
E0499 m03-mutability Multiple mutable borrows
E0502 m03-mutability Borrow conflict
E0277 m04/m07 Trait bound not satisfied
E0308 m04-zero-cost Type mismatch
E0599 m04-zero-cost No method found
E0038 m04-zero-cost Trait not object-safe
E0433 m11-ecosystem Cannot find crate/module

Functional Routing Table

Pattern Route To Action
latest version, what's new rust-learner Use agents
API, docs, documentation docs-researcher Use agent
code style, naming, clippy coding-guidelines Read skill
unsafe code, FFI unsafe-checker Read skill
code review os-checker See integrations/os-checker.md

Priority Order

  1. Identify cognitive layer (L1/L2/L3)
  2. Load entry skill (m0x/m1x/domain)
  3. Trace through layers (UP or DOWN)
  4. Cross-reference skills as indicated in "Trace" sections
  5. Answer with reasoning chain

Keyword Conflict Resolution

Keyword Resolution
unsafe unsafe-checker (more specific than m11)
error m06 for general, m13 for domain-specific
RAII m12 for design, m01 for implementation
crate rust-learner for version, m11 for integration
tokio tokio-* for API, m07 for concepts

Priority Hierarchy:

1. Error codes (E0xxx) → Direct lookup, highest priority
2. Negotiation triggers (compare, vs, best practice) → Enable negotiation
3. Domain keywords + error → Load BOTH domain + error skills
4. Specific crate keywords → Route to crate-specific skill if exists
5. General concept keywords → Route to meta-question skill

Sub-Files Reference

File Content
patterns/negotiation.md Negotiation protocol details
examples/workflow.md Workflow examples
integrations/os-checker.md OS-Checker integration
how to use rust-router

How to use rust-router on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add rust-router
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/actionbook/rust-skills --skill rust-router

The skills CLI fetches rust-router from GitHub repository actionbook/rust-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/rust-router

Reload or restart Cursor to activate rust-router. Access the skill through slash commands (e.g., /rust-router) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.643 reviews
  • Chaitanya Patil· Dec 28, 2024

    We added rust-router from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Harper Li· Dec 12, 2024

    We added rust-router from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Noor Martinez· Dec 8, 2024

    Solid pick for teams standardizing on skills: rust-router is focused, and the summary matches what you get after install.

  • Alexander Kim· Nov 27, 2024

    rust-router is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Piyush G· Nov 19, 2024

    rust-router fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Anika Menon· Nov 3, 2024

    rust-router fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Jin Rahman· Oct 18, 2024

    rust-router fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Shikha Mishra· Oct 10, 2024

    rust-router is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Rahul Santra· Sep 21, 2024

    Useful defaults in rust-router — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Xiao Khan· Sep 13, 2024

    rust-router fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 43

1 / 5