project-report
Skill2 starsChanged 10 days agoMITView on GitHub
Generate the project's complete status report — a read-only Keelokit page with every stage and its documents (context, gaps, PRD scope and metrics, stack, backlog by wave and by epic), bug bashes and security reviews with their findings, environments, decisions and history — to share with someone or export as a file. Use when the user says "reporte", "reporte completo", "informe de estado", "exportá el estado", "para compartir", "status report", "export", "share the project's status", or presses "Generate the full report" on the dashboard. For day-to-day work, use project-dashboard.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mcmespinaa/scholar-supporttheir own version, first seen Mar 31, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mcmespinaa/scholar-support★ 2same 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.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- template/CLAUDE.mdCLAUDE.md
- build-storySkill
- check-bugbashSkill
- check-healthSkill
- check-securitySkill
- coordinateSkill
- harness-upgradeSkill
- keelokitSkill
- plan-backlogSkill
- plan-intakeSkill
- project-adoptSkill
- project-dashboardSkill
- project-newSkill
- run-localSkill
- ship-releaseSkill
- ship-setupSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Ask once, in one line, what the user wants unless they said it:
≈ “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.
Files
Report — the whole project on one read-only page
The same script as the dashboard, in report mode: everything the repo says about the project, laid
out to read end to end. It has no buttons that prepare requests and no Ask Claude box — it is
for reading, sharing and keeping, not for working (that is /keelokit:project-dashboard).
1. Build
Project root and language as in project-dashboard ([dashboard] lang in .keelokit/state.toml).
python3 "${CLAUDE_PLUGIN_ROOT}/skills/project-dashboard/scripts/dashboard.py" --root <root> --reportwrites .keelokit/out/report.html for the Artifact tool; add --standalone for a complete HTML
file that opens in any browser (--out <file> to choose where).
2. Hand it over
Ask once, in one line, what the user wants unless they said it:
- A page to share → publish
report.htmlas its own Artifact (iconreport, description "<product>'s status on<date>, from the repository.") with nocapabilities, so the owner can share it from the page's Share menu, even by public link. Each report is a new Artifact — a snapshot of that day; the dashboard stays the live page. It contains the product's documents: remind the user of that before they share it outside their team. - A file → generate it with
--standaloneand send the file (the chat's file tool, or its path). It opens offline; links to documents point to the repository on GitHub when there is a remote, otherwise to the files next to it.
Then say in two lines what it covers (the date, the stage, stories done of total, open decisions) and that it doesn't update itself: generate a new one to share a later state.
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.