Menú
Jumpstarts an agent's awareness of the pre-configured Forge environment using a tiny amount of tokens.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Discover, claim, implement, checkpoint, and complete units of work from the shared plan ledger based on host capabilities and lease rules, complementary to multihost-orchestration.
Build, install, and DESTRUCTIVELY smoke-test the current Tillandsias checkout on the host you are running on — Linux (Podman), macOS (Virtualization.framework VM), or Windows (WSL2). Detects the OS, builds + installs the locally built tray, irreversibly destroys the host's runtime substrate (Podman store / macOS VM dir / WSL2 distro), re-provisions from a pristine state, and — on Linux only — launches the forge with `/meta-orchestration`. Every issue observed is filed as a `plan/issues/` work packet.
Coordinate Tillandsias Linux, Windows, and macOS implementation agents by auditing shared plan/methodology ledgers, analyzing sibling branch git history, reconciling stale work queues, mediating concurrent conflicts or thrashing, tracking convergence velocity metrics, enforcing finite-time convergence guarantees, and pushing coordination updates. Designed to run hourly to ensure continuous cooperation and unblocking.
Host-aware Tillandsias recurring runtime loop: sync remote state, drain claimable plan work, run eligible e2e smoke gates, coordinate integrations on mutable Linux, release when warranted, update plan, commit, and push before exit.
Clean-room end-to-end smoke test of a PUBLISHED release. Curl-installs the latest release binary from GitHub, does a full `podman system reset --force`, runs `tillandsias --debug --init` from a pristine state, and (if init is clean) launches `tillandsias . --opencode --prompt "Use the /meta-orchestration skill"`. Every issue observed — by this skill's agent during install/reset/init, or by the agents running inside the forge under meta-orchestration — is filed as a plan/issues work packet for later pickup by /advance-work-from-plan.
Refresh linux-next, open/update the PR to main, merge once green, bump VERSION, tag, and trigger the workflow_dispatch release. Runs on a daily cadence so the latest linux-next work reaches a downloadable Linux release operators can smoke-test on a Fedora Silverblue host.
| name | forge-quick-intro |
| description | Jumpstarts an agent's awareness of the pre-configured Forge environment using a tiny amount of tokens. |
Purpose: Immediately bootstrap a new agent's awareness of the Forge environment. Instead of wasting tokens exploring the environment to see what compilers, tools, or browsers are installed, agents should read this brief intro.
The Forge Environment is fully loaded. You DO NOT need to install or search for these tools. They are ready to use:
gh), curl, wget, jq, ripgrep, fd-find, bat, yq, just, etc.dnf (microdnf) is available for additional packages if absolutely needed, though most dev tools are already present.Directive:
Assume all standard modern development tools are in your PATH. When instructed to "build an app" or "compile a project", proceed immediately to coding and executing rather than searching the file system for the compiler binary.