agentsclimarketplace

Report

Skill mehrad-dm/mastermind/skills/report

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.From its SKILL.md

Install
npx -y skills add mehrad-dm/mastermind --skill report

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 20 stars20 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, as published. Nobody here has run it

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: ship / needs-work / redirect, one line why.
  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.

What ships with it: 1 file

4.4 KB alongside SKILL.md

Gives 0 of the 12 instructions most docs writing skills give

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionsin 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • write a concise skimmable record
  • include title and verdict
  • group changed files by area
  • describe verification steps and results
  • list follow-ups and risks
  • update project preferences in prefs file

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 612,213. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.