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, 嵌入式, 单片机, 固件, 裸机

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/domain-embedded/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, actionable embedded-Rust reference with a strong executable code example, but it suffers from redundant restating of the same constraint-to-pattern mappings and lacks an explicit operational workflow with validation checkpoints.

Suggestions

Consolidate the repeated no-heap and ISR-safety mappings so each appears once (e.g., in the Domain Constraints table) and remove the redundant Trace sections to cut tokens.

Trim the basic-fact restatements ('No heap -> Stack allocation', 'No std -> Core only') that Claude already knows, keeping only the Rust-specific implications.

Add a short ordered workflow with a validation step for the common case (e.g., confirm no_std in Cargo.toml, apply the static-state pattern, build with probe-run and check for heap/allocator errors) to give the skill an operational spine.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference material, but the no-heap and ISR-safety mappings are restated across the Domain Constraints, Critical Constraints, Trace Down, Design Patterns, and Trace to Layer 1 sections, and basic facts like 'No heap -> Stack allocation' restate concepts Claude already knows, so it could be tightened.	3 / 5
Actionability	Concrete guidance is strong — a complete executable Static Peripheral Rust example plus specific crate names (heapless, cortex-m-rt, defmt, probe-run) and concrete patterns (Mutex<RefCell<Option<T>>>) — with only minor gaps in coverage of other common tasks since the remaining guidance is tabular reference rather than runnable commands.	4 / 5
Workflow Clarity	The Trace Down and Trace to Layer 1 sections provide a loose conceptual sequence (constraints -> design -> implementation) but there is no operational multi-step workflow with validation checkpoints, matching 'sequence present but checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	The body is well-organized with clear section headers and self-contained one-level structure (no nested references), no bundle files exist to reference, and most content is appropriately placed, matching 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	14 / 20 Passed

Description

58%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has excellent trigger-term coverage and a distinct, low-conflict niche, but it omits any explicit statement of what the skill does, leaving completeness and specificity weak.

Suggestions

Add a leading 'what' clause naming concrete actions the skill performs (e.g., 'Applies embedded/no_std Rust domain constraints and design patterns. Use when...') to raise completeness and specificity.

Include a couple of natural file-extension or config triggers (e.g., '.rs', 'Cargo.toml', 'memory.x') alongside the keywords to round out trigger-term coverage.

Open with a third-person capability verb phrase ('Applies', 'Guides', 'Checks') so the description reads as a capability rather than only a trigger.

Dimension	Reasoning	Score
Specificity	The phrase 'Use when developing embedded/no_std Rust' names the domain concretely but lists no concrete actions (no verbs like 'extract', 'configure', 'generate'), matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	Only the 'when' is explicit ('Use when developing embedded/no_std Rust'); there is no statement of what the skill does, matching the anchor 'only when is present without what'.	2 / 5
Trigger Term Quality	The keyword list is comprehensive and includes natural synonyms and variant spellings (embedded, no_std, MCU, bare metal, HAL, RTIC, embassy, esp32, stm32, plus Chinese terms 嵌入式/单片机/固件/裸机), matching the 'comprehensive coverage of natural terms including synonyms' anchor.	5 / 5
Distinctiveness Conflict Risk	The niche is sharply defined (embedded/no_std Rust with specific frameworks/chips), giving it distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: actionbook/rust-skills
Path: skills/domain-embedded/SKILL.md
Commit: 5c40d3a

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

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.