yocto-build-debug

yocto-build-debug is a skill for Codex from prashantdivate/awesome-yocto-ai-agent-skills. It costs 119 tokens per session (572 once invoked), scanned A, original, MIT.

A troubleshooting skill for Yocto Project builds. Yocto is a system for assembling custom Linux operating systems for embedded devices, and BitBake is its build tool.

In plain words
What is it for?
Use it to investigate parse, download, patch, compile, packaging, quality-check, dependency, cache, disk-space, and host-environment failures.
Why use it?
It helps narrow a failed build to the relevant stage instead of repeating a full image build or changing configuration blindly.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: $skill-name invocation.

Good fit Use it to investigate parse, download, patch, compile, packaging, quality-check, dependency, cache, disk-space, and host-environment failures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-build-debug
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add prashantdivate/awesome-yocto-ai-agent-skills --skill yocto-build-debug
Clone the repo
git clone --depth 1 https://github.com/prashantdivate/awesome-yocto-ai-agent-skills

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for yocto-build-debug

README.md
[![agentmods](https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-build-debug/github.svg)](https://agentmods.dev/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-build-debug)
Your own site
<a href="https://agentmods.dev/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-build-debug"><img src="https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-build-debug/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for yocto-build-debug

Your own site · 80×15
<a href="https://agentmods.dev/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-build-debug"><img src="https://agentmods.dev/badge/skills/prashantdivate/awesome-yocto-ai-agent-skills/yocto-build-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 119 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 572 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00119 $0.00572
Opus 5 $0.00060 $0.00286
Sonnet 5 $0.00024 $0.00114
Haiku 4.5 $0.00012 $0.00057

Measured 12d ago against content hash c19cd9414209, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

yocto-build-debug scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/yocto_log_triage.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

yocto-build-debug/SKILL.md · 42 lines

What it actually says

Yocto Build Debug

Workflow

  1. Identify the build entrypoint: Makefile, kas, repo, oe-init-build-env, container script, CI job, or vendor wrapper.
  2. Confirm MACHINE, DISTRO, BBLAYERS, TMPDIR, DL_DIR, SSTATE_DIR, and target image/recipe.
  3. Reproduce the smallest failing command. Prefer parse, fetch, or one task over a full image rebuild.
  4. Inspect logs before editing metadata. Use yocto_log_triage.py with the build directory for a quick scan.
  5. Classify the failure: parse, layer, provider, fetch, patch, configure, compile, install, package, QA, image, test, or signature.
  6. Route metadata questions to $bitbake-metadata; route board boot/deploy issues to $yocto-deploy-flash or $yocto-bsp-bringup.

Commands

bitbake-layers show-layers
bitbake-layers show-recipes RECIPE
bitbake-layers show-appends
bitbake -e RECIPE
bitbake -c listtasks RECIPE
bitbake -c TASK -f RECIPE
bitbake -g RECIPE
bitbake-diffsigs SIGDATA_A SIGDATA_B
oe-pkgdata-util list-pkgs

References

Guardrails

  • Do not recommend deleting tmp/ or sstate-cache/ until narrower evidence has been checked.
  • Do not silence QA with INSANE_SKIP until the package/file/license root cause is known.
  • Do not assume deploy output is under tmp/; many builds use tmp-glibc, multiconfig paths, or custom TMPDIR.
  • Do not change provider/version policy globally without checking affected recipes and images.
Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 42 lines · 119 tokens per session scan A c19cd9414209

Subscribe to this mod's changes

yocto-build-debug is a skill published in the GitHub repository prashantdivate/awesome-yocto-ai-agent-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 119 tokens to every session and 572 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

debug-task

Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…

moonrepo/moon · 231 tokens

jlink

A tool for using a SEGGER J-Link probe to connect a computer to an embedded chip for programming and debugging.

zhinkgit/embeddedskills · 176 tokens

openocd

A toolkit for programming and debugging microcontrollers through hardware probes such as ST-Link or CMSIS-DAP. OpenOCD can act as a GDB Server, allowing a debugger to inspect source code, registers, memory, breakpoints, and program execution.

zhinkgit/embeddedskills · 247 tokens

serial

A tool for communicating with devices over serial ports, such as USB-to-UART connections. It can find ports, watch incoming data, send messages, save logs, and display raw bytes in hexadecimal form.

zhinkgit/embeddedskills · 137 tokens

can

A debugging tool for CAN and CAN-FD, communication systems used by vehicles and embedded devices. It can find interfaces, monitor and send messages, record logs, decode DBC database files, and report bus statistics.

zhinkgit/embeddedskills · 168 tokens

eide

A build tool for EIDE projects, an embedded-development extension for Visual Studio Code. It finds EIDE project settings and builds firmware using ARM CC or GCC.

zhinkgit/embeddedskills · 151 tokens