Loading the registry…
This skill turns a rough Attaky firmware idea from a non-technical user into a structured concept doc covering behavior, hardware combination, and feature breakdown — ready for firmware-spec to pick up. Use it when a user describes a firmware they want to build for an Attaky device, even casually: "I want to make my Attaky do X", "can my Attaky buzz when ...", "I have an idea for an Attaky firmware", "design something for my Attaky", "build me a firmware that ...", "here's an idea for the LoRa+GPS / Radio / Keyboard module", "what if the Attaky could ...". The user describes function and behavior; the skill silently handles all technical decisions (modules, chip details, pins, memory, code structure) and drafts every section of the concept doc itself. Asks at most a couple of short FUNCTIONAL clarifying questions, one at a time. Iterates until the user approves, confirms a save location (default: current working directory), writes the concept doc, and hands off to firmware-spec.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'attaky-module/attaky-firmware-builder (firmware-brainstorm)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'attaky-module/attaky-firmware-builder (firmware-brainstorm)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
3 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
45 findings · 9.1s
v0.3.74
2 findings · 1.3s
v0.1.0
1 finding · 3.2s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 3.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
No report in this scan: nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 16, 2026 | Flagged61 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-install-instruction: completecapslock ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 48 findings above stand exactly as their scanners reported them, at full severity.