run-app
Skill0 starsChanged 8 months agoMITView on GitHub
Detect the local project type, check for required environment variables, and start or restart the app on localhost. Use when the user wants to run, start, or restart their local app, or invokes /run-app.
- Reads credentials
- Installs packages
12 other projects use a version of this.
Adopted by
Most recently taken up by
- yuri-xyz/skillstheir own version, first seen Nov 8, 2026
- RostislavDugin/postgresustheir own version, first seen Nov 1, 2026
- databasus/databasustheir own version, first seen Nov 1, 2026
- louisbrulenaudet/monorepo-templatetheir own version, first seen Oct 29, 2026
- macro-inc/macrotheir own version, first seen Oct 25, 2026
- andidev30/the-artifacttheir own version, first seen Oct 20, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- databasus/databasus★ 9.3ksame name
- RostislavDugin/postgresus★ 9.3ksame name
- macro-inc/macro★ 6ksame name
- wordpress-mobile/WordPress-Android★ 3.2ksame name
- giulio333/ClaudeLens★ 67same name
- NicholasFlemmer/styx-app★ 31same name
- louisbrulenaudet/monorepo-template★ 19same name
- NodeSpaceAI/nodespace-core★ 8same name
- mavrovde/bookvault★ 2same name
- WtotdeD/agentic-resume-builder★ 2same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- releaseSkill
- fix-englishSkill
- mac-llm-fitSkill
- pushSkill
- repo-metaSkill
- research-apisSkill
- write-user-guideSkill
- write-user-storySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 7 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Read the current directory for project markers to determine the stack:
- Very specific: line 27
If multiple markers exist, prefer docker-compose.yml first, then the primary language marker.
- Very specific: line 33
Look for .env.example, .env.sample, .env.template, or environment documentation in the project.
- Distinctive: line 37
If any required variables are missing or empty, print a clear setup guide:
- Distinctive: line 54
Stop here: if critical variables (like database URLs or required API keys) are missing — do NOT attempt to start the app.
- Very specific: line 59
Check if the port is already in use: lsof -ti:<port>
- Very specific: line 60
If a process is running on that port, kill it: kill -9 $(lsof -ti:<port>)
- Very specific: line 65
If a lock file exists but node_modules / vendor / .venv / target is missing, install first:
- Very specific: line 81
Run the start command in the background using the Bash tool with run_in_background: true.
- Distinctive: line 83
After launching, briefly confirm:
- Very specific: line 93
NEVER expose or log secret values from .env files
- Distinctive: line 94
ALWAYS kill the existing process before starting a new one — do not leave orphan processes
- Very specific: line 95
If docker-compose.yml exists and the user hasn't said otherwise, prefer docker compose up over bare commands
- Distinctive: line 96
If the start command fails, read the error output and suggest a fix rather than silently retrying
- Very specific: line 97
Use the project's own scripts (e.g., npm run dev) rather than inventing custom commands
- Distinctive: line 98
Do NOT modify any project files — this skill only reads and runs
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Run App
Detect the project type, verify environment setup, and start (or restart) the app on localhost.
Process
Step 1 — Detect the project type
Read the current directory for project markers to determine the stack:
| Marker file | Stack | Default start command |
package.json | Node.js | Read scripts.dev or scripts.start from package.json |
requirements.txt / pyproject.toml / setup.py | Python | python manage.py runserver / uvicorn / flask run (infer from deps) |
Gemfile | Ruby / Rails | bundle exec rails server |
go.mod | Go | go run . |
Cargo.toml | Rust | cargo run |
docker-compose.yml | Docker Compose | docker compose up |
Makefile | Check for run/dev/start target | make dev or make run |
If multiple markers exist, prefer docker-compose.yml first, then the primary language marker. If you cannot determine the stack, ASK:
What command do you normally use to start this app?
Step 2 — Check required environment variables
- Look for
.env.example,.env.sample,.env.template, or environment documentation in the project. - Compare with the existing
.envfile (if any). - Also scan the codebase for
process.env.,os.environ,os.Getenv,ENV[or similar patterns to discover required variables.
If any required variables are missing or empty, print a clear setup guide:
⚠️ Missing environment variables:
| Variable | Description | Where to get it |
|-----------------|--------------------------|----------------------------|
| DATABASE_URL | PostgreSQL connection | Your database provider |
| API_KEY | Third-party API key | https://example.com/keys |
Create a `.env` file or copy from the template:
cp .env.example .env
Then fill in the missing values and run /run-app again.Stop here if critical variables (like database URLs or required API keys) are missing — do NOT attempt to start the app.
Step 3 — Kill any existing process on the target port
- Determine the port from:
.env, config files, or default for the framework (e.g., 3000, 8000, 8080, 4000). - Check if the port is already in use:
lsof -ti:<port> - If a process is running on that port, kill it:
kill -9 $(lsof -ti:<port>) - Confirm the port is free before proceeding.
Step 4 — Install dependencies (if needed)
If a lock file exists but node_modules / vendor / .venv / target is missing, install first:
| Lock file | Install command |
package-lock.json | npm install |
yarn.lock | yarn install |
pnpm-lock.yaml | pnpm install |
bun.lockb | bun install |
Gemfile.lock | bundle install |
requirements.txt | pip install -r requirements.txt |
poetry.lock | poetry install |
go.sum | go mod download |
Cargo.lock | cargo build |
Step 5 — Start the app
Run the start command in the background using the Bash tool with run_in_background: true.
After launching, briefly confirm:
✅ App started on http://localhost:<port>
Command: <the command used>
To stop: kill -9 $(lsof -ti:<port>)Rules
- NEVER expose or log secret values from
.envfiles - ALWAYS kill the existing process before starting a new one — do not leave orphan processes
- If
docker-compose.ymlexists and the user hasn't said otherwise, preferdocker compose upover bare commands - If the start command fails, read the error output and suggest a fix rather than silently retrying
- Use the project's own scripts (e.g.,
npm run dev) rather than inventing custom commands - Do NOT modify any project files — this skill only reads and runs
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

