# Qemu Image Packaging

> Use for packaging QEMU boot media from kernels, DTBs, firmware, bootloaders, root filesystems, modules, and raw or qcow2 images, while recording layout, offsets, write commands, hashes, and mutation policy.

- **Type:** Skill
- **Install:** `agentstack add skill-processmission-oh-my-qemu-qemu-image-packaging`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [processmission](https://agentstack.voostack.com/s/processmission)
- **Installs:** 0
- **Category:** [Content & Media](https://agentstack.voostack.com/c/content-and-media)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [processmission](https://github.com/processmission)
- **Source:** https://github.com/processmission/oh-my-qemu/tree/main/.agents/skills/qemu-image-packaging
- **Website:** https://processmission.github.io/oh-my-qemu/

## Install

```sh
agentstack add skill-processmission-oh-my-qemu-qemu-image-packaging
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# QEMU Image Packaging

Use this workflow to create or update QEMU boot media: SD, eMMC, raw disk, qcow2, pflash, NOR, NAND, firmware containers, or rootfs images.

## Primitive Composition

1. Use `qemu-flow-plan`.
2. Use `qemu-source-provenance` for every input artifact.
3. Use `qemu-image-layout` to define the target layout before writing.
4. Package on a scratch copy unless the user explicitly requests otherwise.
5. Verify the resulting image and update `image-layout.md`.

## Packaging Flow

Record:

- base image or blank image creation command;
- virtual size, actual size, and format;
- partition or fixed-region map;
- filesystem creation or file copy commands;
- raw write operations, including offset or seek and block size;
- final image hash and any per-partition or per-file checks;
- whether the image is intended to be reused, treated as disposable, or refreshed before each run.

## Tool Rules

- Use `qemu-img` for QEMU image format conversion or inspection.
- Use partition/filesystem tools appropriate to the local image format.
- Prefer explicit offsets over implicit tool behavior for firmware regions.
- Keep large generated images out of source control.
- Store packaging logs and command transcripts under `build/agent//`.

## Handoff

After packaging, provide a copy-pasteable path and the image contract to `qemu-boot-run` or a boot workflow. If boot fails, re-check the image layout before changing QEMU source.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [processmission](https://github.com/processmission)
- **Source:** [processmission/oh-my-qemu](https://github.com/processmission/oh-my-qemu)
- **License:** MIT
- **Homepage:** https://processmission.github.io/oh-my-qemu/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-processmission-oh-my-qemu-qemu-image-packaging
- Seller: https://agentstack.voostack.com/s/processmission
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.