- Home
- Skills
- DevOps & Cloud
- Portready: localhost up and answering before you look
More screenshots
Works with the AI Agents you already use
Portready: localhost up and answering before you look
Checks the port, starts the container runtime and database, then waits until the dev server answers before opening the browser. A pasted error gets an environment check before any code change.
$9
Portready: localhost up and answering before you look
Example session with this skill installed
Portready: pull the latest on shop-web and run it on port 3020. Last time the page said "Failed to fetch".
- Read your context and instructions
- Compiled the portready
Port 3020 was held by a stale next dev from yesterday (PID 48211). Killed that PID only; your other project on 3000 is untouched.
Sync (receive-only)
git fetch·git stash·git merge --ff-only origin/main·git stash pop --index- 4 new commits, 1 new migration (
20261018_add_orders_index.sql). Not applied: say "migrate" and I will run it with the seed.
Dependencies
- OrbStack running
supabase starton the ports insupabase/config.toml(API 54421, DB 54422).env.localfilled from the CLI output (values not shown here)
Earlier "Failed to fetch": environment, not code
.env.localstill pointed at the hosted project, which is paused. Switched it to the local stack.- Re-checked:
curl -sf http://localhost:3020/api/healthreturns 200.
App
PORT=3020 pnpm devstarted in the background with absolute pathsuntil curl -sf -o /dev/null http://localhost:3020; do sleep 1; doneanswered after 6 s, then the browser opened
Ready: http://localhost:3020 · port 3020 · stop with supabase stop and Ctrl+C on the dev process
Recorded in notes/dev.md: port 3020, start command, paused-DB gotcha.
Next steps
- Say "migrate" to apply the 1 new migration and seed demo data.
- Unpause or move the hosted DB if you need production data locally.
- Say "down" at session end and I will stop the dev server and the Supabase stack.
Connects securely to your tools. The creator never sees your data.
About this skill
You asked your agent to start the app, the browser opened on a blank page, and the server was not even listening yet. Or port 3000 was already taken by another project, the local database was down, and an hour went into chasing a code bug that was really an environment fault.
Portready brings a project up on localhost in a fixed order and only opens the browser once the app has answered a real request.
What it does
- Port check first runs
lsofon the target port and kills only the specific stale PID, never a broad kill that hits other projects. Ports come from one registry file so two projects never share 3000. - Dependencies before the app starts the container runtime, then local Supabase or a Postgres/MySQL container, fills
.env.localfrom CLI output, and keeps DB URLs and keys out of chat. - Wait, then open loops
curluntil the port answers, then opens the browser. - Environment before code probes paused hosted databases, refused DB ports, auth gates, stale service workers and port clashes before forming any code hypothesis.
- Slow machine cleanup measures memory, swap and listening ports, asks what to keep, stops the rest, then reports before and after with re-enable notes.
How it works
- Check the port and the registry.
- Sync a receive-only repo with a fast-forward merge, no edits or push.
- Start dependencies, then the app by stack, passing the port by
PORTenv. - Wait for an answer, open the browser, record URL, port and stop command in notes.
- Down at session end: stop everything the session started.
Frameworks & tools
Uses lsof, curl, git, the Supabase CLI and a container runtime (OrbStack, Docker Desktop or Colima). Covers pnpm dev, npm run dev, php artisan serve and vite. Optional cloudflared quick tunnel for demos.
Why this beats prompting it yourself
A plain prompt starts the server and opens the browser in one breath. Portready gates the browser on a live response, and treats a pasted error as an environment question first, so you stop fixing code that was never broken.
Use cases
- Start of session "start it on localhost" or "run it on port 3020".
- Pasted console error such as
Failed to fetch. - Laptop running hot during dev or before an e2e run.
- Pull latest and run an upstream repo for a demo.
Known limitations
Not for production deploys. A bug already isolated to one function should go straight to debugging. Migrations and seeds on a receive-only repo run only when you say so.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed 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 scanned
Verified clean 1 day ago
- Passed all security checks, Safe to install
Requires