rust-async

Enforces bounded concurrency and cooperative cancellation for Rust async code.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/cecon123/tg-remote-bot --skill rust-async-cecon123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-async
Source: https://github.com/cecon123/tg-remote-bot/tree/main/.agents/skills/rust-async
Command: npx skills add https://github.com/cecon123/tg-remote-bot --skill rust-async-cecon123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Async Rust development often struggles to maintain correctness under cancellation, backpressure, and partial failures. This skill provides proven patterns and practical guidance for building reliable, scalable async systems.

Core Features & Use Cases

  • Bounded concurrency and backpressure to avoid resource exhaustion in I/O-bound services.
  • Structured cancellation and timeout strategies to enable graceful shutdowns.
  • Patterns for streams, join/try_join, and cooperative cancellation across tasks in production services with Rust async runtimes (Tokio/async-std).
  • Real-world examples illustrating safe error handling and resource cleanup.

Quick Start

Provide a ready-to-run Rust example using Tokio that demonstrates bounded concurrency and cooperative cancellation.

Frequently Asked Questions about rust-async

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

FAQPage Schema
How do I handle cancellation safely in async Rust tasks?

Prevent resource exhaustion in async Rust I/O services by enforcing bounded concurrency and applying backpressure. These patterns limit active tasks and buffer sizes to keep your streaming data and API clients stable under heavy load.

How do I prevent resource exhaustion in async Rust I/O services?

Prevent resource exhaustion in async Rust I/O services by enforcing bounded concurrency and applying backpressure. These patterns limit active tasks and buffer sizes to keep your streaming data and API clients stable under heavy load.

What is the best way to manage streams and try_join in Tokio production services?

Async Rust code often hangs or leaks resources because it lacks explicit timeout boundaries and deterministic cleanup. Applying structured concurrency patterns ensures tasks are cancelled cooperatively and resources are released safely during partial failures.

Why does my async Rust code hang or leak resources during partial failures?

Async Rust code often hangs or leaks resources because it lacks explicit timeout boundaries and deterministic cleanup. Applying structured concurrency patterns ensures tasks are cancelled cooperatively and resources are released safely during partial failures.

Does this approach work with both Tokio and async-std runtimes?

Test async Rust cancellation and backpressure logic by verifying deterministic resource cleanup and explicit timeout boundaries. The patterns include guidance for testing and verification to ensure your code remains correct under load and partial failures.

How do I test async Rust cancellation and backpressure logic?

Test async Rust cancellation and backpressure logic by verifying deterministic resource cleanup and explicit timeout boundaries. The patterns include guidance for testing and verification to ensure your code remains correct under load and partial failures.