agentleFS
FAHTHIZFAHTHIZ/oasis/skills/run/SKILL.md

run

Skill4 starsChanged 9 days agoApache-2.0View on GitHub

Launch and drive the project's app to see a change actually working, not only passing tests. Use after implementing a user-visible change.

  • Installs packages

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use report, doctor and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 3 projects that use this

  • MicrosoftSkill

    doctor

    Diagnose an Amplifier CLI environment through the CLI doctor agent. USE WHEN a user requests CLI runtime, settings or missing-capability inspection. DO NOT USE for project bugs or other hosts.

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 5 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start long-running servers in the background (background shell / Monitor) and wait until the log shows it is ready (a port line or "ready" …

    line 13
  2. Distinctive:

    Stop every process you started.

    line 21
  3. Very specific:

    If launching needs steps you had to discover, offer to save them as a project skill (.claude/skills/run-<project>/SKILL.md) so the next run …

    line 24

“Common” is measured: kept by at least 6 in 10 of the 45 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run the app and see the change

  1. Find how the project starts: a project skill or CLAUDE.md/AGENTS.md notes first, then package.json scripts, Makefile, Procfile, docker-compose.yml, manage.py, cargo run, README "Getting started". Prefer the documented dev command.
  2. Install only what the lockfile already declares (npm ci, pip install -r, ...). Ask before installing anything new or touching global state.
  3. Start long-running servers in the background (background shell / Monitor) and wait until the log shows it is ready (a port line or "ready" message) instead of sleeping blindly.
  4. Drive the change the way a user would:
    • Web apps: open the page with the browser tool, click through the changed flow, read the console for errors, take a screenshot of the result.
    • APIs: call the changed endpoints with curl and show status codes and bodies.
    • CLIs: run the command with realistic arguments, including one failure case.
  5. Compare what you saw with what the change should do. If it is wrong, fix it and drive it again.
  6. Stop every process you started. Report the exact commands, what you observed, and anything you could not check (missing credentials, devices, external services).

If launching needs steps you had to discover, offer to save them as a project skill (.claude/skills/run-<project>/SKILL.md) so the next run is one step.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.