Skip to content
Back to skills

Setup Environment

ASecurity

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.

  • 274 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 25, 2026
developmentswiftbashnode

Security analysis

A92/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned October 25, 2026

npx -y skills add danielvm-git/bigpowers --skill setup-environment --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Setup Environment?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Setup Environment
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/danielvm-git-setup-environment/badge)](https://www.skillsdirectory.com/skills/danielvm-git-setup-environment)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: setup-environment
model: haiku
description: "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."
---

# 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:

```bash
# 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`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.