SkillAgentSearch skills...

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

Install / Use

npx skills add actionbook/rust-skills --skill domain-embedded

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Universal

Our assessment of domain-embedded

domain-embedded scores 89/100 on our quality scale, 1630th of 4,698 Development & Engineering skills we index (top 35%).

Its SKILL.md is 4.4 KB long, well organised into 16 sections with 5 code examples: a solid amount of guidance for an agent.

With 1,479 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so domain-embedded is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

domain-embedded compared with similar skills

All 4 of these similar skills score higher than domain-embedded; compare them before choosing.

SkillScoreStarsUpdatedFormat
domain-embedded (this skill)by actionbook891.5k3mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install domain-embedded?
Run npx skills add actionbook/rust-skills --skill domain-embedded. The install tabs above show the steps for each supported agent.
Which AI agents does domain-embedded work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is domain-embedded safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is domain-embedded still maintained?
The repository was last updated about 3 months ago, so domain-embedded is actively maintained.

name: domain-embedded description: "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, 嵌入式, 单片机, 固件, 裸机" globs: ["/Cargo.toml", "/.cargo/config.toml"] user-invocable: false

Project Context (Auto-Injected)

Target configuration: !cat .cargo/config.toml 2>/dev/null || echo "No .cargo/config.toml found"


Embedded Domain

Layer 3: Domain Constraints

Domain Constraints → Design Implications

| Domain Rule | Design Constraint | Rust Implication | |-------------|-------------------|------------------| | No heap | Stack allocation | heapless, no Box/Vec | | No std | Core only | #![no_std] | | Real-time | Predictable timing | No dynamic alloc | | Resource limited | Minimal memory | Static buffers | | Hardware safety | Safe peripheral access | HAL + ownership | | Interrupt safe | No blocking in ISR | Atomic, critical sections |


Critical Constraints

No Dynamic Allocation

RULE: Cannot use heap (no allocator)
WHY: Deterministic memory, no OOM
RUST: heapless::Vec<T, N>, arrays

Interrupt Safety

RULE: Shared state must be interrupt-safe
WHY: ISR can preempt at any time
RUST: Mutex<RefCell<T>> + critical section

Hardware Ownership

RULE: Peripherals must have clear ownership
WHY: Prevent conflicting access
RUST: HAL takes ownership, singletons

Trace Down ↓

From constraints to design (Layer 2):

"Need no_std compatible data structures"
    ↓ m02-resource: heapless collections
    ↓ Static sizing: heapless::Vec<T, N>

"Need interrupt-safe state"
    ↓ m03-mutability: Mutex<RefCell<Option<T>>>
    ↓ m07-concurrency: Critical sections

"Need peripheral ownership"
    ↓ m01-ownership: Singleton pattern
    ↓ m12-lifecycle: RAII for hardware

Layer Stack

| Layer | Examples | Purpose | |-------|----------|---------| | PAC | stm32f4, esp32c3 | Register access | | HAL | stm32f4xx-hal | Hardware abstraction | | Framework | RTIC, Embassy | Concurrency | | Traits | embedded-hal | Portable drivers |

Framework Comparison

| Framework | Style | Best For | |-----------|-------|----------| | RTIC | Priority-based | Interrupt-driven apps | | Embassy | Async | Complex state machines | | Bare metal | Manual | Simple apps |

Key Crates

| Purpose | Crate | |---------|-------| | Runtime (ARM) | cortex-m-rt | | Panic handler | panic-halt, panic-probe | | Collections | heapless | | HAL traits | embedded-hal | | Logging | defmt | | Flash/debug | probe-run |

Design Patterns

| Pattern | Purpose | Implementation | |---------|---------|----------------| | no_std setup | Bare metal | #![no_std] + #![no_main] | | Entry point | Startup | #[entry] or embassy | | Static state | ISR access | Mutex<RefCell<Option<T>>> | | Fixed buffers | No heap | heapless::Vec<T, N> |

Code Pattern: Static Peripheral

#![no_std]
#![no_main]

use cortex_m::interrupt::{self, Mutex};
use core::cell::RefCell;

static LED: Mutex<RefCell<Option<Led>>> = Mutex::new(RefCell::new(None));

#[entry]
fn main() -> ! {
    let dp = pac::Peripherals::take().unwrap();
    let led = Led::new(dp.GPIOA);

    interrupt::free(|cs| {
        LED.borrow(cs).replace(Some(led));
    });

    loop {
        interrupt::free(|cs| {
            if let Some(led) = LED.borrow(cs).borrow_mut().as_mut() {
                led.toggle();
            }
        });
    }
}

Common Mistakes

| Mistake | Domain Violation | Fix | |---------|-----------------|-----| | Using Vec | Heap allocation | heapless::Vec | | No critical section | Race with ISR | Mutex + interrupt::free | | Blocking in ISR | Missed interrupts | Defer to main loop | | Unsafe peripheral | Hardware conflict | HAL ownership |


Trace to Layer 1

| Constraint | Layer 2 Pattern | Layer 1 Implementation | |------------|-----------------|------------------------| | No heap | Static collections | heapless::Vec<T, N> | | ISR safety | Critical sections | Mutex<RefCell<T>> | | Hardware ownership | Singleton | take().unwrap() | | no_std | Core-only | #![no_std], #![no_main] |


Related Skills

| When | See | |------|-----| | Static memory | m02-resource | | Interior mutability | m03-mutability | | Interrupt patterns | m07-concurrency | | Unsafe for hardware | unsafe-checker |

Related Skills

View on GitHub
GitHub Stars1.5k
CategoryDevelopment
Updated2mo ago
Forks114

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium