AC arm-cortex-expert
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and peripheral drivers.
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD).
As a process C 62/100 · Has gaps — weak spots: result and completion, failures and branches, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 4 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 91 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3125 tokens
- 100Progress reporting. Reports progress
- low 15 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -213 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 334: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 91 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.