Agent skill

Local Dev Setup

by mohitagw15856 in mohitagw15856/pm-claude-skills

Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running…

MITAuto-check: notesDevOps & Cloud

Install Local Dev Setup

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill local-dev-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills local-dev-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/local-dev-setup .claude/skills/local-dev-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
local-dev-setup
GitHub stars
1.4k
Token cost
~4.6k tokens
SKILL.md length
1,407 words
Files
1
Skills in repo
1,322
Repo updated
First seen
Licence
MIT

At a glance

Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running…

  • Works in 10 steps: Repository Setup → Environment Variables → Local Service Dependencies → …
  • Asked to write a dev setup guide
  • SKILL.md covers Required Inputs, Output Format, Prerequisites and 1. Repository Setup, plus 8 more sections
  • Calls make, docker and brew; reaches sandbox.stripe.com; needs SECRET_KEY and FEATURE_FLAG_SDK_KEY

What it does

Local Dev Setup is an agent skill from mohitagw15856/pm-claude-skills. Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running the service, running tests, common gotchas, IDE recommendations, and first-contribution checklist. Use when asked to write a dev setup guide, create onboarding documentation for engineers, document local environment setup, or write a getting-started guide for a codebase. Produces a complete setup guide that a new…

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Secrets management and Containers. It works with Docker and Homebrew. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to write a dev setup guide
  • Create onboarding documentation for engineers
  • Document local environment setup
  • Write a getting-started guide for a codebase

Example prompts

  • “/local-dev-setup”

Requirements

  • Python 3
  • Node.js
  • Docker
  • A credential in SECRET_KEY
  • A credential in FEATURE_FLAG_SDK_KEY

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Repository Setup
  2. Environment Variables
  3. Local Service Dependencies
  4. Install Dependencies and Build
  5. Database Setup and Seeding
  6. Running the Service
  7. Running Tests
  8. IDE Setup
  9. Common Gotchas and Troubleshooting
  10. First Contribution Checklist

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • make
    • docker
    • brew
    • curl
    • git
    • npm
    • go
    • python
    • pip
    • psql
    • black
    • openssl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • sandbox.stripe.com

    Also links to:

    • go.dev
    • docs.docker.com
    • nodejs.org
    • direnv.net
    • docs.github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • SECRET_KEY
    • FEATURE_FLAG_SDK_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Local Dev Setup loads about 4.6k tokens when it runs. Until then it costs about 165 tokens; SKILL.md has 1,407 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~165
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:97
    cp .env.example .env.local
  • NoteMentions a .env fileSKILL.md:102
    Open `.env.local` in your editor. Below is a description of every variable and where to get its value:
  • NoteMentions a .env fileSKILL.md:116
    **Using direnv (recommended):** Rename `.env.local` to `.envrc`, add `dotenv` at the top, and run `direnv allow`. Variab
  • NoteMentions a .env fileSKILL.md:402
    make test-integration  # should pick up .env.local automatically
  • NoteMentions a .env fileSKILL.md:403
    # If not: source .env.local && make test-integration
  • NoteMentions a .env fileSKILL.md:433
    # Verify .env.local exists and has all required variables
  • NoteMentions a .env fileSKILL.md:434
    cat .env.local | grep "^[A-Z]" | awk -F= '{print $1}'
  • NoteMentions a .env fileSKILL.md:438
    <(grep "^[A-Z_]*=" .env.local | cut -d= -f1 | sort)

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 1,407 words, ~4,567 tokens.

