AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Env Setup

skill-weisser-dev-awesome-opencode-env-setup · by weisser-dev

Bootstrap developer environment by detecting project type, listing prerequisites, generating .env.example, and producing a Getting Started guide

No reviews yet
0 installs
46 views
0.0% view→install

Install

$ agentstack add skill-weisser-dev-awesome-opencode-env-setup

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access Used
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-weisser-dev-awesome-opencode-env-setup)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Env Setup? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

What I do

  • Detect the project type, language, and framework from repo contents
  • Identify all required prerequisites (runtimes, databases, tools)
  • Generate a .env.example file with all required environment variables
  • Produce a Getting Started guide with step-by-step setup instructions
  • Verify the environment is correctly configured

When to use me

Use this skill when you need to:

  • Onboard a new developer to a project
  • Document the local development setup process
  • Create or update .env.example with missing variables
  • Troubleshoot a broken local development environment
  • Standardize development environment across the team

Process

  1. Detect project type: Scan repository for configuration files
  • package.json -> Node.js (check for next, react, express, etc.)
  • pom.xml / build.gradle -> Java (check for Spring Boot, Quarkus)
  • requirements.txt / pyproject.toml -> Python (check for Django, Flask)
  • go.mod -> Go
  • Cargo.toml -> Rust
  • docker-compose.yml -> Containerized services
  1. Identify prerequisites: List everything needed
  • Runtime version (check .node-version, .python-version, .tool-versions)
  • Package manager (npm, yarn, pnpm, maven, pip, poetry)
  • Databases and services (scan docker-compose, connection strings)
  • External tools (Docker, Redis, Elasticsearch, etc.)
  • CLI tools referenced in scripts
  1. Generate .env.example: Extract all environment variables
  • Scan source for process.env.*, os.environ, System.getenv
  • Scan existing .env files (redact actual values)
  • Scan docker-compose for environment variables
  • Categorize: required vs. optional, with sensible defaults
  1. Produce Getting Started guide: Write step-by-step instructions
  1. Verify setup: Provide verification commands

.env.example Format

# =============================================================================
# Application
# =============================================================================
NODE_ENV=development
PORT=3000
LOG_LEVEL=debug

# =============================================================================
# Database
# =============================================================================
# Required: PostgreSQL connection string
DATABASE_URL=postgresql://user:password@localhost:5432/myapp_dev

# =============================================================================
# Authentication
# =============================================================================
# Required: Generate with `openssl rand -base64 32`
JWT_SECRET=replace-with-generated-secret
JWT_EXPIRY=3600

# =============================================================================
# External Services (optional in development)
# =============================================================================
# SMTP_HOST=smtp.example.com
# SMTP_PORT=587
# SMTP_USER=
# SMTP_PASSWORD=

# =============================================================================
# Feature Flags
# =============================================================================
ENABLE_CACHE=false
ENABLE_RATE_LIMIT=false

Getting Started Template

# Getting Started

## Prerequisites

- [Node.js](https://nodejs.org/) v20+ (check with `node --version`)
- [Docker](https://www.docker.com/) v24+ (check with `docker --version`)
- [Git](https://git-scm.com/) v2.40+

## Setup

1. Clone the repository:
   \`\`\`bash
   git clone 
   cd 
   \`\`\`

2. Install dependencies:
   \`\`\`bash
   npm install
   \`\`\`

3. Set up environment variables:
   \`\`\`bash
   cp .env.example .env
   # Edit .env with your local values
   \`\`\`

4. Start infrastructure services:
   \`\`\`bash
   docker compose up -d
   \`\`\`

5. Run database migrations:
   \`\`\`bash
   npm run db:migrate
   \`\`\`

6. Seed development data (optional):
   \`\`\`bash
   npm run db:seed
   \`\`\`

7. Start the development server:
   \`\`\`bash
   npm run dev
   \`\`\`

## Verify

- Application: http://localhost:3000
- API docs: http://localhost:3000/api-docs
- Health check: `curl http://localhost:3000/health`

## Common Issues

| Problem | Solution |
|---------|----------|
| Port already in use | Change `PORT` in `.env` or kill the process on that port |
| Database connection refused | Ensure Docker is running: `docker compose ps` |
| Missing environment variable | Compare `.env` with `.env.example` |

Rules

  • Never include real secrets or credentials in .env.example
  • Always include comments explaining what each variable does
  • Mark required vs. optional variables clearly
  • Provide sensible development defaults where possible
  • Test the Getting Started guide on a clean machine when feasible
  • Include version requirements for all prerequisites
  • Document platform-specific steps (macOS, Linux, Windows) if they differ

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.