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.
Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running…
$ npx skills add mohitagw15856/pm-claude-skills --skill local-dev-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills local-dev-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "local-dev-setup" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/local-dev-setup into .claude/skills/local-dev-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-dev-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/local-dev-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill local-dev-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills local-dev-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/local-dev-setup .agents/skills/local-dev-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "local-dev-setup" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/local-dev-setup into .agents/skills/local-dev-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-dev-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill local-dev-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills local-dev-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/local-dev-setup .cursor/skills/local-dev-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "local-dev-setup" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/local-dev-setup into .cursor/skills/local-dev-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-dev-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/local-dev-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill local-dev-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills local-dev-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/local-dev-setup .gemini/skills/local-dev-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "local-dev-setup" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/local-dev-setup into .gemini/skills/local-dev-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-dev-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills local-dev-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill local-dev-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/local-dev-setup .github/skills/local-dev-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "local-dev-setup" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/local-dev-setup into .github/skills/local-dev-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-dev-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill local-dev-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills local-dev-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/local-dev-setup .opencode/skills/local-dev-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "local-dev-setup" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/local-dev-setup into .opencode/skills/local-dev-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-dev-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
local-dev-setupWrite 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. 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.
10 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
makedockerbrewcurlgitnpmgopythonpippsqlblackopensslFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
sandbox.stripe.comAlso links to:
go.devdocs.docker.comnodejs.orgdirenv.netdocs.github.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
SECRET_KEYFEATURE_FLAG_SDK_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
cp .env.example .env.localOpen `.env.local` in your editor. Below is a description of every variable and where to get its value:**Using direnv (recommended):** Rename `.env.local` to `.envrc`, add `dotenv` at the top, and run `direnv allow`. Variabmake test-integration # should pick up .env.local automatically# If not: source .env.local && make test-integration# Verify .env.local exists and has all required variablescat .env.local | grep "^[A-Z]" | awk -F= '{print $1}'<(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.
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 1,407 words, ~4,567 tokens.
.claude/skills/local-dev-setup/SKILL.md (or your agent's skills folder).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.
Ask for these if not already provided:
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.
Install these tools before starting. The versions listed are the minimum required — newer patch versions are fine, newer major versions may have compatibility issues.
| Tool | Required version | Install |
|---|---|---|
| [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] | Any | Pre-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) |
| Tool | Purpose | Install |
|---|---|---|
| [direnv] | Auto-load .envrc environment variables | brew install direnv + setup instructions |
| [jq] | Pretty-print JSON in terminal | brew install jq |
| [k9s] | Kubernetes cluster UI (if using K8s locally) | brew install k9s |
| [mkcert] | Local HTTPS certificates | brew install mkcert |
Before starting, make sure you have:
# 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 emailIf 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.
The service requires environment variables for configuration. Never commit actual secrets to the repository.
cp .env.example .env.localOpen .env.local in your editor. Below is a description of every variable and where to get its value:
| Variable | Description | Where to get it | Example (not real) |
|---|---|---|---|
APP_ENV | Environment name | Set to development | development |
APP_PORT | Port the service listens on | Set to 8080 for local | 8080 |
DATABASE_URL | PostgreSQL connection string | Use value from Docker Compose (Section 3) | postgres://app:password@localhost:5432/[service]_dev |
REDIS_URL | Redis connection string | Use value from Docker Compose | redis://localhost:6379 |
SECRET_KEY | Application secret key | Generate with: openssl rand -hex 32 | [random 64-char hex] |
[EXTERNAL_SERVICE]_API_KEY | API key for [External Service] | Retrieve from [1Password vault: "Dev API Keys"] or ask [name] | — |
[EXTERNAL_SERVICE]_BASE_URL | Base URL for [External Service] | Use sandbox URL: https://sandbox.[external-service].com | https://sandbox.stripe.com |
LOG_LEVEL | Logging verbosity | Set to debug for local development | debug |
[FEATURE_FLAG_SDK_KEY] | Feature flag platform SDK key | Retrieve 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.
All infrastructure dependencies run in Docker Compose. You do not need to install PostgreSQL, Redis, or Kafka locally.
# 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]| Service | Port | Purpose | Health check |
|---|---|---|---|
| PostgreSQL [version] | 5432 | Primary database | pg_isready -U app |
| Redis [version] | 6379 | Cache and session store | redis-cli ping |
| [Kafka + Zookeeper] | 9092 / 2181 | Message queue | kafka-topics.sh --list |
| [Mock server — e.g. WireMock] | 8089 | Mocks for external APIs in tests | curl localhost:8089/__admin |
| [LocalStack] | 4566 | AWS 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.
# 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# 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/]# 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] rowsWhat the seed creates:
[admin@example.com] / password: see .env.example for dev password variableTo reset to a clean state:
docker compose down -v # wipe database volume
docker compose up -d # start fresh
make db-migrate
make db-seed# 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}# 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# 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]# 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-integrationExpected test results:
Before pushing a PR, always run:
make lint # code linting — must pass
make test # full test suite — must pass
make build # verify compilation — must passInstall the recommended extensions (VS Code will prompt you automatically):
// .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.].idea/runConfigurations/ — they appear automaticallySymptom: docker compose ps shows a container as Exited (1) seconds after starting.
# 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/amd64Symptom: Service fails to start with "connection refused" or "dial tcp localhost:5432: connect: connection refused"
# 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 exactlySymptom: make db-migrate errors with "ERROR: relation [table] already exists"
# 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 databaseSymptom: Integration tests fail because they cannot connect to PostgreSQL or Redis.
# 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-integrationmake lint fails on a fresh checkoutSymptom: Lint errors on files you have not modified.
# 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 lintSymptom: Service starts but immediately fails with "missing required environment variable: [VAR]"
# 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)Before opening your first pull request, verify:
Setup complete:
make build passes with no errorsmake test passes — all tests greenmake lint passes — no lint errorsGit and GitHub:
ls .git/hooks/pre-commit should exist)main (not committing directly to main)Development workflow:
[test command for single test]docker compose down -v && docker compose up -d && make db-migrate && make db-seedFirst PR:
make test && make lint && make build all pass locally before requesting review.env.example — no undocumented variables© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/local-dev-setup of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Local Dev Setup this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~4.6k | Automated safety check: Notes | MIT | |
| LangBot Deployment Guidelangbot-app/LangBot | 18k | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Add Config Env Varbaserow/baserow | 6.1k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Monstermq Broker Configvogler75/monster-mq | 143 | — | ~2.2k | Automated safety check: Pass | GPL-3.0 | |
| Deploymentmatrixorigin/memoria | 608 | — | ~1.6k | Automated safety check: Notes | Apache-2.0 | |
| Docker Compose Development Patternsaffaan-m/ECC | 275k | 4 repos | ~2.1k | Automated safety check: Notes | MIT |
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.
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…
vogler75/monster-mq
Guide for configuring, deploying, and operating the MonsterMQ broker.
matrixorigin/memoria
Deploy Memoria with Docker Compose or Kubernetes. An agent skill from matrixorigin/memoria.
affaan-m/ECC
Practical Docker and Docker Compose patterns for local development: stacks, override files, networking, volumes, container hardening and debugging.
docker/skills
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…
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.
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
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.
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.
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.
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.
Categories
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.