agentsclimarketplace

Yocto security compliance

Skill prashantdivate/awesome-yocto-ai-agent-skills/yocto-security-compliance

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.

Install
npx -y skills add prashantdivate/awesome-yocto-ai-agent-skills --skill yocto-security-compliance

Assembled 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

Official-doc-first Yocto security, CVE, license, and SBOM compliance support for AI coding agents. Use when investigating cve-check results, vulnerable packages, security patch backports, LICENSE and LIC_FILES_CHKSUM issues, license manifests, SPDX or SBOM output, source provenance, reproducibility concerns, package audit findings, or compliance-sensitive Yocto/OpenEmbedded image and recipe changes.

SKILL.md

2.1 KB, as published. Nobody here has run it

Yocto Security Compliance

Core Workflow

  1. Identify Yocto release, image, recipe, package names, source version, and patch state.
  2. Verify current vulnerability/security facts online when the user asks about CVEs, fixes, exploitability, support status, or latest security data.
  3. Distinguish recipe name, source package name, runtime package name, binary package name, and CVE product/vendor names.
  4. Inspect upstream source, local patches, license files, package manifests, SPDX/SBOM output, and cve-check output before changing metadata.
  5. Prefer recipe upgrades or patch backports over blanket ignores.
  6. Document compliance decisions in the layer or release notes where the project expects them.

Use yocto_security_doc_router.py with a topic name for official documentation links.

References

Guardrails

  • Do not suppress CVE, license, or QA findings without documenting the exact reason.
  • Do not change LICENSE, LIC_FILES_CHKSUM, or CVE status fields without inspecting upstream source, patches, and package output.
  • Do not treat build-time package names, runtime package names, source recipe names, and CVE product names as interchangeable.
  • Do not put signing keys, embargoed details, or private vulnerability data into public layers or logs.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.