m07-concurrency
CRITICAL: Use for concurrency/async. Triggers: E0277 Send Sync, cannot be sent between threads, thread, spawn, channel, mpsc, Mutex, RwLock, Atomic, async, await, Future, tokio, deadlock, race condition, 并发, 线程, 异步, 死锁
78
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/m07-concurrency/SKILL.mdQuality
Discovery
62%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger term coverage with comprehensive Rust concurrency keywords, error codes, and multilingual support, making it highly discoverable. However, it critically fails to describe what the skill actually does - there are no concrete actions or capabilities listed, only a domain label. The description reads more like a keyword index than a skill description.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Diagnoses and fixes Rust concurrency issues including Send/Sync trait bounds, thread safety problems, and async/await patterns.'
Restructure to lead with capabilities before the trigger list, e.g., 'Resolves Rust threading errors, implements safe concurrent patterns, debugs deadlocks and race conditions. Use when...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Use for concurrency/async' without listing any concrete actions. It doesn't describe what the skill actually does - no verbs like 'diagnose', 'fix', 'implement', or 'analyze'. | 1 / 3 |
Completeness | The 'when' is well-covered through the extensive trigger list, but the 'what' is extremely weak - it only says 'Use for concurrency/async' without explaining what actions or help the skill provides. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including error codes (E0277), Rust-specific types (Mutex, RwLock, mpsc), async runtime (tokio), common problems (deadlock, race condition), and even multilingual terms (并发, 线程, 异步, 死锁). | 3 / 3 |
Distinctiveness Conflict Risk | The highly specific Rust concurrency terms (Send, Sync, E0277, tokio, mpsc) create a clear niche that is unlikely to conflict with other skills. The error code and type-specific triggers are very distinctive. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured diagnostic skill that excels at guiding decision-making for concurrency problems. Its strength lies in the error-to-design-question mapping and clear decision flowcharts. The main weakness is limited executable code examples - it tells you what to use but doesn't always show complete implementations.
Suggestions
Add complete, executable code examples for the most common patterns (e.g., full Arc<Mutex<T>> usage with tokio::spawn, complete channel-based message passing example)
Include a concrete before/after code example for the 'Non-Send Types in Async' section showing each of the three options in runnable form
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables, flowcharts, and minimal prose. Every section earns its place with no unnecessary explanations of concepts Claude already knows. | 3 / 3 |
Actionability | Provides good decision frameworks and error mappings, but lacks executable code examples. The code snippets shown are minimal patterns rather than copy-paste ready solutions. The 'Avoid MutexGuard Across Await' section shows patterns but not complete working examples. | 2 / 3 |
Workflow Clarity | Clear decision flowchart with explicit branching logic. The 'Trace Up' and 'Trace Down' sections provide excellent sequenced thinking processes with validation checkpoints (domain detection, constraint checking). | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections and appropriate references to related skills (m02-resource, m03-mutability, domain-*). Content is appropriately structured with quick reference tables for scanning and detailed sections for deeper understanding. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- actionbook/rust-skills
- Commit
1f4becd
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.