Yocto security ota
Skill prashantdivate/awesome-yocto-ai-agent-skills/yocto-security-ota
Claude Agent Skills for Yocto Project, OpenEmbedded, and BitBake workflows - AI coding assistant skills for recipes, layers, images, BSPs, SDKs, metadata, QA, sstate, and build troubleshooting.
npx -y skills add prashantdivate/awesome-yocto-ai-agent-skills --skill yocto-security-otaAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Yocto security hardening and OTA/update skill for AI coding agents. Use for CVE checks, package/license review, firewall policy, SSH hardening, systemd security, read-only rootfs, dm-verity, secure boot, measured boot, signed artifacts, SBOM, SPDX, vulnerability triage, SWUpdate, RAUC, Mender, OSTree, A/B updates, rollback strategy, and production image hardening.
SKILL.md
1.5 KB, as published. Nobody here has run it
Yocto Security OTA
Workflow
- Identify threat model, update model, physical access assumptions, recovery path, and regulatory constraints.
- Inspect image package set, enabled services, network listeners, users, credentials, SSH policy, firewall, and debug features.
- Check Yocto release security status, CVE tooling, license manifests, and SBOM/SPDX output.
- Select update strategy: full image, package feed, A/B slots, bootloader-managed rollback, OSTree, RAUC, Mender, SWUpdate, or vendor OTA.
- Tie secure boot and artifact signing to key management and manufacturing flows.
- Verify with boot tests, rollback tests, power-cut tests, and update failure tests.
References
- security-ota-playbook.md: hardening, CVE/SBOM, firewall, secure boot, and OTA workflows.
Guardrails
- Do not promise security from package removal alone.
- Do not add firewall rules without documenting network services and default policy.
- Do not recommend OTA updates without rollback and recovery planning.
- Do not put signing keys, credentials, or production secrets in layers or CI logs.