agentleFS
perberperber/leafwiki/.claude/skills/run/SKILL.md

run

Skill1.2k starsChanged 18 days agoMITView on GitHub

Launch LeafWiki locally (Go backend + Vite frontend dev server) to manually verify a change in the browser. Use whenever a frontend or backend change needs to be exercised end-to-end instead of just type-checked or unit-tested.

45 other projects use a version of this.

Trending

Less talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 2 mentionsJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the perber/leafwiki repository that our weekly crawl found: only 5 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Used with

Projects with it also use init, report and 6 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

    init

    Also in 4 projects that use this

  • 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

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 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

  • +1 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run make dev in the background (a run_in_background Bash call) and poll http://localhost:5173 / http://localhost:8080 readiness before …

    line 31
  2. Very specific:

    Stop it with pkill -TERM -f scripts/dev.sh: a background job ignores SIGINT, and the script's trap stops both servers on SIGTERM.

    line 33
  3. Distinctive:

    Every image read in the main session stays in its context and is paid for again on every later turn.

    line 36
  4. Very specific:

    Before committing, run npm run format in ui/leafwiki-ui (and in e2e/ if e2e tests changed).

    line 40

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

Running LeafWiki locally

LeafWiki needs two processes running side by side: the Go backend (API + serves data) and the Vite dev server (frontend, proxies /api, /assets, /branding to the backend).

Start

make setup   # first time, or after package-lock.json changed
make dev

make dev builds and starts the backend on http://localhost:8080 and Vite on http://localhost:5173 — open :5173, not :8080, during development. Admin login: username admin, password devpassword (the minimum is 8 characters). --public-access=true lets you view pages without logging in; use the admin login for anything that touches the tree, settings, or editor. Extra backend flags: make dev ARGS=--enable-revision=true. Ctrl-C, or SIGTERM to the script, stops both.

Without make dev: go run . --jwt-secret=dev --admin-password=devpassword --public-access=true --allow-insecure=true in cmd/leafwiki, and npm run dev in ui/leafwiki-ui.

Notes

  • Run make dev in the background (a run_in_background Bash call) and poll http://localhost:5173 / http://localhost:8080 readiness before navigating. Stop it with pkill -TERM -f scripts/dev.sh: a background job ignores SIGINT, and the script's trap stops both servers on SIGTERM.
  • Click-throughs and screenshots belong in a subagent that reports back a short text verdict. Every image read in the main session stays in its context and is paid for again on every later turn.
  • Data is stored on disk under the backend's working directory (cmd/leafwiki) by default — starting fresh creates an empty wiki with just the root page.
  • Before committing, run npm run format in ui/leafwiki-ui (and in e2e/ if e2e tests changed).

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.