rust-async
Skill0 starsChanged 26 days agoMITView on GitHub
Rust async with tokio or async-std: guards across await, detached tasks, blocking work, cancellation and shutdown. Trigger: When writing or reviewing async Rust in a package that declares tokio or async-std.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- adxptived/Rust-Skillstheir own version, first seen Oct 17, 2026
- takurot/rust-skills-comprehensivetheir own version, first seen Oct 15, 2026
- dawidpereira/rust-skillstheir own version, first seen Mar 22, 2026
- huiali/rust-skillstheir own version, first seen Feb 9, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- huiali/rust-skills★ 47same name
- adxptived/Rust-Skills★ 1same name
- dawidpereira/rust-skills★ 0same name
- takurot/rust-skills-comprehensive★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository219 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/behavioral-discipline.mdcCursor rule
- .cursor/rules/context-budget.mdcCursor rule
- .cursor/rules/orchestration.mdcCursor rule
- .cursor/rules/yagni-stdlib.mdcCursor rule
- androidSkill
- android-ui-designSkill
- api-versioningSkill
- astroSkill
- auth-token-inspectorSkill
- backlogSkill
- cc-api-contractSkill
- cc-db-migrationSkill
- cc-featureSkill
- cc-fixSkill
- cc-pagespeedSkill
- cc-refactorSkill
- cc-reviewSkill
- cc-spec-mutationSkill
- cc-tdd-cycleSkill
- cc-test-planSkill
- code-reviewSkill
- commitSkill
- conductor-setupSkill
- councilSkill
- database-migrationsSkill
- django-ormSkill
- django-testingSkill
- django-uvSkill
- drizzle-schema-architectSkill
- evaluationSkill
- fastapi-pydantic-strictSkill
- find-skillsSkill
- jpa-nplusone-detectorSkill
- jpa-postgresSkill
- laravel-specialistSkill
- livewire-alpine-bridgeSkill
- multi-agent-orchestrationSkill
- nextjs-typescriptSkill
- openspecSkill
- pagespeed-insightsSkill
- pagespeed-perfSkill
- php-proSkill
- python-django-stackSkill
- python-fastapi-stackSkill
- pythonSkill
- rust-engineeringSkill
- rust-sqlxSkill
- security-ai-llmSkill
- security-blue-teamSkill
- security-cloudSkill
- security-cryptoSkill
- security-exploit-devSkill
- security-grcSkill
- security-incident-responseSkill
- security-log-analysisSkill
- security-malware-analysisSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
Do not change runtime flavor or add features without a Task Card line.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Rust async
Activation
Apply when the owning package declares tokio or async-std as a normal
dependency and the change touches async fn, .await, spawn or channels.
Inputs
- Declared runtime, its features (
rt,rt-multi-thread,sync,time). - Existing shutdown path (
CancellationToken, signal handler,JoinSet).
Procedure
- Guards across await (
rust.guard-across-await). Condition: astd::sync::MutexGuard/RwLockguard orRefCellborrow is live at an.await. Action: scope the guard in a block that ends before the await, or copy out the data. Usetokio::sync::Mutexonly when the lock must be held across the await. Exception: none for std guards (the future becomes!Sendor can deadlock). Verify:cargo check; aSendbound compile error onspawnis the signal. - Detached tasks (
rust.detached-task). Condition:spawnresult is dropped. Action: dropping aJoinHandledetaches the task; keep the handle or use aJoinSet, and decide who observes panics and errors. Exception: fire-and-forget with logged failure and no shutdown dependency. Verify: eachspawnhas an owner that is awaited or aborted at shutdown. - Blocking work. Condition: CPU-heavy or blocking I/O inside async code.
Action:
tokio::task::spawn_blocking. Exception: work shorter than a scheduling quantum. Verify: nostd::thread::sleepor blockingstd::fs/std::netcall in anasync fn. - Cancellation. Condition: a future may be dropped at any
.await. Action: keep state consistent at every await; use cancel-safe operations inselect!.abort()does not stop aspawn_blockingtask that already started. Exception: none. Verify: a test that drops the future mid-operation. - Shutdown. Condition: the service owns tasks. Action: signal, then await
handles with a timeout. Started
spawn_blockingtasks run to completion, so bound their runtime. Verify: a test or run that shuts down without hanging.
Decisions and exceptions
- Do not change runtime flavor or add features without a Task Card line.
async-stdandtokioAPIs differ; follow the declared runtime only.- Unbounded channels need a stated reason; default to bounded.
Evidence
cargo test -p <package> with the exit code, plus the named test that drops
or aborts the future. Report unverified cancellation paths as unverified.
References
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

