rust-router

Routes Rust queries to layered, domain-specific skills for structured answers.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/yumazak/kodo --skill rust-router-yumazak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rust-router
Source: https://github.com/yumazak/kodo/tree/main/.agents/skills/rust-router
Command: npx skills add https://github.com/yumazak/kodo --skill rust-router-yumazak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route Rust questions through a layered, cross-skill reasoning system to deliver structured, domain-aware guidance.

Core Features & Use Cases

  • Dual-skill routing: loads language mechanics skills and domain skills when keywords indicate cross-domain context (e.g., ownership, concurrency, web, CLI).
  • Layered trace: traces queries UP and DOWN across L1/L2/L3 markers to surface rationale and recommended actions.
  • Negotiation-ready: supports comparative queries by routing to multiple knowledge sources and synthesizing results.

Quick Start

Ask a Rust question and let rust-router route it to the appropriate ownership, concurrency, or domain skills for a structured answer.

Frequently Asked Questions about rust-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix Rust borrow checker errors related to ownership and borrowing?▼

Rust ownership errors are routed through a layered reasoning system that loads language mechanics skills to provide structured guidance on borrowing conflicts, compile errors, and recommended code fixes.

How does Rust concurrency design handle cross-domain routing for web or CLI applications?▼

Rust concurrency design uses dual-skill routing to load both language mechanics and domain-specific skills when keywords trigger cross-domain context, synthesizing structured guidance for web or CLI environments.

What is the best way to debug Rust compile errors during structural design inquiries?▼

Debugging Rust compile errors through layered cross-skill reasoning traces queries across L1, L2, and L3 markers to surface rationale and deliver domain-aware design recommendations.

Can I compare multiple Rust ownership approaches using a single routing query?▼

Comparative Rust ownership queries are handled through negotiation-ready routing, which loads multiple knowledge sources and synthesizes results to provide a structured comparison.

Do I need specific dependencies to trace Rust concurrency or design questions through this system?▼

No dependencies are required to trace Rust concurrency or design questions; the system routes queries through frontmatter-driven skill identification and internal layered markers.

Why does my Rust routing query return synthesized responses instead of a single direct answer?▼

Rust routing queries return synthesized responses because the system loads multiple skills when cross-domain keywords are detected, negotiating between knowledge sources to provide comprehensive guidance.