[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77SVMCKXDSCWGF444DFH34Q":3,"skill-same:01M77SVMCKXDSCWGF444DFH34Q":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77SVMCKXDSCWGF444DFH34Q","rust-async-task-design",null,"Design and review Rust async code around task ownership, suspension points, cancellation, blocking work, and runtime boundaries. Use when writing, refactoring, or reviewing futures, async functions, Tokio tasks, spawn, JoinHandle, Send futures, async traits, cancellation, or mutexes across await points.","ConcertoNotes\u002Fcodex-plugins","ConcertoNotes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249301288?v=4","01M77NJ0BK2KN5YW0D8RHD99TB","01M77NJ0CCEDPATAY3JTXEWNK5",0,"MIT","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Frust-async-task-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rust-async-task-design\ndescription: Design and review Rust async code around task ownership, suspension points, cancellation, blocking work, and runtime boundaries. Use when writing, refactoring, or reviewing futures, async functions, Tokio tasks, spawn, JoinHandle, Send futures, async traits, cancellation, or mutexes across await points.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Rust Async Task Design\n  category: Rust\n  tags: rust,async,tokio,futures,tasks\n---\n\n# Rust Async Task Design\n\nUse this skill to make Rust async code explicit about task ownership, suspension\npoints, blocking work, and cancellation. Async is a concurrency model, not a\ndefault replacement for threads or a performance guarantee.\n\n## Core Workflow\n\n1. Identify the async boundary: runtime entrypoint, handler, client call,\n   stream, background task, or trait method.\n2. Mark every `.await` as a possible suspension point. Check what state is held\n   across it.\n3. Use `tokio::spawn(async move { ... })` only when the task can own everything\n   it needs and its future is `Send + 'static` on the selected runtime.\n4. Keep `JoinHandle`s when task success, panic, cancellation, or shutdown\n   matters. Do not silently detach important work.\n5. Keep blocking IO and CPU-heavy work out of async tasks. Use async APIs,\n   `spawn_blocking`, Rayon, or dedicated threads as the workload requires.\n6. Do not hold a synchronous `MutexGuard`, `RefCell` borrow, or non-`Send` value\n   across `.await`.\n7. Add tests for timeout, cancellation, dropped channel, and failed task paths\n   when those outcomes affect behavior.\n\n## Runtime Rules\n\nRead `references\u002Fasync-runtime-patterns.md` when reviewing task spawning,\nshared state in async code, or blocking work.\n\n- Use `std::sync::Mutex` in async code only for short, low-contention critical\n  sections that do not cross `.await`.\n- Use `tokio::sync::Mutex` when a lock must be held across `.await`, but first\n  consider moving the state behind a task and interacting by messages.\n- Use `spawn_blocking` for blocking operations that eventually finish. Limit\n  parallelism for CPU-heavy work; Tokio's blocking pool can grow large.\n- Use `tokio::time::timeout` or explicit cancellation tokens for bounded\n  operations.\n- Use `select!` carefully: dropping a future can cancel it. Check cancellation\n  safety before using it around IO or partially completed work.\n\n## Async Trait Rules\n\n- Native `async fn` in traits is fine for private traits and static dispatch\n  when callers do not need to add bounds to the returned future.\n- Public traits that need `Send` futures should usually spell the method as\n  `fn name(...) -> impl Future\u003COutput = T> + Send` or use `trait-variant` to\n  offer local and `Send` variants.\n- Public traits that need dynamic dispatch usually need an explicit boxed\n  future return type, such as `Pin\u003CBox\u003Cdyn Future\u003COutput = T> + Send + '_>>`.\n  Use `async-trait` as an ergonomics layer only when the dependency and\n  allocation tradeoff are acceptable.\n- Avoid leaking executor-specific types from a trait unless the trait is\n  intentionally runtime-specific.\n\n## Review Checklist\n\n- No lock or borrow crosses `.await` accidentally.\n- Spawned tasks own their inputs with `async move`.\n- Important `JoinHandle`s are awaited, monitored, or aborted on shutdown.\n- Blocking work is isolated and bounded.\n- Error paths preserve context instead of becoming `JoinError` or timeout noise.\n","# Rust Async Task Design\n\nUse this skill to make Rust async code explicit about task ownership, suspension\npoints, blocking work, and cancellation. Async is a concurrency model, not a\ndefault replacement for threads or a performance guarantee.\n\n## Core Workflow\n\n1. Identify the async boundary: runtime entrypoint, handler, client call,\n   stream, background task, or trait method.\n2. Mark every `.await` as a possible suspension point. Check what state is held\n   across it.\n3. Use `tokio::spawn(async move { ... })` only when the task can own everything\n   it needs and its future is `Send + 'static` on the selected runtime.\n4. Keep `JoinHandle`s when task success, panic, cancellation, or shutdown\n   matters. Do not silently detach important work.\n5. Keep blocking IO and CPU-heavy work out of async tasks. Use async APIs,\n   `spawn_blocking`, Rayon, or dedicated threads as the workload requires.\n6. Do not hold a synchronous `MutexGuard`, `RefCell` borrow, or non-`Send` value\n   across `.await`.\n7. Add tests for timeout, cancellation, dropped channel, and failed task paths\n   when those outcomes affect behavior.\n\n## Runtime Rules\n\nRead `references\u002Fasync-runtime-patterns.md` when reviewing task spawning,\nshared state in async code, or blocking work.\n\n- Use `std::sync::Mutex` in async code only for short, low-contention critical\n  sections that do not cross `.await`.\n- Use `tokio::sync::Mutex` when a lock must be held across `.await`, but first\n  consider moving the state behind a task and interacting by messages.\n- Use `spawn_blocking` for blocking operations that eventually finish. Limit\n  parallelism for CPU-heavy work; Tokio's blocking pool can grow large.\n- Use `tokio::time::timeout` or explicit cancellation tokens for bounded\n  operations.\n- Use `select!` carefully: dropping a future can cancel it. Check cancellation\n  safety before using it around IO or partially completed work.\n\n## Async Trait Rules\n\n- Native `async fn` in traits is fine for private traits and static dispatch\n  when callers do not need to add bounds to the returned future.\n- Public traits that need `Send` futures should usually spell the method as\n  `fn name(...) -> impl Future\u003COutput = T> + Send` or use `trait-variant` to\n  offer local and `Send` variants.\n- Public traits that need dynamic dispatch usually need an explicit boxed\n  future return type, such as `Pin\u003CBox\u003Cdyn Future\u003COutput = T> + Send + '_>>`.\n  Use `async-trait` as an ergonomics layer only when the dependency and\n  allocation tradeoff are acceptable.\n- Avoid leaking executor-specific types from a trait unless the trait is\n  intentionally runtime-specific.\n\n## Review Checklist\n\n- No lock or borrow crosses `.await` accidentally.\n- Spawned tasks own their inputs with `async move`.\n- Important `JoinHandle`s are awaited, monitored, or aborted on shutdown.\n- Blocking work is isolated and bounded.\n- Error paths preserve context instead of becoming `JoinError` or timeout noise.\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":28},{"tags":24,"version":25,"category":26,"displayName":27},"rust,async,tokio,futures,tasks","0.1.0","Rust","Rust Async Task Design","Codex, Claude Code, and other Agent Skills-compatible clients.","main","9ba3c9fadff1092395837bf1502e1b8a7f98b1e1","plugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Frust-async-task-design","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FConcertoNotes","2026-06-26 10:13:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ConcertoNotes\u002Fcodex-plugins --skill rust-async-task-design",{"tool":41,"command":42},"bunx","bunx skills add ConcertoNotes\u002Fcodex-plugins --skill rust-async-task-design",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ConcertoNotes\u002Fcodex-plugins --skill rust-async-task-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Frust-async-task-design\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",253,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Frust-async-task-design\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fasync-runtime-patterns.md",1643,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Frust-async-task-design\u002Freferences\u002Fasync-runtime-patterns.md",[60,69,76,84,91,98],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M77YB7WW36DS9AERTWP673E0","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M77Y7AA8N45G6NM0WJSS2W9C","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M77Y2W5H5YGSW7MYWEJ8HYXD","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M77Y06GV1DAME7PN9KBFHWRX","render-workflows","Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M77Y01A6RJA8VYT7CZ2TVETF","render-web-services","Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M77XZW1AZ6B6NZTWWFVY72T3","render-static-sites","Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React\u002FVue\u002FHugo\u002FGatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]