Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Arch Distro Design — ISO & Appliance Harness

    1

    Design, build, and validate persistent Arch Linux appliances and ISOs with local repos and automated QEMU testing.

    $25

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Arch Distro Design — ISO & Appliance Harness

    Arch Distro Design — ISO & Appliance Harness

    Example session with this skill installed

    I need a persistent Arch Linux .img appliance for a minimalist monitoring station. It needs a desktop, must work offline, and should be tested in QEMU before I write it to a 16GB USB.

    • Read your context and instructions
    • Compiled the arch distro design

    I have initiated the Arch Distro Design workflow. We will build a persistent .img appliance with a frozen repository for offline capability and an L1 (Openbox) desktop layer.

    Appliance Specification & Build Plan

    ComponentSpecification
    ArtifactPersistent GPT .img Appliance
    PartitioningEFI (512MB) / SYS (ext4) / DATA (ext4, Label: DATA)
    Desktop LayerL1: Openbox + tint2 + falkon (~400 MB)
    Repo PolicyFrozen offline local repo (signed)
    HardwareTarget 16GB USB (UEFI)
    Networksystemd-networkd inactive by default

    Configuration Manifest

    
    # arch-distro-design brief signature
    OBJECTIVE=persistent_monitoring
    OUTPUT_FORMAT=img
    HARDWARE=usb_uefi_16gb
    NETWORK=offline
    LAYERS=L1
    IMMUTABILITY=rw_update_rule
    UPDATE_POLICY=local_signed_repo
    
    # Partitioning commands generated
    parted -s "$DESTINO" mklabel gpt
    mkfs.vfat -F32 "${DESTINO}1"
    mkfs.ext4 "${DESTINO}2"
    mkfs.ext4 -L DATA "${DESTINO}3"
    

    Validation Strategy

    1. Build: Generate .img using pacstrap and local versions.txt pinning.

    Test: Launch qemu-system-x86_64 with -serial mon:stdio -nographic to verify the DATA partition auto-mounts.
    3. Deploy: Write to /dev/sdb (verified via lsblk) using dd conv=fsync followed by triple sync.

    Next steps

    • Confirm the list of specific monitoring packages for repo-packages.txt.
    • Approve the L1 desktop layer configuration (Openbox/tint2).
    • Run the arch-qemu-validation suite once the image build completes.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Developing custom Arch Linux distributions and persistent appliances often leads to silent failures, data loss, and hardware hangs. This specialized skill suite provides a rigorous, 9-part orchestration framework to design, build, and validate Arch-based systems from initial brief to physical media writing.

    What it does

    • Architectural Routing guides the selection between live ISOs and persistent .img appliances based on the project objective.
    • Persistent Appliance Building creates GPT-partitioned images with independent EFI, SYS, and DATA partitions for maximum portability.
    • Offline Repository Management generates signed, frozen pacman repositories for reliable updates in internet-restricted environments.
    • Payload Materialization uses a bash-only manifest system to deploy self-hosted apps without vendoring source code.
    • Hardware Safety Gate enforces strict disk identification and sync protocols to prevent filesystem corruption and "error -71" hardware hangs.
    • Automated Validation executes a 15-point QEMU test harness to verify boot, serial console, and SSH before deployment.

    How it works

    1. Design Brief: Complete the 7 mandatory categories (Objective, Format, Hardware, Network, Payloads, Immutability, Update Policy).
    2. Profile Configuration: Define the archiso profile or appliance partition structure using standardized desktop layers (L0 to L6).
    3. Artifact Generation: Build the ISO or .img while pinning package versions in a local signed repository.
    4. QEMU Verification: Pass the automated test harness to confirm network policies and graceful shutdowns.
    5. Hardware Writing: Use the hardware handler to safely flash the artifact to physical media with post-write validation.

    Frameworks & tools

    Built for Arch Linux using archiso 91-1, pacstrap, systemd-boot, qemu-system-x86_64, and pure Bash scripts.

    Why this beats prompting it yourself

    Generic AI prompts often miss critical archiso internal function changes or produce unbootable images due to empty bootstrap packages. This skill enforces a "pitfalls" memory that catches specific technical failures like realpath errors and UEFI/BIOS compatibility issues that occur during the build process.

    Use cases

    • Building a persistent kiosk appliance with a portable DATA partition.
    • Creating an air-gapped recovery ISO with a pre-synced package repository.
    • Developing custom thin-client distros ranging from console-only to GNOME environments.
    • Validating OS images in headless CI environments before physical USB deployment.

    Known limitations

    Requires an Arch Linux host with qemu-desktop and edk2-ovmf for validation. Appliances are restricted to x86_64 architecture and require a minimum 8 GB disk.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    Requires Arch Linux host. Validation needs qemu-desktop and edk2-ovmf. Supports x86_64 only. Physical disks must be >= 8GB. Bash-only manifest parsing (no jq/yq). Not a desktop distro generator. USB writes require a Linux host and will refuse the disk holding the running root. No GUI; everything is CLI + Markdown.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Software
    PythonGitarchisoqemuarch-linuxBash

    Permissions

    Terminal / Shell
    Network Access
    Write Files
    Read Files

    Allowed Hosts

    archlinux.org

    File Scopes

    skills/**
    /tmp/arch-*/**
    ~/arch-build/**

    Writes only to the target device you name explicitly and refuses to touch the host root disk. No curl-pipe-to-shell, no unguarded rm -rf.

    Listed6 days ago
    Updated5 days ago

    What's inside

    Frequently Asked Questions

    No. `archiso` builds the ISO. This harness decides *what to build, why, and how to validate it before touching hardware*. It is the governance layer, not the build tool.

    Yes. Each skill is independently usable. But the design assumes you start with `arch-distro-design` (the Brief router), because skipping it is the #1 documented cause of "I built the wrong thing."

    If your agent reads `SKILL.md` files, yes. That includes Claude Code, Cursor, Copilot, Gemini CLI, Windsurf, Cline, Aider, and Continue.

    This pack is Arch-specific. The pitfalls catalog is Arch-specific. For NixOS, use `nixos-generators`; for Debian, use `live-build`.

    Yes, via the creator profile on Agensi and through public GitHub Issues. Response within 48h for questions about the skills; no SLA for custom builds.

    Digital goods are generally non-refundable. If something is broken, contact me and I'll fix it. See Agensi's standard policy for the formal terms.

    New in DevOps & Cloud