Env Doctor Pro — Why Won't This Repo Start

    1

    Diagnose why a project won't install or boot: toolchain, lockfiles, missing env keys, ports — confirm before every write.

    $29

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Env Doctor Pro — Why Won't This Repo Start

    Example session with this skill installed

    The project won't start. I'm getting a module not found error when I run npm run dev, but I already ran npm install. Here is the log.

    • Read your context and instructions
    • Compiled the env doctor pro

    I have analyzed the startup failure and scanned the local configuration files. It appears there is a mismatch between your installed dependencies and the required Node.js version.

    Env Doctor report

    Symptom: Error: Cannot find module 'lucide-react' during next dev.
    Likely cause: Stale node_modules / Node version mismatch (High confidence).
    Evidence:

    • package.json engines specify node >=20.0.0, but current shell is v18.16.0.
    • package-lock.json was generated with npm v10, current is npm v9.6.7.
    • lucide-react is present in package.json but missing from node_modules/.bin.

    Fix plan

    1. Use nvm use or switch shell to Node v20.0.0. [needs confirm]
    2. Verify .env matches .env.example keys. [read-only]
    3. Run npm install to sync lockfile with node_modules. [needs confirm]
    4. Check if port 3000 is occupied by another process. [read-only]

    Next command

    npm run dev

    Next steps

    • Would you like me to attempt switching the Node version using your version manager?
    • Should I proceed with a clean npm install once the version is corrected?
    • I can also check your .env file for missing keys from the example file.

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

    About this skill

    Stop wasting hours troubleshooting local environment mismatches and cryptic install errors. This skill automates the diagnostic process for projects that refuse to boot, install, or run. It systematically audits Node and Python toolchains, lockfile integrity, missing environment variables, and port conflicts to find exactly why a repo is failing.

    What it does

    • Reproduce failures by capturing exact command signals and exit codes.
    • Scan toolchains to compare runtime versions against .nvmrc, engines, or runtime.txt.
    • Audit lockfiles for mismatches between npm, pnpm, yarn, uv, or poetry.
    • Identify env gaps by checking .env.example keys against active processes.
    • Rank root causes using a failure matrix to assign confidence levels to potential fixes.

    How it works

    1. Symptom Capture: Provide the failing command and error log; the skill extracts the crash signature.
    2. Diagnostic Scan: The agent performs a read-only audit of configuration files and system paths.
    3. Report Generation: You receive a prioritized list of causes with specific evidence from your filesystem.
    4. Fix Approval: The agent proposes a plan, labeling steps as either safe read-only actions or system-altering writes.
    5. Guided Execution: Upon confirmation, the agent applies the fix and verifies the boot sequence.

    Frameworks & tools

    Supports Node.js (npm, pnpm, yarn), Python (venv, poetry, uv), Docker, and standard Unix/Windows shell environments.

    Why this beats prompting it yourself

    Standard prompts often suggest destructive "shotgun" fixes like deleting node_modules or upgrading all packages immediately. This skill enforces a strict scan-order and failure-matrix approach, ensuring the smallest possible change unblocks the project without polluting your global environment.

    Use cases

    • Debugging a legacy repo that fails to install on a new machine.
    • Fixing "module not found" or "wrong node version" errors during onboarding.
    • Resolving port conflicts and missing .env keys in complex microservices.
    • Verifying lockfile integrity after a messy git merge.

    Known limitations

    Does not support automatic Docker Desktop installation or private registry credential management. User must provide project root for monorepos.

    Requires shell access for diagnostics. Does not install Docker or manage private registry credentials. Destructive resets require explicit confirmation.

    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

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Requires

    Python

    Permissions

    No special permissions declared or detected

    Listed27 days ago

    What's inside

    Frequently Asked Questions

    env doctor pro is a diagnostic agent that identifies why local development projects won't install or run by auditing your Node/Python toolchains, lockfiles, and environment variables. Unlike generic prompts, it uses a ranked failure matrix to find the most efficient fix without resorting to destructive 'shotgun' methods.

    The skill fully supports Node.js (npm, yarn, pnpm) and Python (venv, poetry, uv) ecosystems, along with Docker and Unix/Windows shell environments. It is designed for use with any AI agent or platform that has read/write access to your local filesystem and terminal.

    The agent follows a strict 'Scan-Report-Approve' workflow: it first performs a read-only audit and presents a ranked fix plan. It will only apply system-altering changes—such as updating lockfiles or modifying environment variables—after you review and approve specific steps.

    Yes, env doctor pro is effective for monorepos, though you must provide the specific project root or subdirectory for the agent to begin its diagnostic scan. It will then analyze the relevant configuration files (like .nvmrc or pyproject.toml) within that context.

    The skill currently does not support automatic Docker Desktop installation or the management of credentials for private registries (like private npm or PyPI servers). You will need to ensure your machine has the basic runtime installed and necessary registry permissions before the agent can troubleshoot project-level issues.

    New in LLM Ops