dashboard
Skill46 starsChanged 26 days agoMITView on GitHub
Build, change or remove a module of the owner's personal web dashboard, push data to it, or dress it in their brand. Use when the owner asks to see something on their dashboard, add a page or a card to it, have a cron post a report there, or put it in their colors, logo or font.
- Commits and pushes
64 other projects use a version of this.
Adopted by
Most recently taken up by
- YardonYan/ui-design-skillstheir own version, first seen Nov 15, 2026
- jasondasuki/agent-timelinestheir own version, first seen Nov 15, 2026
- barkain/madroxtheir own version, first seen Nov 15, 2026
- localixai/tokendoctortheir own version, first seen Nov 15, 2026
- galiprandi/job-seekertheir own version, first seen Nov 14, 2026
- Vulnetix/pix-ai-coding-assistanttheir own version, first seen Nov 12, 2026
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-aiSkillactivity
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
OpenAISkilltelemetry
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
anombyte93Skilldiscover
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
soilmassSkillexport
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
seongjaeryuSkillsave
Complete and save your current thinking to Bindly
Also in 4 projects that use this
seongjaeryuSkillorganize
Organize knowledge into Sets
Also in 3 projects that use this
Other versions64 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 64
- dlt-hub/dlt★ 6.1ksame name
- Zafer-Liu/Data-Analysis-Agent★ 2.6ksame name
- PrimeIntellect-ai/prime-rl★ 2.2ksame name
- suboss87/FDEOps★ 940same name
- SethGammon/Citadel★ 927same name
- egregore-labs/egregore★ 293same name
- hsantanna88/clo-author★ 262same name
- hugosantanna/clo-author★ 262same name
- wellwelwel/lagune★ 216same name
- Aster110/mycc★ 165same name
54 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 repository42 other files it gives its agents.
- skills/setup-my-hermes-dashboard/template/AGENTS.mdAGENTS.md
- audit-safetySkill
- betterSkill
- cleanupSkill
- create-projectSkill
- doneSkill
- dreamSkill
- projectsSkill
- setup-brainSkill
- cloudflareSkill
- code-debugSkill
- codex-imagesSkill
- connect-googleSkill
- connect-instagram-developer-platformSkill
- connect-toolSkill
- connect-vpsSkill
- connect-youtube-developer-platformSkill
- convexSkill
- create-internal-appSkill
- create-landingSkill
- create-softwareSkill
- dev-browserSkill
- grill-meSkill
- initializeSkill
- install-skillsSkill
- lumailSkill
- safe-shipSkill
- setup-cloudflareSkill
- setup-convexSkill
- setup-dev-browserSkill
- setup-githubSkill
- setup-lumailSkill
- setup-my-hermes-dashboardSkill
- setup-nodeSkill
- setup-stripeSkill
- setup-vpsSkill
- show-meSkill
- skill-managerSkill
- stripe-checkoutSkill
- use-styleSkill
- verifySkill
- wait-whatSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 50 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Read ~/projects/dashboard/AGENTS.md first: it has the stack, the recipe to add a module and the rules.
- Very specific: line 23
Commit and push: cd ~/projects/dashboard && git add -A && git commit -m "<module>: <what it shows>" && git push.
- Very specific: line 26
When the owner asks for the dashboard in their own brand ("my colors", "my logo", "my site is acme.com"), follow …
- Very specific: line 34
Never print a key or a token, never publish the dashboard another way than it already is, and never delete the database in …
“Common” is measured: kept by at least 6 in 10 of the 50 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
Dashboard
The owner has a personal web dashboard next to you. Every module on it is one they asked you for; the System monitoring group is built in for admins: Conversations (your latest sessions), Infra (server health, the daily infra-audit cron, fixes sent to your board) and Models (the model you answer with; the owner can switch it there, and connecting a new provider stays with you). The code is in ~/projects/dashboard, a git repository on their GitHub, and it runs as the dashboard service.
- Read
~/projects/dashboard/AGENTS.mdfirst: it has the stack, the recipe to add a module and the rules. Follow the code that is already there. - Build only what the owner asked, as one module (a page, its line in the sidebar, its mark). If the request is vague, pick the most useful small version and say what you chose.
- To see what a Hermes endpoint returns before you use it:
dashboard hermes /api/cron/jobs(sessions, crons, skills, usage, status). - Ship with
dashboard deploy. It typechecks, tests and builds before restarting, and keeps the old version online if anything fails: read the error, fix it, deploy again. - Commit and push:
cd ~/projects/dashboard && git add -A && git commit -m "<module>: <what it shows>" && git push. - Answer the owner in one or two lines: what the module shows and its address (the
urlline ofdashboard status, plus the module path).
When the owner asks for the dashboard in their own brand ("my colors", "my logo", "my site is acme.com"), follow ~/projects/dashboard/BRANDING.md: get the name, logo, main color and font from their site or from them, show what you found, apply it, dashboard deploy, commit and push.
To push data from a cron or a task (a morning report, today's numbers), the module needs a write route (step 5 of the recipe). Then dashboard-cli post /api/v1/<name> '<json>'. If dashboard-cli get /api/v1/whoami says there is no key, run dashboard key once.
Several people may sign in, each with their email and a code (dashboard member list): admins see everything, members see the modules but not System monitoring (Conversations, Infra, Models, the Hermes link), the API keys or the Team page. A module that only admins should see or change uses getViewer() or requireAdmin() from src/server/viewer.ts (see the AGENTS.md). To let someone in: dashboard member add <email> --invite (admin only when the owner says so, in those words); dashboard member remove <email> signs them out at once. Admins can also add and remove members on the Team page (/team). The dashboard has its own sign-in: never put it behind the gate, never add a way in without signing in.
An Infra task on your board (title "Fix: ...") came from the owner pressing "Fix": follow it, never open a port in the firewall, and ask the owner before anything that could cut their access (SSH, firewall, a restart of the server). dashboard-cli get /api/v1/infra gives the last check and audit.
Never print a key or a token, never publish the dashboard another way than it already is, and never delete the database in ~/.local/share/dashboard.
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.

