# Set Up Reliable Development Environments

New machines and project onboarding often fail because required tools, versions, and configuration steps are unclear. This skill creates platform-specific setup, verification, and troubleshooting guidance.

## Install

```bash
npx skillstore add sickn33/environment-setup-guide
```

## Metadata

- Status: approved
- Slug: sickn33-environment-setup-guide
- Skillstore revision: r2
- Version status: missing
- Tree hash: 1f10032a707fc51135a23d4499a2e1c6c66a7f9e63ddc69f0b275efc0881d8b5
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/environment-setup-guide
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/sickn33-environment-setup-guide
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-environment-setup-guide/manifest

## Capabilities

- Identifies required languages, package managers, databases, development tools, and configuration files.
- Provides separate installation guidance for macOS, Linux, and Windows.
- Creates setup sequences for Node.js, Python, Docker, and database-backed projects.
- Adds version checks, service checks, and basic application verification steps.
- Documents environment variable templates without supplying real credentials.
- Explains common PATH, permission, port, and database connection problems.

## Use Cases

- Onboard a New Developer: Create a complete setup checklist with prerequisites, project configuration, verification steps, and common fixes.
- Prepare a Replacement Workstation: Rebuild a working development environment on a new operating system while preserving project requirements.
- Standardize Project Documentation: Turn informal installation notes into structured, testable environment documentation for contributors.

## Prompt Templates

### Check My Current Environment

```
Review my operating system and project requirements. List safe commands that check installed tool versions before suggesting any changes.
```

### Create a Project Setup Guide

```
Create setup instructions for {project type} on {operating system}. Include prerequisites, pinned versions, dependency installation, environment templates, verification, and troubleshooting.
```

### Adapt Setup Across Platforms

```
Convert these existing setup notes for macOS, Ubuntu, and Windows. Separate platform commands and identify steps that require administrator approval.
```

### Audit and Harden Setup Automation

```
Review this setup workflow for remote scripts, elevated commands, lifecycle hooks, weak credentials, network exposure, and destructive changes. Propose safer verified alternatives.
```

## Limitations

- Instructions require review for the user's operating system, architecture, shell, and package sources.
- The skill cannot verify third-party installers, repositories, or packages without additional inspection.
- Commands may change system packages, shell configuration, services, containers, or project data.
- Version examples can become outdated and should be checked against project requirements.

## Best Practices

- Check existing versions and project requirements before installing or changing anything.
- Pin versions and verify checksums or signatures for downloaded installers.
- Separate verification from changes and request approval before privileged, destructive, or data-changing commands.

## Anti Patterns

- Do not execute mutable remote scripts directly with administrator privileges.
- Do not place real secrets or reusable passwords in examples, logs, or setup documentation.
- Do not run dependency hooks, migrations, or project scripts before reviewing their effects.

## Security Audit

- Audited at: 2026-07-23T23:30:47.198\+00:00
- Summary: Most static findings are false positives caused by Markdown fences, placeholders, local addresses, and ordinary setup references. Confirmed risks include mutable remote installers, root execution, Docker group privileges, and exposed default database credentials. No prompt injection or data-exfiltration intent was found.

## Stats

- Views: 159
- Downloads: 9
- Favorites: 0
- Popularity score: 0