snap-orchestrator

Coordinates analyzer, packager, and validator sub-agents to build and validate snaps end-to-end.

7|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/rascheel/scheel-skills --skill snap-orchestrator-rascheel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: snap-orchestrator
Source: https://github.com/rascheel/scheel-skills/tree/main/snap-orchestrator
Command: npx skills add https://github.com/rascheel/scheel-skills --skill snap-orchestrator-rascheel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Packaging an application as a snap requires chaining analysis, manifest generation, building, and validation with iterative patching, which is tedious and error-prone to coordinate manually. ## Core Features & Use Cases - Full Pipeline Orchestration: Delegates analysis, packaging, and validation to focused sub-agents that communicate through files on disk, minimizing context usage. - Iterative Patch Loop: Loops validate → patch → rebuild with separate caps for denial fixes (5), devmode build fixes (3), and OCI reproducibility fixes (3). - Dual Input Support: Selects snap-analyzer for source-code projects or snap-oci-analyzer for Docker/OCI container input, driving the same pipeline for both. - Use Case: Point it at a project root or a Docker image reference and receive a built, validated .snap plus a consolidated report of interfaces, denials, and reproducibility status. ## Quick Start Run the full snap packaging pipeline on this project and build and validate a snap from the source code in the current directory.

Frequently Asked Questions about snap-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate the full snap packaging pipeline?

Run the snap-orchestrator from your project root; it delegates analysis, packaging, and validation to sub-agents and loops patch-and-rebuild until the snap validates clean or iteration caps are reached. It requires LXD and snapcraft installed.

Can I convert a Docker image to a snap package?

Yes. When the input is a Docker Hub URL, image reference, docker save tarball, or pre-extracted config.json plus rootfs, the orchestrator selects snap-oci-analyzer and drives the same package, validate, and patch loop, including a reproducibility check.

What tools are required to run the snap packaging pipeline?

LXD and snapcraft must be installed for validation and packaging. The OCI path additionally needs skopeo, umoci, and jq, which the analyzer can attempt to install automatically.

What happens when snap validation finds AppArmor denials?

The orchestrator sends the validation results to snap-packager in patch mode, which adds the suggested interfaces or layouts to snapcraft.yaml and rebuilds. This loop repeats up to 5 times before reporting unresolved denials.

Does the pipeline support classic confinement snaps?

Yes, but validation is skipped for classic snaps since it does not apply. The orchestrator proceeds directly to the final report, noting the Snap Store approval requirement and Ubuntu Core incompatibility.