report
Skill0 starsChanged yesterdayMITView on GitHub
Use only when the user explicitly invokes /report - "what do we have now", "what is the result", "give a summary of what is done", "what improved this week", "clear statistics are needed", "write what was done, not the commits", "write it all as text".
100 other projects use a version of this.
Adopted by
Most recently taken up by
- SuresoftTechnologies/statica-plugintheir own version, first seen Nov 15, 2026
- XORwell/archeflowtheir own version, first seen Nov 15, 2026
- FYClamityDestiny/vettedtheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- matthewdonsemail-lab/logtheir own version, first seen Nov 15, 2026
- automagik-si/genietheir own version, first seen Nov 15, 2026
Used with
Projects with it also use opportunities, export 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.
ansvisorSkillopportunities
Finds content gaps, prompts worth tracking, and the off-site sources AI cites instead of the brand.
Also in 3 projects that use this
soilmassSkillexport
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
GoogleSkillquality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
Also in 3 projects that use this
genomewalkerSkillresume
Resume a thread by loading its ~800-token context capsule
Also in 7 projects that use this
tokyubevoxelverseSkillcheckup
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
rajnavakotiSkillscan
Run the AI dashboard scanner and generate the HTML report.
Also in 5 projects that use this
Other versions100 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 100
- microsoft/data-formulator★ 17ksame name
- Zafer-Liu/Data-Analysis-Agent★ 2.6ksame name
- H-mmer/pentest-agents★ 815same name
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
- cwinvestments/memstack★ 425same name
- automagik-si/genie★ 353same name
- automagik-dev/genie★ 351same name
- namastexlabs/automagik-genie★ 351same name
- ansvisor/ansvisor★ 233same name
- andrew-yangy/gru-ai★ 153same name
90 more not listed
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.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- global/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-qualitySkill
- blockersSkill
- changesSkill
- codex-orchestrationSkill
- context-resumeSkill
- copy-checkSkill
- debug-profileSkill
- evidence-researchSkill
- healthSkill
- project-initSkill
- relaySkill
- shipSkill
- spec-analyzeSkill
- spec-auditSkill
- spec-dispatchSkill
- spec-nextSkill
- spec-planSkill
- ui-checkSkill
- work-statusSkill
The file
Files
report: a summary for the user
Argument (optional): a period ("for a week", "since 1 October") or a topic ("call scoring"). By default, the last 7 days of this project. The reader is the user.
The report only reads. Files do not change unless the user asked to save the report.
Sources
git logfor the period: group by the result for the product's user, do not retell commits.- The change archive for the period (
solo-sdd/changes/archive), theirverification.md. docs/status.md,docs/waiting.md,README.md.- Project metrics: logs, the database, dashboards, reports. Read only and only free requests.
Form (in the user's language, as plain text)
- Result: 2-3 sentences: where the project is now and what mattered most in the period.
- What was done, by result: what the product can do now or what got better.
- Numbers: a table. Every number has a source, a date or period and a status: confirmed | from an old record | not checked. A "was → became" comparison, if there is something to compare with. The table always has two rows: archived changes (the
solo-sdd/changes/archivefolders of the period) andlight:commits (git log --oneline --grep='^light:' --since=<period start>), each counted apart. - What is broken or at risk.
- What waits, from
docs/waiting.md: what, from whom, since when. - What next: 1-3 items.
What is not in the sources, do not make up: write "no data" and where to get it.
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
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.