rip-cage-tool-manifest-authorlisted

Use when a user wants to add a new tool to their rip-cage Docker image via the host-only manifest mechanism (ADR-005 D11). Guides a HOST-SIDE agent to read a named tool's source and release situation, determine whether a prebuilt Linux binary exists or a from-source build is needed, and draft a manifest entry (plus a build script for the from-source path) as HUMAN-REVIEWABLE host files under ~/.config/rip-cage/. The human approves the drafted files before running rc build; the fail-closed validator enforces the contract. Does NOT perform any in-cage write or runtime injection. cm is the worked example (no prebuilt linux-arm64 release -> from-source path).
jsnyde0/rip-cage · ★ 1 · API & Backend · score 74

Install: claude install-skill jsnyde0/rip-cage

# rip-cage Tool Manifest Authoring Use this skill when a user asks to add a tool to their rip-cage image. You are running HOST-SIDE under the user's supervision. You draft REVIEWABLE FILES; the human approves before `rc build`. You do NOT write into a running cage. --- ## Host-only invariant (FIRM — ADR-005 D7, ADR-024) The rip-cage manifest lives at `~/.config/rip-cage/tools.yaml` on the HOST. The in-cage agent cannot reach this file: `rc` is not copied into the container image, and `RC_MANIFEST_GLOBAL` / `XDG_CONFIG_HOME` are not forwarded into the cage. This is not a path-based lock — it is enforced by `rc` being a host-only process. **You are the host-side agent. Your job:** 1. Draft a manifest entry (and build script if needed) as HOST files for human review. 2. Tell the human what to review and how to apply it. 3. Never write into a running cage. Never instruct the in-cage agent to modify the manifest. Never produce a runtime injection. --- ## Step 0 — Orient before drafting Before proposing any manifest entry, read the tool's actual source / release page: - Check GitHub releases for a prebuilt linux-arm64 asset. - Check GitHub releases for a prebuilt linux-amd64 asset. - Check the Dockerfile / package manager (apt, apt-get) install path if one exists. - Identify the version you want to pin (`version_pin`). This is open-ended per-tool judgment. The goal: determine which of the two manifest paths fits the tool. --- ## Two paths: prebuilt vs from-source ###