domain-embedded
Use when developing embedded/no_std Rust. Keywords: embedded, no_std, microcontroller, MCU, ARM, RISC-V, bare metal, firmware, HAL, PAC, RTIC, embassy, interrupt, DMA, peripheral, GPIO, SPI, I2C, UART, embedded-hal, cortex-m, esp32, stm32, nrf, 嵌入式, 单片机, 固件, 裸机
72
66%
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/domain-embedded/SKILL.mdQuality
Discovery
44%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 embedded Rust keywords but critically fails to describe what the skill actually does. It's essentially a keyword list with a 'Use when' clause but no capability description, making it impossible for Claude to understand what actions this skill enables.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Assists with peripheral configuration, interrupt handling, memory-mapped register access, and HAL/PAC usage for embedded Rust development.'
Structure as 'what + when' format: Start with capabilities (what it does), then follow with the trigger guidance and keywords.
Consider condensing the keyword list and integrating key terms naturally into capability descriptions rather than presenting as a raw list.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks any concrete actions - it only states 'Use when developing' without describing what the skill actually does (e.g., 'configures peripherals', 'writes interrupt handlers', 'generates HAL code'). | 1 / 3 |
Completeness | While the 'when' is addressed with 'Use when developing embedded/no_std Rust', the 'what' is completely missing - there's no description of what capabilities or actions this skill provides. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural keywords including hardware platforms (ARM, RISC-V, esp32, stm32, nrf), protocols (SPI, I2C, UART), frameworks (RTIC, embassy), and even Chinese terms (嵌入式, 单片机). Users would naturally use these terms. | 3 / 3 |
Distinctiveness Conflict Risk | The embedded/no_std Rust niche is highly specific and unlikely to conflict with other skills. The extensive keyword list (MCU, bare metal, firmware, HAL, PAC, specific chip families) creates a clear, distinct domain. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality embedded Rust skill that efficiently communicates domain constraints and their Rust implications through well-structured tables. The code example is complete and executable. The main weakness is the lack of explicit workflow sequences with validation steps for common embedded development tasks like flashing and debugging.
Suggestions
Add a brief workflow section for common tasks (e.g., build -> flash -> debug cycle) with validation checkpoints
Include a verification step in the code pattern showing how to confirm peripheral initialization succeeded
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables extensively to compress information. No unnecessary explanations of concepts Claude would know. Every section earns its place with actionable constraints and patterns. | 3 / 3 |
Actionability | Provides executable code pattern with complete no_std setup. Tables map constraints directly to Rust implementations. Common mistakes section gives specific fixes. The static peripheral example is copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill documents constraints and patterns well but lacks explicit workflow sequences for common embedded tasks. No validation checkpoints for flashing, debugging, or verifying peripheral setup. The code example shows usage but not a complete development workflow. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections and tables. References to related skills (m02-resource, m03-mutability, etc.) are one level deep and clearly signaled. The layer stack and trace sections provide good navigation without deep nesting. | 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.