agentleFS
egregore-labsegregore-labs/egregore/.claude/skills/dashboard/SKILL.md

dashboard

Skill293 starsChanged 10 days agoMITView on GitHub

Explicit personal-status surface for /dashboard or a direct request for the whole personal overview. Do not use it to find or resume one specific prior handoff, project, or work thread; that is semantic organizational recall through Runtime/QMD.

67 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use discover, export 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.
  • 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

    organize

    Organize knowledge into Sets

    Also in 3 projects that use this

  • admin-remixSkill

    workspace

    Google Workspace administration - manage users, groups, email, Drive, calendars, and devices through natural conversation. Triggers on: Google Workspace, G Suite, user management, group management, admin tasks, offboarding, onboarding, email forwarding, Drive permissions, suspended users, organizational units, ChromeOS devices, audit logs, admin reports.

    Also in 3 projects that use this

  • bivexSkill

    schedule

    Управление расписанием занятий с специалистами по самосовершенствованию. Используй когда пользователь спрашивает о расписании, хочет добавить/удалить/перенести занятие, посмотреть план на день или неделю.

    Also in 3 projects that use this

  • MetaSkill

    roadmap

    Build, continue, inspect, or visualize a source-grounded mathematical roadmap and theorem DAG in an existing Autoform Markdown blueprint. Use for source research, repository-wide inventories of existing and planned mathematics, scope, coverage, milestones, and roadmap articles; do not create repository infrastructure or prove Lean declarations.

    Also in 3 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 52 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:

    Use this bounded status card only when the user explicitly asks for Dashboard or the whole personal overview.

    line 8
  2. Distinctive:

    Do not sync repositories, query memory again, or call implementation infrastructure directly.

    line 28
  3. Very specific:

    Never print raw JSON or narrate routine commands.

    line 37

“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

Use this bounded status card only when the user explicitly asks for Dashboard or the whole personal overview. A request to return to one earlier piece of work must use attached EGREGORE_ORG_CONTEXT_V1 evidence or exactly one Search workflow query when that evidence is absent. Never use Dashboard as discovery fallback.

Render the personal view immediately. The renderer's stdout IS the product card: it is fully visible the moment rendering finishes, and it must appear exactly once in the conversation. Never copy, regenerate, summarize, or repeat the card — or any of its rows — in your reply; add nothing beyond an answer to something the user separately asked.

Map the requested range to P1D, P7D, P30D, or P365D as {time-range}, then fetch and render exactly one authorized Runtime snapshot:

bash bin/dashboard-data.sh '{time-range}' 2>/dev/null \
  | bash bin/node-run.sh bin/codex-skill-render.mjs dashboard-card -

Do not sync repositories, query memory again, or call implementation infrastructure directly. The snapshot owns actor resolution, authorization, bounds, canonical lifecycle state, and presentation data.

Connected enrichment is separate and explicit. Set EGREGORE_STATUS_CONNECTED_ENRICH=1 only when the user requests projected Connected status. It is capability/permission gated and cannot replace canonical handoffs, questions, quests, todos, sessions, or lifecycle metadata.

Never print raw JSON or narrate routine commands. Preserve the shared 72-column card, omit graph/setup messaging in Local mode, end with What's next?, and act on the reply in the next turn.

When to invoke

Explicit personal-status surface for /dashboard or a direct request for the whole personal overview. Do not use it to find or resume one specific prior handoff, project, or work thread; that is semantic organizational recall through Runtime/QMD.

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.