Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
rust-best-practice - Skill - OpenSmartRoute
Skillv1.0.0
rust-best-practice
name: rust-best-practice description: [Critical] Best practice for Rust coding. Always activate this skill before authoring Rust code or answering questions about Rust. ---
Imported from abusch/gb-rs (.claude/skills/rust-best-practice/SKILL.md). Install upstream with npx skills add abusch/gb-rs --skill rust-best-practice. Copyright stays with the author.
name: rust-best-practice
description: [Critical] Best practice for Rust coding. Always activate this skill before authoring Rust code or answering questions about Rust.
Important dos and don'ts for working with Rust source code
Use cargo add to add new dependencies or features rather than editing Cargo.toml directly
Before finishing your turn, when editing Rust code:
Run cargo fmt after modifying Rust source files to ensure consistent formatting
Run tests (most commonly cargo test --all --workspace, though some projects may have other commands)
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
abusch-gb-rs-rust-best-practice.ocm.jsonjson
{
"ocm": "1",
"id": "abusch-gb-rs-rust-best-practice",
"kind": "skill",
"name": "rust-best-practice",
"description": "name: rust-best-practice description: [Critical] Best practice for Rust coding. Always activate this skill before authoring Rust code or answering questions about Rust. ---",
"publisher": "abusch",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"name: rust-best-practice description: [Critical] Best practice for Rust coding. Always activate this skill before authoring Rust code or answering questions about Rust. ---"
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/abusch/gb-rs",
"path": ".claude/skills/rust-best-practice/SKILL.md",
"ref": "dfc1cd0be12a530312add343912d0c6cad945e1a",
"url": "https://github.com/abusch/gb-rs/blob/dfc1cd0be12a530312add343912d0c6cad945e1a/.claude/skills/rust-best-practice/SKILL.md",
"key": "abusch/gb-rs/.claude/skills/rust-best-practice/SKILL.md"
}
},
"instructions": "---\nname: rust-best-practice\ndescription: [Critical] Best practice for Rust coding. Always activate this skill before authoring Rust code or answering questions about Rust.\n---\n\n# Important dos and don'ts for working with Rust source code\n\n* Use `cargo add` to add new dependencies or features rather than editing `Cargo.toml` directly\n* Before finishing your turn, when editing Rust code:\n * Run `cargo fmt` after modifying Rust source files to ensure consistent formatting\n * Run tests (most commonly `cargo test --all --workspace`, though some projects may have other commands)",
"cost": {
"context_tokens": 145
}
}
Fetch it by URL: GET /api/v1/registry/abusch-gb-rs-rust-best-practice/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
