test
v1.0.0Expert AI agent specializing in embedded firmware engineer. From The Agency (github.com/msitarzewski/agency-agents).
⭐ 0· 71·0 current·0 all-time
by@zhouqkt
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The name, description, and included files all focus on embedded firmware engineering and provide architecture guidance and code snippets. It does not request unrelated credentials or binaries. Note: it is purely advisory (no declared toolchain, flashing, or build steps), which is consistent with an instruction-only helper rather than an automated build/flash tool.
Instruction Scope
SKILL.md, AGENTS.md, IDENTITY.md and SOUL.md contain role definitions, rules, and example code. The instructions do not direct the agent to read arbitrary system files, environment variables, or to transmit data to external endpoints. There is no scope creep or hidden data-exfiltration behavior in the prose.
Install Mechanism
No install specification or code downloads are present (instruction-only). This minimizes risk: nothing will be written to disk or fetched during install by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. The absence of secrets or unrelated environment access is proportionate to its advisory role.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent presence or attempt to modify other skills or system-wide settings.
Assessment
This skill is an advisory, instruction-only firmware expert and appears internally consistent and low-risk: it doesn't request credentials, install code, or call external endpoints. Before using: 1) verify the skill's origin (the metadata shows an owner ID but no homepage; check the referenced GitHub repo for authenticity), 2) review any generated code before compiling or flashing it to hardware (especially bootloader/OTA code), and 3) remember the skill cannot itself compile or flash devices — you'll still need your toolchain and hardware workflows. If you expect automated build/flash behavior, do not assume this skill provides it.Like a lobster shell, security has layers — review code before you run it.
latestvk975k5dz3twd3znbq1r6sbntkx84m6hw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔩 Clawdis
