agentleFS
Sign inStart free
izoredizored/Audhd-summary/progress-board/SKILL.md

progress-board

Skill0 starsChanged 3 months agoMITView on GitHub

Render a visual, AuDHD-friendly status board of the current session or project — what's done, what's broken, what's waiting on the user, what's next. Use when the user says "progress board", "status board", "show me progress", "visual report", "where are we", or invokes /progress-board.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. mongdang/girok★ 2same name
    2. LetermeFlorent/claude-skills★ 0same name

    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.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

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

    test suite result if one exists (count, pass/fail)

    line 16
  2. Very specific:

    If the mcp__visualize__show_widget tool is available: call mcp__visualize__read_me first (silently, modules: mockup), then build ONE HTML …

    line 22
  3. Very specific:

    If the visualize tools are NOT available: same structure as markdown — a stats line, then one ### section per group with checkbox lists (- …

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Progress board

Render the current state of work as ONE visual widget the user can scan in seconds. The user is AuDHD: grouping, color, counts, and short rows beat prose. Never deliver this report as paragraphs.

Gather (before rendering)

Pull real state — never invent numbers:

  • git log --oneline for recent commits (short hashes go on the rows)
  • test suite result if one exists (count, pass/fail)
  • the conversation itself: what was found, fixed, deferred, decided
  • any plans/TODO index in the repo (e.g. .claude/plans/README.md, TASKS.md)

Render

If the mcp__visualize__show_widget tool is available: call mcp__visualize__read_me first (silently, modules: mockup), then build ONE HTML widget with this structure:

  1. Metric cards row (2–4 cards): version, commits, tests green, items fixed/open. Big number, muted 13px label.
  2. One card per section, each with a header row: Tabler icon + title + right-aligned count pill ("N of M fixed" / "N open"). Sections in this order, skip empty ones:
    • Done / fixed — green (--text-success, --bg-success), ti-check rows, commit hash right-aligned in <code> when known
    • Waiting on user — amber (--text-warning), 2px solid var(--border-warning) card border, ti-square checkbox rows
    • Blocked / broken — red (--text-danger), ti-alert-triangle
    • Next options — blue (--text-accent), each row gets a small sendPrompt('...') button ("Start ↗") so one click kicks off the work
  3. Style rules: CSS variables only (dark-mode safe), flat, no emoji (Tabler outline icons), sentence case, one line per row (≤12 words), 14px rows.

If the visualize tools are NOT available: same structure as markdown — a stats line, then one ### section per group with checkbox lists (- [x] done, - [ ] waiting) and counts in the headers. Still no prose paragraphs.

After the widget

One or two sentences max below the widget: what the colors mean and the single most important next action. Do not repeat the board's content in text.

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.

Check your setup, free