skills.rest
8007342
8007342COMMUNITY
Explore all skills by this author →
GitHub

smoke-curl-install-and-test-e2e

Validates published Tillandsias releases via clean-room curl-install, destructive reset, and fresh init.

5|Updated Mar 21, 2026
Search Tags:#end-to-end testing#release validation#smoke test#podman#ci cd#clean room#curl install
One-click install
npx skills add https://github.com/8007342/tillandsias --skill smoke-curl-install-and-test-e2e-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-curl-install-and-test-e2e
Source: https://github.com/8007342/tillandsias/tree/main/skills/smoke-curl-install-and-test-e2e
Command: npx skills add https://github.com/8007342/tillandsias --skill smoke-curl-install-and-test-e2e-8007342

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A release can pass local CI yet still fail for a real operator installing the published artifact from scratch. This Skill closes that gap by smoke-testing the actual downloadable release on a wiped host substrate, catching install, reset, and init failures that only appear outside the build environment. ## Core Features & Use Cases - Clean-room release validation: Curl-installs the exact pinned release (daily or stable channel) from GitHub, asserts the installed version matches the tag, and stops on any mismatch. - Destructive substrate reset: Runs podman system reset --force on Linux, removes VM state on macOS, and unregisters the WSL2 distro plus clears vault credentials on Windows, with assertions proving the store is empty. - Pristine init and forge lane: Runs tillandsias --debug --init from scratch and launches the meta-orchestration forge lane, filing every observed issue as a plan/issues work packet. - Use Case: After promoting a new stable release, run this Skill once per host (Linux, macOS, Windows) to prove the promoted artifact installs, resets, and re-provisions correctly before operators rely on it. ## Quick Start Run the smoke-curl-install-and-test-e2e skill to curl-install the latest daily release and smoke test it end to end on this host.

Frequently Asked Questions about smoke-curl-install-and-test-e2e

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

FAQPage Schema
How do I smoke test a published release end to end?▼

Curl-install the pinned release from GitHub, assert the installed version matches the tag, wipe the container or VM substrate, then run a fresh init from the pristine state. This Skill automates that full sequence and files any failure as a work packet.

What is the difference between the daily and stable smoke channels?▼

The daily channel tests the newest release including prereleases and is the default for routine smoke runs. The stable channel tests the newest non-prerelease and is run once right after a promotion to prove the promoted artifact installs.

Does the smoke test work on Windows and macOS?▼

Yes. Windows uses install-windows.ps1 with a WSL2 distro unregister and Credential Manager vault cleanup, while macOS uses install-macos.sh with removal of the Virtualization.framework state and cache directories.

Is the podman system reset step destructive?▼

Yes. On Linux it irreversibly deletes all containers, images, volumes, and secrets for the user, including vault data and project mirrors. It is intended for dedicated smoke hosts; operator workstations require explicit authorization first.

Why must the smoke run under bash instead of zsh?▼

The runbook asserts exit codes via PIPESTATUS, which is a bash array that expands empty under zsh, causing failed steps to silently pass. Every bash block begins with a guard that fails loudly if not running under bash.

What happens to issues found during the smoke test?▼

Every issue observed during install, reset, init, or the forge lane is filed as a plan/issues work packet. These packets are later picked up by the advance-work-from-plan worker loop rather than being fixed inline.

Related Skills

Explore More Software Engineering Skills→
OneIdentityOneIdentity
24

build-and-release

Reproduce safeguard-ps Azure Pipeline build-and-release behavior locally.

Official
Intermediate
kangnam7654kangnam7654
1

release

Coordinate end-to-end Paperclip releases across verification, publishing, and announcements.

Community
Advanced
ThalesGroupThalesGroup
19

agilab-testing

Execute targeted AGILAB tests across unit, smoke, and regression suites.

Official
Advanced
sunzcdevsunzcdev

release

Automate deterministic software releases with changelog generation, version bumps, and Homebrew checksum updates.

Community
Advanced