agentleFS
Sign inStart free
educlopezeduclopez/mallard/skills/show-me-your-work/SKILL.md

show-me-your-work

Skill4 starsChanged 14 days agoMITView on GitHub

Keep a reviewable decision trail (one TSV row per decision) for long or unattended work. Use when the user says "deja rastro de las decisiones", "show me your work", "registro de decisiones", or for long multi-phase jobs a human reviews later: a knowledge-base rewrite, a theme migration, a bulk translation, a multi-store rollout.

67 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ketchup-video, principle-explain-the-number 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.
  • tristanphvnSkill

    ketchup-video

    Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.

    Also in 14 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 29 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 20 projects that use this

  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 25 projects that use this

  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 14 projects that use this

  • instructureSkill

    ketchup

    Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories

    Also in 25 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 64 edited versions we read keep these.

  • 1

    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:

    Create the header on first use.

    line 32
  2. Very specific:

    Default decisions.tsv in the work directory, kept out of git (.git/info/exclude).

    line 40
  3. Distinctive:

    Check each row maps to a real action and its evidence resolves and shows what the row claims.

    line 44

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

show-me-your-work

Adapted from pstack's show-me-your-work. Only for long tasks. Skip it for anything that fits in one sitting.

Log

One file, one row per decision, append-only, cells on a single line. Evidence is a pointer, never prose.

ts	phase	decision	why	evidence	result
  • ts: ISO 8601. phase: workstream.
  • decision: what was chosen or done, one line.
  • why: the reason in plain words.
  • evidence: commit SHA, file:line, screenshot or artifact path.
  • result: tests green, reverted, open, INCONCLUSIVE.

Create the header on first use. If a cell starts with =, +, - or @, prefix it with ' so spreadsheets do not read it as a formula.

What to log

Forks chosen, units finished with their verification result, pivots and reverts with the trigger, blockers, fixed gates. Skip trivial actions. A wrong call gets a new row that supersedes it; never edit history.

Where it lives

Default decisions.tsv in the work directory, kept out of git (.git/info/exclude). Commit it only when a reviewer needs the trail to trust the result, and only if the user agrees.

Before handing back

Check each row maps to a real action and its evidence resolves and shows what the row claims. Fix or supersede any row that does not.

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