Production Install

Use when a dev tool meets the owner's real data. Pin, isolate.

44 starsOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add SamueleBassoli/hermes-fleet-apps --skill production-install
Manual install
git clone --depth 1 https://github.com/SamueleBassoli/hermes-fleet-apps.git /tmp/hermes-fleet-apps
mkdir -p ~/.claude/skills
cp -r /tmp/hermes-fleet-apps/roles/coder/skills/production-install ~/.claude/skills/production-install

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Production install beside the dev checkout

Dev work and the owner's real data must never share a database, a venv, or a code
copy. Sharing one means a test run pollutes their data, and the next edit in the
repo silently changes the tool they rely on.

```
  launcher   ~/.local/bin/<tool>-real.bat   (already on PATH; one line)
     |- program   %LOCALAPPDATA%\<tool>-app\   own venv, pinned to a commit
     |- data      <path the owner names>\data\  via the tool's data-dir flag
  dev (untouched)  repo .venv + default data dir
```

The example is Windows (`.bat`, `Scripts/`). On Linux and macOS the launcher is a
two-line shell script in `~/.local/bin`, the venv has `bin/` instead of `Scripts/`,
and the program dir sits under `~/.local/share/<tool>-app/`.

## Procedure

1. **Ask the owner for the data location. Never guess a drive.** Then check free
   space (`df -h <drive>`) and say so if the disk is nearly full.
2. **Read how the data dir is chosen.** If the flag is GLOBAL (before the
   subcommand), the launcher is `tool --data-dir X %*`. If there is no env-var
   override, say so: the launcher is then the ONLY separation, and plain
   `tool` still writes to the dev data.
3. **Pin dependencies to what the tests passed on.** Run
   `uv pip freeze --python .venv/Scripts/python.exe`, drop the package itself
   and the test-only deps, and save the rest as a constraints file in scratch.
4. **Build the exact commit, not the working tree:**
Read the full skill on GitHub

Details

Skill name
production-install
Path
roles/coder/skills/production-install/SKILL.md
License
MIT
Repo updated
31 October 2026

FAQ

What does the Production Install skill do?

Use when a dev tool meets the owner's real data. Pin, isolate.

How do I install the Production Install skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add SamueleBassoli/hermes-fleet-apps --skill production-install. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Production Install popular?

It lives in SamueleBassoli/hermes-fleet-apps, which has 44 GitHub stars and 0 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.