generate-report
Skill4 starsChanged 7 months agoMITView on GitHub
Assemble structured findings and evidence into a human-readable report
10 other projects use a version of this.
Adopted by
Most recently taken up by
- Cellular-Semantics/claude-skillstheir own version, first seen Oct 13, 2026
- MohamedEssam0-0/claude-skillstheir own version, first seen Oct 11, 2026
- ExplorerFreda/fskillstheir own version, first seen Aug 5, 2026
- maxwell2732/my-submission-formatting-agenttheir own version, first seen Mar 15, 2026
- aiagentwithdhruv/skillstheir own version, first seen Mar 2, 2026
- jackhendon/ecom-feedback-intelligencetheir own version, first seen Feb 28, 2026
Used with
Projects with it also use add-webhook, casualize-names 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.
nickjwellsSkilladd-webhook
Add new Modal webhooks for event-driven execution. Use when user asks to create a webhook, add an endpoint, or set up event triggers.
Also in 3 projects that use this
nickjwellsSkillcasualize-names
Convert formal names to casual versions for cold email personalization - first names, company names, and city names. Use when user asks to casualize names, make names friendly, or prepare lead data for emails.
Also in 3 projects that use this
- +10 more from nickjwells
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- maxwell2732/my-submission-formatting-agent★ 106same name
- nickjwells/skills-workspace★ 28same name
- aiagentwithdhruv/skills★ 16same name
- ExplorerFreda/fskills★ 11same name
- jackhendon/ecom-feedback-intelligence★ 1same name
- Cellular-Semantics/claude-skills★ 0same name
- gu-dsan6725/ai-assisted-coding★ 0same name
- jorgegoco/claude_skills★ 0same name
- MohamedEssam0-0/claude-skills★ 0same name
- phuongdo/claude-skills★ 0same 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 repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- annotate-variantsSkill
- detect-build-normalizeSkill
- ingest-vcfSkill
- nextflow-runnerSkill
- pharmacogenomicsSkill
- polygenic-riskSkill
- prioritize-findingsSkill
- query-variantsSkill
- setup-workstationSkill
- annotate-variantsSkill
- detect-build-normalizeSkill
- generate-reportSkill
- ingest-vcfSkill
- nextflow-runnerSkill
- pharmacogenomicsSkill
- polygenic-riskSkill
- prioritize-findingsSkill
- query-variantsSkill
- setup-workstationSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
4
Distinctive
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 30
Put strong items first, then probabilistic items, then exploratory leads.
- Distinctive: line 36
Do not invent missing evidence.
- Distinctive: line 37
Do not hide ambiguity.
- Distinctive: line 38
If upstream artifacts are missing, stop and state which ones are missing.
“Common” is measured: kept by at least 6 in 10 of the 10 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.
Files
Generate report
Assemble structured findings and evidence into a human-readable report plus machine-readable index. Use after prioritization is finished.
When to use
- findings.json and evidence.jsonl exist
- a human-readable deliverable is required
Do not use when
- upstream analysis is still missing
Expected outputs
report.mdreport.htmlreport-index.json
Goal
Turn structured artifacts into a concise report with a clear evidence ladder.
Procedure
- Load the manifest, summary, findings, and evidence artifacts.
- Group findings by confidence and category.
- Put strong items first, then probabilistic items, then exploratory leads.
- End with limitations and required human review.
- Emit
report.md, optionalreport.html, and a machine-readable report index.
Guardrails
- Do not invent missing evidence.
- Do not hide ambiguity.
- If upstream artifacts are missing, stop and state which ones are missing.
References
See references/README.md for durable notes and scripts/ for deterministic helpers.
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.

