Rust Async Patterns — Tokio tasks, channels, streams, error handling
Thin router skill for production async Rust with Tokio: tasks, channels, streams and error handling — detailed patterns live in the bundled resources/implementation-playbook.md in the repo
- What
- Thin router skill for production async Rust with Tokio: tasks, channels, streams and error handling — detailed patterns live in the bundled resources/implementation-playbook.md in the repo
- Cost
- Free
- Needs
- an async Rust project using Tokio — the skill is a router the agent follows, not software; the detailed content lives in the bundled resources/implementation-playbook.md
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @sickn33's rust-async-patterns: a router-style skill for production async Rust programming with the Tokio runtime — tasks, channels, streams and error handling, for building async applications, implementing concurrent network services, or debugging async code. It defines when to use (and not use) the skill, an instruction loop (clarify goals, apply best practices, validate outcomes, provide actionable steps and verification), and points to the bundled `resources/implementation-playbook.md` for the detailed patterns and examples. Honest caveats: deliberately thin by design — most of the substance lives in the bundled playbook inside the repo, not in the SKILL.md itself; scope limitations are stated explicitly (only within its scope, never a substitute for environment-specific validation or expert review). The skill's frontmatter states no license; the catalog manifest records MIT — manifest takes precedence. MIT licensed per the manifest. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: an async Rust project using Tokio — the skill is a router the agent follows, not software; the detailed content lives in the bundled resources/implementation-playbook.md Install "Rust Async Patterns — Tokio tasks, channels, streams, error handling" for me. It gives my agent @sickn33's async-Rust entry point: when to use it (building async Rust apps, concurrent network services, Tokio async I/O, async error handling, debugging, performance), when not to, an instruction loop (clarify goals and constraints, apply best practices, validate outcomes, provide actionable steps and verification), and the pointer to resources/implementation-playbook.md for the detailed patterns and examples. License note: the skill's frontmatter states no license; the catalog manifest records MIT — manifest takes precedence. Repository: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/rust-async-patterns/SKILL.md 1. Fetch the SKILL.md file (and the bundled resources/implementation-playbook.md) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "rust-async-patterns". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (nothing — it's a router guide the agent applies when working on async Rust). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.