pu

Automate creation, command execution, artifact copying, and teardown of ephemeral Incus containers.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/srid/smriti --skill pu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pu
Source: https://github.com/srid/smriti/tree/main/.claude/skills/pu
Command: npx skills add https://github.com/srid/smriti --skill pu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Incus, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation and management of Incus containers, offering a clean, reproducible environment for tasks like CI, builds, and evidence capture without the risk of local system interference.

Core Features & Use Cases

  • Provisioning Containers: Spin up a fresh Linux container for a range of off-machine tasks.
  • Running Commands: Execute commands within the container, ensuring the environment is pristine and reproducible.
  • Copying Artifacts: Safely copy artifacts back to the local machine for analysis or further processing.
  • Ephemeral Containers: Create short-lived containers for quick experiments or long-term setups as needed.
  • Use Case: Ideal for running builds, conducting CI tests, or capturing evidence on a fresh remote environment.

Quick Start

Use the pu skill to create a container named 'ci-env' and run 'nix run github:owner/app'.

Frequently Asked Questions about pu

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

FAQPage Schema
How do I automate the creation of ephemeral Incus containers for CI builds?

You can automate ephemeral Incus containers by using scripts to spin up a fresh Linux environment, execute build commands, copy artifacts, and automatically tear down the container to ensure clean CI execution.

What is the best way to run builds in a clean Linux environment without interfering with my local machine?

Running builds in a clean Linux environment without local interference is achieved by provisioning short-lived Incus containers that isolate your build environment and safely copy the resulting artifacts back to your host machine.

Do I need Incus installed locally to spin up short-lived containers for off-machine tasks?

Yes, you need Incus and its associated tools installed locally to manage the container lifecycle, which includes provisioning, executing commands, and destroying the short-lived containers used for off-machine tasks.

How do I execute commands and capture evidence in a reproducible environment?

To execute commands and capture evidence in a reproducible environment, you spin up an ephemeral Incus container that provides a pristine Linux state, run your required operations, and extract the output artifacts before teardown.

Can I copy build artifacts from an Incus container back to my local machine?

Yes, you can copy build artifacts from an Incus container back to your local machine, allowing you to safely analyze or process the results generated within the ephemeral build environment before it is destroyed.