Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Env Setup

ASecurity

Environment setup assistant — detects project requirements, generates .env.example, documents prerequisites, creates setup scripts, and verifies the development environment is ready. Use when setting up a project for the first time.

7 stars
0 votes
0 copies
1 views
Added 5/28/2026
ai-agentspythonrustgobashsqlnodedockergitapidatabase

Works with

cliapi

Security Analysis

A100/100

Scanned 5/28/2026

$npx -y skills add viknesh20-20/claude-code-tool-kit --skill env-setup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Env Setup?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Env Setup
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/viknesh20-20-env-setup/badge)](https://www.skillsdirectory.com/skills/viknesh20-20-env-setup)

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

Download with Pro
Files
SKILL.md
---
name: env-setup
description: "Environment setup assistant — detects project requirements, generates .env.example, documents prerequisites, creates setup scripts, and verifies the development environment is ready. Use when setting up a project for the first time."
argument-hint: "[optional: 'verify' to check current environment]"
allowed-tools: Read, Grep, Glob, Bash, Write
---

# Environment Setup

## Detect Requirements
!`ls package.json requirements.txt pyproject.toml go.mod Cargo.toml *.csproj Gemfile composer.json mix.exs 2>/dev/null`
!`ls .env .env.example .env.sample .env.template 2>/dev/null`
!`ls Dockerfile docker-compose* Makefile Procfile 2>/dev/null`

## Current Environment
!`node --version 2>/dev/null || echo "Node.js: not installed"`
!`python3 --version 2>/dev/null || echo "Python: not installed"`
!`go version 2>/dev/null || echo "Go: not installed"`
!`rustc --version 2>/dev/null || echo "Rust: not installed"`
!`docker --version 2>/dev/null || echo "Docker: not installed"`
!`git --version 2>/dev/null`

---

## Setup Process

### Step 1: Identify Requirements
Scan project files to determine:
- Runtime(s) and version(s) needed
- Package manager(s)
- Database(s)
- Cache (Redis, Memcached)
- External services (S3, email, payment, etc.)
- Build tools
- Required CLI tools

### Step 2: Generate .env.example
Scan the codebase for environment variable references:
```bash
grep -rn "process\.env\." --include="*.ts" --include="*.js" | ...
grep -rn "os\.environ\|os\.getenv" --include="*.py" | ...
grep -rn "os\.Getenv" --include="*.go" | ...
```

Generate `.env.example` with:
```
# Application
APP_PORT=3000
APP_ENV=development
APP_SECRET=change-me-to-a-random-string

# Database
DATABASE_URL=postgresql://user:password@localhost:5432/dbname

# External Services
# API_KEY=your-api-key-here
```

**Include:**
- Comments explaining each variable
- Safe defaults for development
- Placeholder values for secrets (never real values)
- Grouped by category

### Step 3: Check Prerequisites
Verify each requirement is met:
| Requirement | Status | Version | Required |
|-------------|--------|---------|----------|
| Node.js | OK/MISSING | v20.x | >=18 |
| ... | ... | ... | ... |

### Step 4: Generate Setup Instructions
Create or update setup documentation:
1. Prerequisites to install
2. Clone and install steps
3. Environment configuration
4. Database setup (create, migrate, seed)
5. Start development server
6. Verify everything works

### Step 5: Verify
Run a series of checks:
- [ ] All required runtimes installed at correct versions
- [ ] Dependencies installed successfully
- [ ] Environment variables configured
- [ ] Database accessible (if applicable)
- [ ] Dev server starts without errors
- [ ] Tests pass

## Rules
- Never put real secrets in .env.example
- Use descriptive comments for every variable
- Group variables by service/purpose
- Include both required and optional variables
- Document which variables have safe defaults

Attribution

viknesh20-20viknesh20-20
View sourceSee grades on GitHubMore from viknesh20-20 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →