Environment Setup
Environment verification, tool checking, version validation, and path configuration. Use when checking system requirements, verifying tool installations, validating versions, checking PATH configuration, or when user mentions environment setup, system check, tool verification, version check, missing tools, or installation requirements.
What this skill does
# Environment Setup
**CRITICAL: The description field above controls when Claude auto-loads this skill.**
## Overview
Provides comprehensive environment verification, tool installation checking, version validation, PATH configuration, and environment variable management for development workflows.
## Instructions
### Environment Verification
1. Use `scripts/check-environment.sh` to verify all required tools are installed
2. Check versions of languages, package managers, and build tools
3. Validate PATH configuration and tool accessibility
4. Verify environment variables are properly configured
5. Generate comprehensive environment report
### Tool Installation Verification
1. Use `scripts/check-tools.sh` to verify specific tools (node, python, go, rust, etc.)
2. Check if tools are in PATH and accessible
3. Verify tool versions meet minimum requirements
4. Provide installation instructions for missing tools
5. Detect version managers (nvm, pyenv, rbenv, rustup)
### Version Validation
1. Use `scripts/validate-versions.sh` to check language and tool versions
2. Compare against project requirements (package.json, .tool-versions, etc.)
3. Identify version mismatches and compatibility issues
4. Suggest version upgrades or downgrades
5. Check for deprecated versions
### PATH Configuration
1. Use `scripts/validate-path.sh` to verify PATH is correctly configured
2. Check for tool binaries in expected locations
3. Detect PATH issues (missing entries, duplicate entries, ordering problems)
4. Suggest PATH fixes for shell configuration files
5. Validate system paths vs user paths
### Environment Variable Management
1. Use `scripts/check-env-vars.sh` to validate required environment variables
2. Check for missing, empty, or misconfigured variables
3. Validate API keys and credentials (without exposing values)
4. Suggest environment variable configuration
5. Detect conflicts between .env files and system environment
## Available Scripts
- **check-environment.sh**: Comprehensive environment verification across all tools
- **check-tools.sh**: Verify specific tools are installed and accessible
- **validate-versions.sh**: Check tool versions against requirements
- **validate-path.sh**: Verify PATH configuration and detect issues
- **check-env-vars.sh**: Validate environment variables and configuration
## Templates
- **environment-report.template**: Comprehensive environment status report
- **tool-requirements.md**: Project tool requirements documentation
- **path-config.sh.template**: Shell configuration for PATH setup
- **env-template.template**: Environment variable template file
- **version-requirements.json**: Tool version requirements specification
- **installation-guide.md.template**: Tool installation instructions
## Examples
See `examples/` directory for:
- **basic-usage.md**: Simple environment checks
- **advanced-usage.md**: Complex multi-tool verification
- **common-patterns.md**: Typical environment setup patterns
- **error-handling.md**: Handling missing tools and version issues
- **integration.md**: Using with other skills and workflows
## Requirements
- Support major languages: Node.js, Python, Go, Rust, Ruby, Java, PHP, .NET
- Support package managers: npm, yarn, pnpm, pip, poetry, cargo, gem, maven, composer
- Support build tools: make, cmake, gradle, webpack, vite, rollup
- Support version managers: nvm, pyenv, rbenv, rustup, jenv, phpbrew
- Detect operating system differences (Linux, macOS, Windows/WSL)
- Provide actionable error messages with installation instructions
- Generate reports in multiple formats (text, JSON, markdown)
## Best Practices
- **Never assume tools are installed** - Always verify before proceeding
- **Check versions before operations** - Prevent version-related failures
- **Provide clear error messages** - Include installation instructions
- **Support multiple OSes** - Handle Linux, macOS, Windows/WSL differences
- **Detect version managers** - Use nvm, pyenv, etc. when available
- **Cache verification results** - Avoid redundant checks within same session
- **Report all issues** - Don't fail on first error, collect all problems
## Output Format
All scripts output structured results:
```json
{
"status": "success|warning|error",
"tools": {
"node": {"installed": true, "version": "20.11.0", "required": ">=18.0.0", "status": "ok"},
"python": {"installed": true, "version": "3.11.5", "required": ">=3.9.0", "status": "ok"},
"go": {"installed": false, "status": "missing"}
},
"path": {"valid": true, "issues": []},
"env_vars": {"valid": true, "missing": []},
"recommendations": []
}
```
---
**Purpose**: Comprehensive environment verification and configuration management
**Used by**: All agents requiring tool verification, project setup, and environment validation
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.