agentleFS
matt82198matt82198/aesop/skills/dashboard/SKILL.md

dashboard

Skill2 starsChanged 31 days agoMITView on GitHub

Launch the aesop web dashboard — idempotent health check, background serve, browser open, and optional stop.

66 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use activity, telemetry and 10 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.
  • gokite-aiSkill

    activity

    View transaction history and recent account activity. Invoke when the user asks about past spending, wants to verify a payment went through, check if an order completed, review wallet transfers, or see a log of all account actions. Covers wallet transfers, faucet drops, API payments, shopping checkouts, agent registrations, and session approvals.

    Also in 3 projects that use this

  • OpenAISkill

    telemetry

    Add and verify lightweight macOS runtime telemetry. Use when wiring Logger events or inspecting logs for windows, sidebars, menus, and actions.

    Also in 3 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 7 projects that use this

  • soilmassSkill

    export

    Animation export configurations including format selection, resolution, framerate, quality, and optimization settings. Use when rendering animations for web, mobile, video, or social media. Provides tokens for all export parameters across Lottie, GIF, video, and sprite sheet formats.

    Also in 4 projects that use this

  • seongjaeryuSkill

    save

    Complete and save your current thinking to Bindly

    Also in 4 projects that use this

  • seongjaeryuSkill

    organize

    Organize knowledge into Sets

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 52 edited versions we read keep these.

  • 2

    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. Distinctive:

    If 200: dashboard already running → report URL + "Already running" + skip to step 4.

    line 20
  2. Distinctive:

    If non-200 or connection refused: proceed to step 2.

    line 21
  3. Very specific:

    Use curl --retry to poll until :8770 responds with 200:

    line 34
  4. Very specific:

    If invoked with argument stop:

    line 62
  5. Very specific:

    No blocking sleeps: curl --retry-delay 1 gives server time without busy-wait.

    line 81

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

/dashboard — Launch the aesop web dashboard

Idempotent dashboard launch: check if already running on :8770, start if needed (background process), open browser, report URL + task id. Optional stop argument to kill the server.

Model: Haiku (read-only + light operations)

Behavior

1. Check dashboard health (no startup on this call)

curl -s -o /dev/null -w '%{http_code}' http://localhost:8770/
  • If 200: dashboard already running → report URL + "Already running" + skip to step 4.
  • If non-200 or connection refused: proceed to step 2.

2. Start the dashboard server (background)

From the aesop repo root, launch via Bash run_in_background: true:

python ui/serve.py

Environment override (optional):

  • PORT=<port> — defaults to 8770 if unset.
  • Config precedence: PORT env var > aesop.config.json > default 8770

3. Poll for readiness (no blocking sleeps)

Use curl --retry to poll until :8770 responds with 200:

curl -s --retry 20 --retry-delay 1 --retry-connrefused http://localhost:8770/

Expect 200 — then proceed.

4. Open browser (Windows)

start http://localhost:8770

5. Report

Output one summary line with:

  • Dashboard URL: http://localhost:8770
  • Status: "Running" or "Already running"
  • Background task id (if just started)
  • Data freshness: hit /api/state for one-line status (e.g., "heartbeat: 5s old")

Example:

Dashboard: http://localhost:8770 | Running (task: bg-1234) | heartbeat: 5s old

Optional: stop argument

If invoked with argument stop:

# Find the port-holder PID
netstat -ano | findstr :8770

# Kill by PID
taskkill /PID <pid> /F

# Verify port freed (expect connection refused / non-200)
curl -s -o /dev/null -w '%{http_code}' http://localhost:8770/

Report: "Dashboard stopped" + port verification.


Implementation notes

  • Idempotent: repeat calls when server is up → no-op start, just open.
  • No blocking sleeps: curl --retry-delay 1 gives server time without busy-wait.
  • ThreadingHTTPServer required: the Python backend uses one thread per SSE client (Server-Sent Events).
  • Token file: state/.ui-session-token (regenerated if missing, 0600).
  • Config: PORT from env or aesop.config.json (query ui/config.py for precedence).
  • Repo-relative: python ui/serve.py assumes cwd is the aesop repo root.

Related

  • serve.py location: ui/serve.py (repo-relative)
  • Config precedence: env PORT > aesop.config.json > default 8770
  • API routes: /api/state, /api/wave/prs, /api/cost, /events (SSE).
  • Dashboard docs: ui/CLAUDE.md

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.