agentleFS
onelastcommitonelastcommit/noctra/.claude/skills/dashboard/SKILL.md

dashboard

Skill4 starsChanged 29 days agoMITView on GitHub

Use when changing the operations dashboard (internal/dashboard) — its Preact + TypeScript UI under web/, the esbuild bundle committed to static/, auth tokens, or the local dev server.

60 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

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

  • 0

    Common

    Most of the 46 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Commit the regenerated internal/dashboard/static/ with the source change.

    line 18
  2. Very specific:

    Keep ports faithful: the live index.html in git history is the source of truth for exact visuals and derivations.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 46 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 frontend (Preact + esbuild)

The UI is a Preact + TypeScript project under internal/dashboard/web/ (src/components/ = one component per panel: KPIs, active runs, queue, run history, donut, token/cost, spend, runs-by-repo, throughput, budget, repo cards, sweep matrix, log overlay), bundled with esbuild (web/build.mjs, ~3 deps, no Vite). It builds into a single self-contained index.html committed to internal/dashboard/static/, which dashboard.go serves via //go:embed static.

After changing anything under web/

cd internal/dashboard/web
yarn install --frozen-lockfile   # first time / after dependency changes
yarn build                       # type-checks, then writes internal/dashboard/static/index.html (+ fonts/)

Commit the regenerated internal/dashboard/static/ with the source change. The dashboard-bundle CI job runs yarn build and fails when the committed static/ differs from a fresh build — it guards, it doesn't regenerate.

  • yarn dev (web/devserver.mjs): esbuild watch + a mock /api (sample data + SSE) at http://localhost:8080/?token=dev&admin_token=dev. Builds to a gitignored web/.dev/, so it never dirties static/.
  • yarn watch rebuilds static/ on change, for testing against the real backend. //go:embed bakes static/ in at compile time, so rebuild the Go binary to see UI edits.
  • Keep ports faithful: the live index.html in git history is the source of truth for exact visuals and derivations.

Why one inlined file

The page sits behind a read token, and @font-face/<script>/<link> subrequests don't carry the page's ?token= query param. build.mjs inlines all JS + CSS into the HTML so the only subresource is fonts, which stay unauthenticated (mux.Handle("/fonts/", …)). Keep the build emitting one file: separate /assets/*.js|css chunks would hit the token gate, 401, and the page would silently fail to boot. Fonts live in web/public/fonts/ (source of truth), are copied to static/fonts/ at build, and are referenced by the absolute /fonts/ URL (external: ['/fonts/*'] in build.mjs).

Why the build output is committed

go build ./... embeds static/, so it must hold real files to compile, and dashboard_test.go serves the page under go test ./... with no Node. Building only in CI would put a Node step in front of every go build/go test. Committing the output keeps tag-on-merge.yml → GoReleaser and the Dockerfile pure Go. static/index.html is marked linguist-generated in .gitattributes so its minified diff collapses; web/node_modules/ is gitignored.

Auth

DASHBOARD_TOKEN gates the page (?token=). DASHBOARD_ADMIN_TOKEN unlocks operator controls (kill / requeue / retry / pause / POST /api/sweep); it travels only in a request header, never the query string.

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.