agentleFS
Sign inStart free
mehrad-dmmehrad-dm/mastermind/skills/report/SKILL.md

report

Skill23 starsChanged 2 months agoMITView on GitHub

Use when the user asks for a written record of what was done: \"write it up\", \"give me a report\", \"summarize what you changed\", \"document this cycle\": or at the end of a build/QA cycle ONLY if the project's cycle-report preference is on. Off by default: never produce one unprompted, and skip it for a one-line change.

93 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use opportunities, export and 9 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.
  • ansvisorSkill

    opportunities

    Finds content gaps, prompts worth tracking, and the off-site sources AI cites instead of the brand.

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

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 3 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 7 projects that use this

  • tokyubevoxelverseSkill

    checkup

    Give a repository a full health exam — doc rot, dependency staleness, CI decay, git hygiene, dead links, docs contradicting code — and grade it. Use when the user wants to know what quietly rotted, or a prioritized maintenance list.

    Also in 3 projects that use this

  • rajnavakotiSkill

    scan

    Run the AI dashboard scanner and generate the HTML report.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 2

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

    Default is off: otherwise the in-chat verdict is the whole deliverable.

    line 15
  2. Very specific:

    Read .mastermind/prefs.md in the project root for a cycle-report: line: one of:

    line 19
  3. Distinctive:

    Keep it tight: a bloated report gets ignored (same rule as the brain: signal density beats volume).

    line 38
  4. Very specific:

    Markdown (default): write .mastermind/reports/<slug>-<YYYY-MM-DD>.md (use today's date), or a path the user names.

    line 42

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

report: a receipt for the work

Turn a completed cycle into a concise, skimmable record someone can read without re-reading the diff. It's the same content as the in-chat verdict, made durable and shareable.

When it runs

  • On request: "give me a report", "write up what you did", "summarize this cycle".
  • Automatically at the end of build / qa only if the project preference says so (below). Default is off: otherwise the in-chat verdict is the whole deliverable.

Preference (per project): off by default

Read .mastermind/prefs.md in the project root for a cycle-report: line: one of:

  • off (default, and the assumption if the file/key is missing): report only on explicit request.
  • ask: at the end of a report-worthy cycle, offer once: "want a report? markdown / html / no".
  • markdown: always write a Markdown report.
  • html: always write a self-contained HTML report.

The init skill sets this once, at the first task. The user can change it anytime ("reports off", "always give me html reports"): update the line in .mastermind/prefs.md to match.

What goes in it: signal, not a log

  1. Title + verdict: Done · Done, not fully checked · Not done · Wrong thing, one line why, and the not checked: line.
  2. What changed: files touched (path + one-line what), grouped by area.
  3. Key decisions: the non-obvious calls and the one-line reason (not what the model already knows).
  4. How it was verified: what was actually run/observed end-to-end, and what it produced.
  5. Follow-ups / risks: anything left, edge cases, TODOs.

Keep it tight: a bloated report gets ignored (same rule as the brain: signal density beats volume).

Format

  • Markdown (default): write .mastermind/reports/<slug>-<YYYY-MM-DD>.md (use today's date), or a path the user names. Cheap, diffable, opens anywhere.
  • HTML (on request / cycle-report: html): one self-contained file (inline CSS, no external assets or scripts), lightly MasterMind-styled, so it opens in any browser. Costs more tokens.

Tool-agnostic: always a plain file on disk, so it survives whatever tool wrote it.

Cost & restraint

An HTML report adds meaningful output tokens (~1.5–4k) vs Markdown (~0.4–1k); the in-chat verdict is ~free. Match effort to stakes: for a one-line change, skip the report entirely: offer nothing. Reserve it for cycles someone would actually want to read or share.

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