agentsclimarketplace
Sign in

Yocto doc router

Skill Higangssh/yocto-agent-skills/skills/yocto-doc-router

Release-aware official documentation routing for Yocto Project, OpenEmbedded, and BitBake questions. Use when the user asks where to find current Yocto docs, when a Yocto answer may depend on release/branch, or before giving precise guidance about variables, classes, tasks, QA errors, migration, BSP, kernel, SDK, security, SBOM, CVE, or build setup.From its SKILL.md

Install
npx -y skills add Higangssh/yocto-agent-skills --skill yocto-doc-router

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 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.

SKILL.md

2.5 KB, as published. Nobody here has run it

Yocto Doc Router

Use this skill to route Yocto and BitBake questions to the correct official documentation before answering. Yocto is release-sensitive; do not rely on generic memory when syntax, variables, classes, host support, or QA behavior may differ by branch.

Workflow

  1. Identify the release or branch: inspect LAYERSERIES_COMPAT_*, conf/layer.conf, Poky/OE-Core branch names, build output, or vendor layer documentation.
  2. If the release is unknown, state the assumption and prefer current official docs.
  3. Read references/official-doc-map.md to route by problem type.
  4. For release changes, read references/migration.md.
  5. Return the smallest useful doc path, the reason it matters, and the evidence needed from the user's tree.

Routing Rules

  • New build setup: Quick Build, Development Tasks Manual, source directory structure, supported host distro.
  • Syntax and overrides: BitBake User Manual > Syntax and Operators, Conditional Syntax, Functions, Tasks.
  • Variables: Reference Manual Variables Glossary plus references/variables-core.md.
  • Classes: Reference Manual Classes plus references/classes-core.md.
  • QA errors: Reference Manual QA messages plus references/qa-errors.md.
  • Layers: Development Tasks Manual > Layers, BitBake concepts for layers and appends.
  • Recipes: Development Tasks Manual > Writing a New Recipe, Reference Manual Tasks and Classes.
  • BSP/kernel: BSP Guide, Kernel Development Manual, relevant class and variable entries.
  • Security/SBOM/CVE/license: Security Manual, Security Reference, Reference Manual classes and variables.
  • Image/rootfs: Development Tasks Manual image customization, package management, and Reference Manual image/rootfs tasks.

Output

Answer with:

  1. assumed or detected release
  2. official manual section to check
  3. local file/log/command that confirms the issue
  4. next focused skill to use, if any: bitbake-debug, yocto-recipe-review, yocto-layer-review, yocto-image-rootfs, yocto-bsp-kernel, or yocto-security-sbom

What ships with it: 5 files

28.7 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most docs writing skills give

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionsin 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • Identify the release or branch
  • State assumptions if the release is unknown
  • Consult the official documentation map
  • Read migration documentation for release changes
  • Provide the smallest useful documentation path
  • Explain why the documentation matters

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 626,194. 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.