- Home
- Skills
- Testing & Debugging
- Startup Triage
Works with the AI Agents you already use
Startup Triage
A fresh clone won't run and you don't know why.
$5
Startup Triage
Example session with this skill installed
why won't this project start?
- Read your context and instructions
- Compiled the startup triage
I have triaged the startup failure by checking the toolchain, dependencies, environment, and ports. I found a critical version mismatch that is blocking the build process.
Triage Verdict: Startup Blocked
| Layer | Status | Finding |
|---|---|---|
| Runtime | 🔴 BLOCKING | System is running Node v20.10.0, but .nvmrc requires v18.x. |
| Dependencies | 🟡 Warning | package-lock.json is out of sync with package.json. |
| Environment | 🟢 Ruled Out | All keys from .env.example are present in .env. |
| Ports | 🟢 Ruled Out | Port 3000 is available. |
| Codegen | 🟢 Ruled Out | Next.js artifacts are not yet required for this stage. |
The Fix
The runtime mismatch is preventing the native dependency compilation. Switch your Node version to match the project specification:
nvm use
Note: After fixing the runtime, you will likely need to run npm install to resolve the lockfile drift noted in the warnings.
Next steps
- Run
nvm useto switch to the supported Node version. - Run
npm installto synchronize your lockfile. - Attempt
npm run devagain.
Connects securely to your tools. The creator never sees your data.
About this skill
A fresh clone won't run and you don't know why. Startup Triage detects your stack and walks the startup-failure layers in the order they actually fail, then stops at the first blocking cause — so you get the one thing to fix, with its command, instead of a pile of findings to bisect by hand.
Triages, in order
- Runtime/toolchain version vs the pinned version (
.nvmrc,python_requires,godirective…) — the #1 cause - Dependencies installed and lockfile-consistent
- Required environment variables (from
.env.example/ schema / source refs) — reported by name, never value - Ports already bound, Docker daemon down, unready services
- Missing codegen artifacts (Prisma client, protobuf stubs, compiled assets)
Verdict: 🔴 the one blocker (+ exact fix command) · 🟡 warnings for after · 🟢 ruled-out, so you trust it.
Why this beats a generic env check: it's decisive. It reasons in dependency order and reports the blocking layer first, not every warning at once.
Safe: never prints a secret's value; never runs install/build/startup for you.## Startup Triage
A fresh clone won't run and you don't know why. Startup Triage detects your stack and walks the startup-failure layers in the order they actually fail, then stops at the first blocking cause — so you get the one thing to fix, with its command, instead of a pile of findings to bisect by hand.
Triages, in order
-
Runtime/toolchain version vs the pinned version (
.nvmrc,python_requires,godirective) — the #1 cause -
Dependencies installed and lockfile-consistent
-
Required environment variables (from
.env.example/ schema / source refs) — reported by name, never value -
Ports already bound, Docker daemon down, unready services
-
Missing codegen artifacts (Prisma client, protobuf stubs, compiled assets)
Verdict: 🔴 the one blocker (+ exact fix command) · 🟡 warnings for after · 🟢 ruled-out, so you trust it.
Why this beats a generic env check: it's decisive. It reasons in dependency order and reports the blocking layer first, not every warning at once.
Safe: never prints a secret's value; never runs install/build/startup for you.## Startup Triage
A fresh clone won't run and you don't know why. Startup Triage detects your stack and walks the startup-failure layers in the order they actually fail, then stops at the first blocking cause — so you get the one thing to fix, with its command, instead of a pile of findings to bisect by hand.
Triages, in order
-
Runtime/toolchain version vs the pinned version (
.nvmrc,python_requires,godirective) — the #1 cause -
Dependencies installed and lockfile-consistent
-
Required environment variables (from
.env.example/ schema / source refs) — reported by name, never value -
Ports already bound, Docker daemon down, unready services
-
Missing codegen artifacts (Prisma client, protobuf stubs, compiled assets)
Verdict: 🔴 the one blocker (+ exact fix command) · 🟡 warnings for after · 🟢 ruled-out, so you trust it.
Why this beats a generic env check: it's decisive. It reasons in dependency order and reports the blocking layer first, not every warning at once.
Safe: never prints a secret's value; never runs install/build/startup for you.
Does not execute install or build commands. Does not read or print secret values from environment files. Scope is limited to root-level manifest detection.
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 18 days ago
Requires