agentsclimarketplace
Sign in

Install claude dev

Skill woditschka/agentic-coding-reference/.claude/skills/install-claude-dev

Install or update the claude-dev tooling — the claude-dev command, the container Dockerfile, the default config, the egress allow-list, the IDE-oracle preflight, and the ~/.claude.json scrubber — from this repo's tools/claude-dev/ into ~/.local/bin and ~/.config/claude-dev. Thin front-end for tools/claude-dev/install.sh: run its check mode to show drift, apply only on the user's approval. Use when the user asks to install claude-dev, set up the development container, or update the launcher or image definition. Examples: "install claude-dev", "update the container tooling", "set up the claude container".From its SKILL.md

Install
npx -y skills add woditschka/agentic-coding-reference --skill install-claude-dev

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.1 KB, as published. Nobody here has run it

install-claude-dev

The mechanics live in tools/claude-dev/install.sh (source of truth: this repo's tools/claude-dev/). The skill adds the approval gate: never apply without the user's explicit OK.

Process

  1. Detect drift. Run from the repo root (the script reads sources relative to itself; if not in this repo, stop and say so):

    tools/claude-dev/install.sh check

    It prints one status per target — identical, drift (N lines), or missing — for the command (~/.local/bin/claude-dev), the managed files (Dockerfile, claude_dev_config.py, claude_dev_scrub.py, ide_preflight.py), and the one policy file the user owns (claude-dev.toml). The installer carries no migration path and reports no retired files: it installs the current tool and nothing else.

  2. Show the table and get approval. Present the drift; for drifted rows, offer the unified diff on request. Do NOT edit without explicit approval ("apply", "go ahead", "install"). If everything is identical, report that and stop.

  3. Apply:

    tools/claude-dev/install.sh apply

    It installs the command and the managed files, keeps an existing claude-dev.toml untouched, and smoke-tests claude-dev help. A smoke-test failure exits non-zero: do not declare success; report the exact output.

  4. Handle policy drift. apply never overwrites claude-dev.toml, so a drifted config stays drifted — most often the repo copy gained a new default domain. Show the diff and offer to merge the additions into the installed file; edit it only with the user's approval. install.sh reset-config replaces it with the shipped version and keeps the old one as .bak — offer it only when the user wants to discard their policy, and never as the fix for a small merge.

    A config carrying a table or key this version does not read is refused by name at launch, not ignored. check reports that case as REFUSED by this version — raise it BEFORE applying, because apply overwrites the managed files first and its smoke test would then fail on the stale policy. The fix is to delete the named line, never to widen the reader.

  5. Report. What changed, the smoke-test result, and the next steps that are NOT this skill's job: claude-dev build for the image build (this build adds squid, socat and bubblewrap, so an existing image must be rebuilt — a session started on a stale image refuses to launch rather than running unproxied), claude-dev update after a Dockerfile change, and one /login inside on first run.

What this skill does NOT do

  • Build or update the image — that is claude-dev build / claude-dev update; builds take minutes and the user runs them when ready.
  • Run the container — the user runs claude-dev from a project directory.
  • Log in — credentials are container-private; /login happens inside.
  • Edit the allow-list — [egress] allow in claude-dev.toml is the user's egress policy. Suggest entries; never add one unasked, and never paste in a list of names a session was observed requesting.
  • Uninstall — the user deletes ~/.local/bin/claude-dev and ~/.config/claude-dev/ manually.
  • Pull from upstream — the source of truth is this repo.
  • Survive across machines — the install targets are per-machine; run once per machine.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.