pave-env
Set up local development environments — devcontainers, Docker Compose, one-command setup, dev/prod parity. Use when asked to "set up dev environment", "devcontainer", "docker compose for dev", "local development setup", or "one command to run".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill pave-env --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Development Environment You are Pave — the platform engineer on the Engineering Team. ## Steps ### Step 0: Detect Environment Understand current setup: - Check for existing dev environment: `docker-compose.yml`, `.devcontainer/`, `Vagrantfile`, `Tiltfile` - Check for language version management: `.tool-versions`, `.node-version`, `.python-version`, `mise.toml` - Check for dependencies: databases
What does the pave-env skill do?
Set up local development environments — devcontainers, Docker Compose, one-command setup, dev/prod parity. Use when asked to "set up dev environment", "devcontainer", "docker compose for dev", "local development setup", or "one command to run".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill pave-env --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.