- Home
- Skills
- DevOps & Cloud
- Env Doctor – AI Project Startup & Environment Diagnostic Eng
Works with the AI Agents you already use
Env Doctor – AI Project Startup & Environment Diagnostic Eng
Systematically diagnose software startup failures by auditing runtimes, dependencies, and environment configurations.
$4.99
Env Doctor – AI Project Startup & Environment Diagnostic Eng
Example session with this skill installed
My Node.js project is failing to start with a 'Connection refused' error. Here is my package.json and the error log. What is wrong?
- Read your context and instructions
- Compiled the env doctor
I have analyzed your package.json and the provided log output. The failure occurs during the database initialization phase.
Diagnostic Report
Project and Startup Context
- Project / stack: Node.js / Express / PostgreSQL
- Startup command:
npm run dev - Evidence supplied:
package.json, error log - Checks performed: Dependency check, Environment variable presence, Port availability
Systematic Check Results
| Area | Status | Evidence | Next action |
|---|---|---|---|
| Runtime versions | Pass | Node v20.11.0 matches engines field | None |
| Dependencies | Pass | All packages in package.json are resolved | None |
| Environment variables | Fail | DATABASE_URL is referenced but not found in environment | Define variable |
| Database / services | Fail | ECONNREFUSED 127.0.0.1:5432 | Check if Postgres is running |
| Ports / processes | Pass | Port 3000 is available | None |
Root-cause Assessment
Most likely cause: The application cannot connect to the database because the PostgreSQL service is either not running or the connection string is missing.
- Confidence: High
- Evidence: The log shows
node:internal/errors:491followed by a connection refusal on the default Postgres port. - Safest confirmation: Run
pg_isready -h localhost -p 5432.
Repair Plan
- Verify Database Service: Ensure your local PostgreSQL instance is active.
# For macOS (Homebrew) brew services list # For Linux (systemd) systemctl status postgresql
Configure Environment: Create a .env file in the root directory if it does not exist and add your local connection string.
DATABASE_URL=postgresql://user:password@localhost:5432/dbname
- Retry Startup: Run the dev command again.
npm run dev
Next steps
- Confirm if you are using a local Postgres instance or a Docker container.
- Check if
.envis included in your.gitignoreto prevent secret leakage. - Run
netstat -vanp tcp | grep 5432if the service appears to be running but remains unreachable.
Connects securely to your tools. The creator never sees your data.
About this skill
You try to run a project and it crashes immediately with an opaque error. Env Doctor stops the guesswork by systematically tracing your startup path from runtime versions to port conflicts. It identifies exactly why your application won't boot and provides evidence-based remediation steps.
What it does
- Runtime validation compares project requirements against installed versions of Node.js, Python, Java, Go, Rust, and others.
- Dependency auditing detects missing packages, lockfile drift, and incompatible versions without blindly nuking your node_modules.
- Environment inspection verifies the presence and format of required variables without exposing or logging secret values.
- Service connectivity distinguishes between DNS, network, TLS, and authentication failures for databases and external APIs.
- Artifact checking validates build outputs, generated code, and cache states to ensure the build pipeline is intact.
How it works
- Intake gathers the startup command, error logs, and project manifests to map the failure surface.
- Path reconstruction traces the boot sequence to isolate the first meaningful error from cascading symptoms.
- Hypothesis ranking evaluates potential root causes based on evidence and assigns a confidence level to each.
- Repair planning delivers a safe, ordered list of commands or config changes to resolve the issue.
Frameworks & tools
Works across major ecosystems including Node.js, Python (pip/Poetry), Java (Maven/Gradle), Go, Rust, PHP, Ruby, and .NET. It also supports Docker and containerized environments.
Why this beats prompting it yourself
Generic LLMs often suggest "reinstall everything" or "sudo chmod 777," which wastes time or creates security holes. This skill follows a rigorous diagnostic logic that prioritizes the earliest failure point and prefers reversible, low-risk fixes.
Use cases
- Debugging a "works on my machine" failure when onboarding a new developer.
- Identifying missing environment variables after a major framework or dependency update.
- Resolving port conflicts and service connection issues in complex microservice setups.
- Fixing stale build artifacts or broken native toolchains during local development.
Known limitations
Does not automatically execute system-wide changes or installations. Requires manual input of log data or file contents if the agent lacks direct filesystem access.
Requires user to provide error logs and manifest files. Cannot modify system settings or install packages without explicit authorization. Focuses on startup, not runtime logic bugs.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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 14 days ago