agentleFS
Sign inStart free
danielvm-gitdanielvm-git/bigpowers/skills/setup-environment/SKILL.md

setup-environment

Skill288 starsChanged 6 days agoMITView on GitHub

Pre-install dependencies and configure tools before development work begins. Use at session start on a fresh clone, before kickoff-branch, or when user says setup environment or install deps.

  • Reads credentials
  • Installs packages

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read CLAUDE.md / CONVENTIONS.md for required runtimes and commands.

    line 16
  2. Very specific:

    Verify runtime versions (node -v, swift --version, etc.).

    line 17
  3. Very specific:

    Run smoke: lint + one fast test or --version on key tools.

    line 20
  4. Very specific:

    Verify the install: big-counter --version Skip if BCP Plus sizing is not needed for this project.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Setup Environment

HARD GATE — HARD GATE — Environment setup must be idempotent and reproducible. If setup fails, provide clear error messages and remediation steps. Do NOT assume prior state.

Idempotent prep so BUILD phase commands succeed on first run.

Checklist

  1. Read CLAUDE.md / CONVENTIONS.md for required runtimes and commands.
  2. Verify runtime versions (node -v, swift --version, etc.).
  3. Install dependencies (npm ci, bundle install, etc.) — prefer lockfile installs.
  4. Copy .env.example → .env if documented; never commit secrets.
  5. Run smoke: lint + one fast test or --version on key tools.
  6. Record versions in specs/state.yaml under Environment.

BCP Plus Counter (optional)

The big-counter tool is an optional dependency for BCP Plus 13-dimension story sizing:

# Install from PyPI (recommended)
pip install big-counter

# Or from npm
npm install -g big-counter

Verify the install: big-counter --version Skip if BCP Plus sizing is not needed for this project.

Verify

→ verify: test -f CLAUDE.md && grep -q Test CLAUDE.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free