Download SKILL.mdSave it as .claude/skills/local-dev-setup/SKILL.md (or your agent's skills folder).
name
local-dev-setup
description
Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running the service, running tests, common gotchas, IDE recommendations, and first-contribution checklist. Use when asked to write a dev setup guide, create onboarding documentation for engineers, document local environment setup, or write a getting-started guide for a codebase. Produces a complete setup guide that a new engineer can follow from zero to running tests in under 30 minutes, with a troubleshooting section for the most common setup failures.

Local Dev Setup Skill

Produce a complete local development environment setup guide for a service or project — walking a new engineer from zero (a clean laptop) to a working local environment with passing tests in under 30 minutes. A good setup guide reduces onboarding time, prevents the "it works on my machine" problem, and lets engineers make their first contribution with confidence. Write every step as a concrete command or action — not a description of what needs to happen.

Required Inputs

Ask for these if not already provided:

  • Service name and what it does
  • Tech stack — language, framework, database, cache, message queue, and any external services
  • Dependencies — databases, caches, message queues, and external services (mocked or real)
  • Test framework — how tests are run and what the test suite covers
  • CI/CD platform — GitHub Actions, CircleCI, Jenkins, etc. (for context on what "passing CI" means locally)

Output Format


Local Development Setup: [Service Name]

Tech stack: [Language + version] | [Framework] | [Database] | [Cache] Estimated setup time: [20–30 minutes] on a clean machine Last verified: [Date] on [macOS Ventura 13.x / Ubuntu 22.04] Questions? Ask in [Slack: #[team-channel]] or ping [@tech-lead-handle]

First contribution? Complete setup first (this doc), then read [CONTRIBUTING.md] for code standards and PR process.


Prerequisites

Install these tools before starting. The versions listed are the minimum required — newer patch versions are fine, newer major versions may have compatibility issues.

Required Tools
ToolRequired versionInstall
[Git]2.x+Pre-installed on most systems; or brew install git
[Language runtime — e.g. Go][1.22+][https://go.dev/dl/ or brew install go]
[Docker]24.x+[https://docs.docker.com/get-docker/]
[Docker Compose]2.x+Included with Docker Desktop; or brew install docker-compose
[Make]AnyPre-installed on macOS/Linux
[Tool — e.g. Node.js][20.x+][brew install node or https://nodejs.org]
[Tool — e.g. psql client][15+]brew install postgresql@15 (client only)
ToolPurposeInstall
[direnv]Auto-load .envrc environment variablesbrew install direnv + setup instructions
[jq]Pretty-print JSON in terminalbrew install jq
[k9s]Kubernetes cluster UI (if using K8s locally)brew install k9s
[mkcert]Local HTTPS certificatesbrew install mkcert
Required Accounts and Access

Before starting, make sure you have:

  • GitHub access to [org/repo] — request via [access request process / Slack: #it-help]
  • [AWS / GCP / Azure] account with [dev environment] access — request via [process]
  • [Internal tool — e.g. 1Password] for retrieving development secrets — request via [process]
  • [VPN access] if required to reach internal services — request via [process]

1. Repository Setup

bash
# Clone the repository
git clone git@github.com:[org]/[repo-name].git
cd [repo-name]

# Install git hooks (required — enforces commit message format and runs pre-commit checks)
make install-hooks
# Or manually:
# cp scripts/hooks/pre-commit .git/hooks/pre-commit && chmod +x .git/hooks/pre-commit

# Verify your git setup
git config user.name   # should be your name
git config user.email  # should be your work email

If you see a permission denied error on clone: Your SSH key is not added to GitHub. Follow GitHub's SSH key guide or use HTTPS with a personal access token instead.


2. Environment Variables

The service requires environment variables for configuration. Never commit actual secrets to the repository.

Step 1 — Copy the example file
bash
cp .env.example .env.local
Step 2 — Fill in the values

Open .env.local in your editor. Below is a description of every variable and where to get its value:

VariableDescriptionWhere to get itExample (not real)
APP_ENVEnvironment nameSet to developmentdevelopment
APP_PORTPort the service listens onSet to 8080 for local8080
DATABASE_URLPostgreSQL connection stringUse value from Docker Compose (Section 3)postgres://app:password@localhost:5432/[service]_dev
REDIS_URLRedis connection stringUse value from Docker Composeredis://localhost:6379
SECRET_KEYApplication secret keyGenerate with: openssl rand -hex 32[random 64-char hex]
[EXTERNAL_SERVICE]_API_KEYAPI key for [External Service]Retrieve from [1Password vault: "Dev API Keys"] or ask [name]—
[EXTERNAL_SERVICE]_BASE_URLBase URL for [External Service]Use sandbox URL: https://sandbox.[external-service].comhttps://sandbox.stripe.com
LOG_LEVELLogging verbositySet to debug for local developmentdebug
[FEATURE_FLAG_SDK_KEY]Feature flag platform SDK keyRetrieve from [LaunchDarkly/Split dev project]—

Using direnv (recommended): Rename .env.local to .envrc, add dotenv at the top, and run direnv allow. Variables will load automatically when you cd into the project.


3. Local Service Dependencies

All infrastructure dependencies run in Docker Compose. You do not need to install PostgreSQL, Redis, or Kafka locally.

bash
# Start all dependencies (PostgreSQL, Redis, and any other services)
docker compose up -d

# Verify all containers are healthy
docker compose ps
# Expected output: all services show "healthy" status

# View logs if something is not healthy
docker compose logs [service-name]
What Docker Compose Starts
ServicePortPurposeHealth check
PostgreSQL [version]5432Primary databasepg_isready -U app
Redis [version]6379Cache and session storeredis-cli ping
[Kafka + Zookeeper]9092 / 2181Message queuekafka-topics.sh --list
[Mock server — e.g. WireMock]8089Mocks for external APIs in testscurl localhost:8089/__admin
[LocalStack]4566AWS service emulation (S3, SQS, etc.)aws --endpoint-url=http://localhost:4566 s3 ls

If a container exits immediately: See Troubleshooting section — common causes are port conflicts and Docker memory limits.

Stopping Dependencies
bash
# Stop containers (preserves data volumes)
docker compose stop

# Stop and remove containers (clears data — use when you want a fresh start)
docker compose down -v

4. Install Dependencies and Build

bash
# Install language dependencies
# Go:
go mod download

# Node.js:
npm install   # or: yarn install / pnpm install

# Python:
python -m venv .venv
source .venv/bin/activate   # On Windows: .venv\Scripts\activate
pip install -r requirements-dev.txt

# Verify build compiles cleanly
make build
# Expected: no errors; binary or compiled output in [./bin/ or ./dist/]

5. Database Setup and Seeding

bash
# Run database migrations (creates tables and schema)
make db-migrate
# Or directly:
# [Migration command — e.g. "go run ./cmd/migrate up" or "alembic upgrade head" or "npm run db:migrate"]

# Verify migrations applied
# psql $DATABASE_URL -c "\dt"  # should list all tables

# Seed the database with development data
make db-seed
# Or directly:
# [Seed command — e.g. "go run ./cmd/seed" or "python scripts/seed.py" or "npm run db:seed"]

# Verify seed data is present
# psql $DATABASE_URL -c "SELECT COUNT(*) FROM [primary-table]"
# Expected: [N] rows

What the seed creates:

  • [N] test user accounts (credentials in [scripts/seed/README.md or .env.example])
  • [N] sample [resources] for development and testing
  • Admin account: [admin@example.com] / password: see .env.example for dev password variable

To reset to a clean state:

bash
docker compose down -v   # wipe database volume
docker compose up -d     # start fresh
make db-migrate
make db-seed

6. Running the Service

bash
# Run the service locally
make run
# Or directly:
# [Run command — e.g. "go run ./cmd/server" or "python app.py" or "npm run dev"]

# Expected output:
# [Example of healthy startup log lines — e.g.:]
# {"level":"info","message":"Database connected","host":"localhost","port":5432}
# {"level":"info","message":"Redis connected","host":"localhost","port":6379}
# {"level":"info","message":"Server listening","port":8080}
Verify It's Working
bash
# Health check
curl http://localhost:8080/health
# Expected: {"status":"ok","version":"[git-sha]"}

# Test a key endpoint (authenticated)
# First, get a dev token:
curl -X POST http://localhost:8080/api/v1/auth/login \
  -H "Content-Type: application/json" \
  -d '{"email":"[dev-user-from-seed]@example.com","password":"[dev-password-from-env]"}'
# Copy the token from the response, then:

curl http://localhost:8080/api/v1/[resource] \
  -H "Authorization: Bearer [token-from-above]"
# Expected: 200 with JSON response
Hot Reload (for Development)
bash
# Run with hot reload — service restarts automatically on file changes
make run-dev
# Or:
# [Hot reload command — e.g. "air" for Go / "uvicorn --reload" for Python / "npm run dev" for Node]

7. Running Tests

bash
# Run the full test suite
make test
# Or:
# [Test command — e.g. "go test ./..." or "pytest" or "npm test"]

# Run tests with coverage report
make test-coverage
# Coverage report: [./coverage.html or stdout]

# Run a specific test file or test case
# Go: go test ./pkg/[package]/... -run TestFunctionName
# Python: pytest tests/test_[module].py::TestClass::test_method -v
# Node: npm test -- --testPathPattern=[filename]

# Run only unit tests (fast — no external dependencies)
make test-unit

# Run only integration tests (requires Docker Compose dependencies running)
make test-integration

Expected test results:

  • Unit tests: [N] tests, all pass, [<30] seconds
  • Integration tests: [N] tests, all pass, [<2] minutes
  • Coverage: [≥80]% (enforced in CI — tests fail below this threshold)

Before pushing a PR, always run:

bash
make lint      # code linting — must pass
make test      # full test suite — must pass
make build     # verify compilation — must pass

8. IDE Setup

Install the recommended extensions (VS Code will prompt you automatically):

json
// .vscode/extensions.json — already in the repository
{
  "recommendations": [
    "[language-extension — e.g. golang.go]",
    "dbaeumer.vscode-eslint",
    "esbenp.prettier-vscode",
    "ms-azuretools.vscode-docker",
    "eamodio.gitlens"
  ]
}

Workspace settings are in .vscode/settings.json — format on save is enabled, linter is configured automatically.

[Language]-specific setup:

[e.g. Go: The gopls language server is installed automatically by the Go extension.
 Run "Go: Install/Update Tools" from the command palette after installing the extension.]
Show full SKILL.md (577 more words)Show less
JetBrains (IntelliJ / GoLand / PyCharm / WebStorm)
  • Open the project root as the project directory
  • [Language SDK]: set to [version] — File → Project Structure → SDKs
  • Run configurations are checked into .idea/runConfigurations/ — they appear automatically
  • Enable "Run formatters on save" in Settings → Tools → Actions on Save

9. Common Gotchas and Troubleshooting

Docker container exits immediately on startup

Symptom: docker compose ps shows a container as Exited (1) seconds after starting.

bash
# Check the container logs for the error
docker compose logs [container-name]

# Common causes:
# 1. Port already in use — find and kill the conflicting process:
lsof -ti tcp:[port] | xargs kill -9

# 2. Docker doesn't have enough memory — allocate at least 4GB in Docker Desktop:
# Docker Desktop → Settings → Resources → Memory → 4GB

# 3. M1/M2 Mac architecture mismatch — add platform directive to docker-compose.yml:
# platform: linux/amd64
Database connection refused

Symptom: Service fails to start with "connection refused" or "dial tcp localhost:5432: connect: connection refused"

bash
# Is PostgreSQL actually running?
docker compose ps postgres
# If not running: docker compose up -d postgres

# Is it on the right port?
lsof -i :5432

# Can you connect manually?
psql postgres://app:password@localhost:5432/[service]_dev -c "SELECT 1"

# If using a custom DATABASE_URL, verify it matches the docker-compose.yml settings exactly
Migrations fail with "relation already exists"

Symptom: make db-migrate errors with "ERROR: relation [table] already exists"

bash
# Check current migration state
[migration status command — e.g. "go run ./cmd/migrate status" or "alembic current"]

# The database may be in a partial state — reset it:
docker compose down -v
docker compose up -d
make db-migrate  # should now succeed on a clean database
Tests fail with "connection refused" or dependency errors

Symptom: Integration tests fail because they cannot connect to PostgreSQL or Redis.

bash
# Integration tests need Docker Compose running
docker compose up -d

# Verify all containers are healthy before running tests
docker compose ps   # all should show "healthy"

# If containers are running but tests still fail, check environment variables:
make test-integration  # should pick up .env.local automatically
# If not: source .env.local && make test-integration
make lint fails on a fresh checkout

Symptom: Lint errors on files you have not modified.

bash
# Formatting issue — auto-fix with:
# Go:
gofmt -w .
goimports -w .

# Python:
black .
isort .

# Node/TypeScript:
npm run lint:fix
# Or: npx eslint --fix . && npx prettier --write .

# Re-run lint to confirm
make lint
Environment variables not loading

Symptom: Service starts but immediately fails with "missing required environment variable: [VAR]"

bash
# Verify .env.local exists and has all required variables
cat .env.local | grep "^[A-Z]" | awk -F= '{print $1}'

# Compare against required variables in .env.example
diff <(grep "^[A-Z_]*=" .env.example | cut -d= -f1 | sort) \
     <(grep "^[A-Z_]*=" .env.local | cut -d= -f1 | sort)

# Missing variables are shown in left column only (< prefix)

10. First Contribution Checklist

Before opening your first pull request, verify:

Setup complete:

  • make build passes with no errors
  • make test passes — all tests green
  • make lint passes — no lint errors
  • Service starts and health check returns 200
  • You can authenticate and call at least one API endpoint

Git and GitHub:

  • You have read [CONTRIBUTING.md] — code standards, commit message format, PR process
  • Your git user.name and user.email are set correctly
  • Pre-commit hooks are installed (ls .git/hooks/pre-commit should exist)
  • You have branched from main (not committing directly to main)

Development workflow:

  • You know how to run a specific test: [test command for single test]
  • You know how to reset the database: docker compose down -v && docker compose up -d && make db-migrate && make db-seed
  • You have joined [Slack: #[team-channel]] and [#[service-consumers-channel] if applicable]
  • You have read the [architecture overview doc / README] — you understand what this service does

First PR:

  • Changes are small and focused — one logical change per PR
  • Tests are added or updated for your change
  • make test && make lint && make build all pass locally before requesting review
  • PR description explains what changed and why (use the [pr-description-writer skill] if needed)

Quality Checks

  • A new engineer with no prior knowledge of the project can follow this guide from start to finish without asking anyone for help
  • Every command is tested on a clean environment — not written from memory and assumed to work
  • Environment variables table covers every variable in .env.example — no undocumented variables
  • The troubleshooting section covers the 5 most common real failures observed during onboarding — not theoretical issues
  • Docker Compose version and Docker Desktop memory requirements are stated explicitly
  • "Expected output" is shown for key commands so engineers know whether a step succeeded
  • Setup time estimate is honest — verified by timing a real onboarding session, not estimated

Anti-Patterns

  • Do not write setup steps from memory without testing them on a clean machine — steps that skip implicit knowledge break for new engineers
  • Do not leave environment variables undocumented — every variable in .env.example must appear in the Variables table with a description and source
  • Do not write troubleshooting entries for theoretical issues — only include problems that have actually occurred during real onboarding sessions
  • Do not assume Docker Desktop is configured correctly — memory limits and platform (M1/M2) compatibility must be explicitly called out
  • Do not omit expected output for key commands — without "expected output", engineers cannot tell whether a step succeeded or silently failed

Example Trigger Phrases

  • "Write a dev setup guide."
  • "Create onboarding documentation for engineers."
  • "Document local environment setup."
  • "Write a getting-started guide for a codebase."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/local-dev-setup of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Local Dev Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Local Dev Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Local Dev Setup this skillmohitagw15856/pm-claude-skills1.4k—~4.6kAutomated safety check: NotesMIT
LangBot Deployment Guidelangbot-app/LangBot18k—~1.2kAutomated safety check: NotesApache-2.0
Add Config Env Varbaserow/baserow6.1k—~1.1kAutomated safety check: PassCustom licence
Monstermq Broker Configvogler75/monster-mq143—~2.2kAutomated safety check: PassGPL-3.0
Deploymentmatrixorigin/memoria608—~1.6kAutomated safety check: NotesApache-2.0
Docker Compose Development Patternsaffaan-m/ECC275k4 repos~2.1kAutomated safety check: NotesMIT

Similar skills

  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.2k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Add Config Env Var

    baserow/baserow

    Add a Baserow configuration environment variable for the backend, frontend, or both, and propagate it through settings, Nuxt runtime config, Docker Compose, documentation, consumers, and tests as…

    6.1k GitHub stars~1.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Monstermq Broker Config

    vogler75/monster-mq

    Guide for configuring, deploying, and operating the MonsterMQ broker.

    143 GitHub stars~2.2k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Deployment

    matrixorigin/memoria

    Deploy Memoria with Docker Compose or Kubernetes. An agent skill from matrixorigin/memoria.

    608 GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Practical Docker and Docker Compose patterns for local development: stacks, override files, networking, volumes, container hardening and debugging.

    275k GitHub starsUsed in 4 repos~2.1k tokens
    DevOps & CloudAuto-check: notes
  • Official

    A skill your agent uses when authoring, planning, or running a declarative sbxenv.yaml file for Docker Sandboxes (sbx env create/run/plan/exec/rm), even if the user just says they want to "check in…

    539 GitHub stars~4k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,322 skills in this repo
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Offer Comparison

    mohitagw15856/pm-claude-skills

    Compare two or more job offers as total-comp curves over four years — vesting cliffs, bonuses, 401(k) match, and the crossover year computed, not vibed.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Refinance Breakeven

    mohitagw15856/pm-claude-skills

    Compute the month a refinance actually starts saving money — payment delta, breakeven month, and total interest on both paths including the term-reset trap.

    1.4k GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • Rent Vs Buy

    mohitagw15856/pm-claude-skills

    Model rent-vs-buy honestly — year-by-year net position for both paths including the assumption everyone drops (the renter invests the difference), with a breakeven horizon instead of a verdict.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Local Dev Setup

What does Local Dev Setup do?

Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running…. Local Dev Setup is an agent skill from mohitagw15856/pm-claude-skills. Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running the service, running tests, common gotchas, IDE recommendations, and first-contribution checklist.

When should I use Local Dev Setup?

Local Dev Setup fits situations like: asked to write a dev setup guide; create onboarding documentation for engineers; document local environment setup; write a getting-started guide for a codebase.

How do I install Local Dev Setup in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill local-dev-setup -a claude-code`. Or copy the skill folder (skills/local-dev-setup in mohitagw15856/pm-claude-skills) into .claude/skills/local-dev-setup in your project. Claude Code loads it when a task matches its description.

How do I install Local Dev Setup in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill local-dev-setup -a codex`. Or copy the skill folder (skills/local-dev-setup in mohitagw15856/pm-claude-skills) into .agents/skills/local-dev-setup in your project. Codex loads it when a task matches its description.

Can I use Local Dev Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill local-dev-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/local-dev-setup, .gemini/skills/local-dev-setup, .github/skills/local-dev-setup and .opencode/skills/local-dev-setup in your project.

What does Local Dev Setup need to run?

Going by SKILL.md and its folder, Local Dev Setup needs the command-line tools its instructions call (make, docker, brew, curl, git and npm) and credentials named SECRET_KEY and FEATURE_FLAG_SDK_KEY. Our summary lists: Python 3; Node.js; Docker; A credential in SECRET_KEY; A credential in FEATURE_FLAG_SDK_KEY.

Does Local Dev Setup access the network?

SKILL.md names 6 domains. In commands or code: sandbox.stripe.com; the agent is likely to contact it when it follows the instructions. As links in the text: go.dev, docs.docker.com, nodejs.org, direnv.net and docs.github.com. This is read from the text; nothing was executed.

Is Local Dev Setup safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Local Dev Setup use?

Local Dev Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Local Dev Setup use?

About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Local Dev Setup?

Skills that share tags, products or a category with Local Dev Setup: LangBot Deployment Guide (langbot-app/LangBot, 18k stars), Add Config Env Var (baserow/baserow, 6.1k stars), Monstermq Broker Config (vogler75/monster-mq, 143 stars) and Deployment (matrixorigin/memoria, 608 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Local Dev Setup?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,431 GitHub stars. The repository holds 1,322 skills in this directory. The repository was last updated on October 7, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.