embedded-systems
tessl i github:jeffallan/claude-skills --skill embedded-systemsUse when developing firmware for microcontrollers, implementing RTOS applications, or optimizing power consumption. Invoke for STM32, ESP32, FreeRTOS, bare-metal, power optimization, real-time systems.
Review Score
67%
Validation Score
12/16
Implementation Score
42%
Activation Score
90%
Generated
Validation
Total
12/16Score
Passed| Criteria | Score |
|---|---|
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata |
body_examples | No examples detected (no code fences and no 'Example' wording) |
Implementation
Suggestions 4
Score
42%Overall Assessment
This skill has excellent progressive disclosure structure with clear navigation to reference materials, but critically lacks actionable content. It reads more like a job description than executable guidance - describing the role and constraints without providing concrete code examples, specific register configurations, or copy-paste-ready patterns that Claude could immediately use.
Suggestions
- Add at least 2-3 executable code examples showing common patterns (e.g., GPIO initialization, ISR implementation, FreeRTOS task creation) to make the skill actionable
- Include a concrete validation workflow with specific commands or checks (e.g., 'Verify ISR timing with logic analyzer', 'Check stack usage with FreeRTOS vTaskGetInfo')
- Remove or condense the 'Role Definition' section which duplicates the header and adds no actionable value
- Add a minimal working example in the Output Templates section showing what the expected deliverable actually looks like
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The skill includes some unnecessary framing ('Senior embedded systems engineer with 10+ years experience') and the 'Role Definition' section largely duplicates the header. The constraints and workflow sections are reasonably efficient but could be tighter. |
Actionability | 1/3 | The skill provides no executable code examples, no concrete commands, and no specific implementation patterns. It describes what to do ('Implement drivers', 'Optimize resources') without showing how. The output templates describe what to provide but don't demonstrate it. |
Workflow Clarity | 2/3 | The 5-step core workflow provides a logical sequence but lacks validation checkpoints, feedback loops, or specific verification steps. For embedded systems where errors can be hardware-destructive, missing validation steps are a significant gap. |
Progressive Disclosure | 3/3 | Excellent structure with a clear reference table pointing to topic-specific files with explicit 'Load When' guidance. The main skill serves as an overview with well-signaled one-level-deep references to detailed materials. |
Activation
Suggestions 1
Score
90%Overall Assessment
This is a solid skill description with excellent trigger terms and clear 'when to use' guidance. The main weakness is that the capabilities section could be more specific about concrete actions beyond the general 'developing', 'implementing', and 'optimizing'. The description effectively carves out a distinct niche in embedded systems development.
Suggestions
- Add more specific concrete actions like 'configure peripherals', 'write interrupt handlers', 'implement DMA transfers', 'debug timing issues' to improve specificity
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names the domain (firmware, microcontrollers, RTOS) and mentions some actions (developing, implementing, optimizing), but lacks concrete specific actions like 'configure peripherals', 'write interrupt handlers', or 'debug timing issues'. |
Completeness | 3/3 | Explicitly answers both what (developing firmware, implementing RTOS, optimizing power) and when ('Use when...', 'Invoke for...'). Has clear trigger guidance with specific invocation terms. |
Trigger Term Quality | 3/3 | Excellent coverage of natural terms users would say: 'STM32', 'ESP32', 'FreeRTOS', 'bare-metal', 'power optimization', 'real-time systems', 'firmware', 'microcontrollers', 'RTOS'. These are exactly what embedded developers would mention. |
Distinctiveness Conflict Risk | 3/3 | Very distinct niche - embedded systems/firmware development is clearly separate from general programming skills. Specific platform names (STM32, ESP32, FreeRTOS) and domain terms (bare-metal, real-time) make conflicts unlikely. |