More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    🩺 Env Doctor

    3

    Env Doctor guides a local, read-only diagnosis when an app works on one machine but not another.

    Free

    10 usesSecurity scanned
    🩺 Env Doctor

    🩺 Env Doctor

    Example session with this skill installed

    I can't get this project to start. Why won't it run? Check my local environment and find out why the server is failing.

    • Read your context and instructions
    • Compiled the env doctor

    Env Doctor Findings

    1. [High] Port 3000 is already in use
      Evidence: lsof identifies PID 81234 (node) owned by your user.
      Fix: stop that app from its owning terminal with Ctrl+C, or leave it running and start this project on another port. No process was terminated.

    2. [High] Required environment key is missing
      Evidence: DATABASE_URL appears in .env.example but is absent from .env; no values were displayed.
      Fix: add DATABASE_URL locally using the value from your approved development setup.

    What I Checked
    Node runtime, dependencies, common ports, environment key presence, and local services. No .env values were displayed or retained.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    What it does

    Env Doctor guides a local, read-only diagnosis when an app works on one machine but not another. It checks project type, runtime versions, dependencies, required environment-variable key names, local port ownership, Docker configuration, and service health across Node.js, Python, Go, and Docker projects.

    Why use this skill

    Environment failures often look like application bugs. Env Doctor follows a prioritized workflow so you can identify the likely setup issue before changing code. It never asks for secret values, never prints .env contents, and does not kill processes or modify project files blindly. Findings include the evidence checked, the likely cause, and shell-specific next steps.

    Cross-platform fixes

    Commands are matched to the user's shell: PowerShell on Windows, or Bash-compatible commands on macOS and Linux. Port checks identify the owning process before any stop action is suggested.

    Supported tools

    • Runtimes: Node.js, Python, Go, Docker
    • Services: Postgres, MySQL, Redis
    • Package managers: npm, pip, go mod
    • System checks: dependency state, key-only environment validation, port ownership, Docker configuration, and local service health

    • Focuses on Node.js, Python, Go, Docker, and common local services; unusual stacks may need additional checks.
    • Environment validation compares key names and present/empty state only; it never verifies secret values.
    • Diagnosis is read-only and does not automatically run fixes or stop processes.
    • Commands depend on the matching runtime and system tools being installed.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    10 uses

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    • Free with an Agensi account

    Requires

    Python
    macOS

    Permissions

    Read Files

    File Scopes

    package.json
    requirements.txt
    go.mod
    Dockerfile
    .env
    .env.example
    **/node_modules/**

    Env Doctor needs terminal access to run version checks (`node --version`), port checks (`lsof -i :3000`), and service checks (`pg_isready`). File read access reads manifest files (package.json, requirements.txt) and .env files to validate configuration. No write, browser, network, or env var access required.

    Listed5 months ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions

    Env Doctor is compatible with any AI agent that has file system access and terminal execution capabilities. It works across Windows, macOS, and Linux environments to identify and resolve system-level inconsistencies.

    Unlike generic troubleshooting, this skill uses a structured diagnostic tree to scan specific system ports, check database service statuses, and cross-reference your environment variables against template files like .env.example.

    No manual configuration is needed. Simply run the skill within your project directory, and it will automatically detect your stack—whether it's Node.js, Python, Go, or Docker—to begin the health check.

    This skill provides a detailed report of detected issues along with the specific, prioritized bash or terminal commands required to fix them, such as clearing port conflicts or installing missing dependencies.

    Your purchase includes the full skill set for project diagnostics and 12 months of version updates to ensure compatibility with new package manager versions and database releases.

    Yes, Env Doctor is specifically designed to detect and troubleshoot containerized environments, verifying that Docker daemons are running and that volume mounts are correctly configured.

    New in DevOps & Cloud