test-report
Skill0 starsChanged 17 days agoMITView on GitHub
Create a test summary / test execution report from results — pass/fail stats, defect summary, and a go/no-go verdict computed by script (never by guessing). Use when the user needs a test report, daily QA status, or release sign-off summary.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Eleven-M/flowmindtheir own version, first seen Nov 8, 2026
- yasunori0418/skillstheir own version, first seen Jun 27, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- yasunori0418/skills★ 9same name
- Eleven-M/flowmind★ 1same 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- api-testSkill
- automateSkill
- bug-reportSkill
- exploratorySkill
- mobile-testSkill
- test-casesSkill
- test-dataSkill
- test-planSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
All math and the release verdict are computed by a Python script — NEVER calculate percentages or decide go/no-go yourself.
- Very specific: line 35
If the script prints INPUT ERRORS (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Test Report Writer
All math and the release verdict are computed by a Python script — NEVER calculate percentages or decide go/no-go yourself. Follow this workflow EXACTLY.
Workflow (mandatory)
- Collect the numbers from the user: total test cases, passed, failed, blocked, and the list of defects (id, severity, status, title). If numbers are missing, ask for them — do not invent.
- Write the input file
reports/results.json:
{
"project": "MyApp v2.3",
"date": "<today>",
"total": 120, "passed": 100, "failed": 12, "blocked": 3,
"defects": [
{"id": "BUG-101", "severity": "Critical", "status": "Open", "title": "Login crash on timeout"}
],
"notes": "optional context from the tester"
}Severity: Blocker|Critical|Major|Minor|Trivial. Status: Open|Fixed|Deferred.
- Generate the report:
python .claude/skills/test-report/scripts/make_report.py --in reports/results.json --out reports/test-report.md- If the script prints
INPUT ERRORS(e.g. passed+failed+blocked > total), tell the user exactly what is inconsistent and ask for the correct numbers. NEVER silently adjust numbers to make them fit. - The script computes the verdict with fixed rules: open Blocker/Critical → ❌ NOT READY; execution < 90% → ❌; failure rate > 10% or open Major → ⚠️ RELEASE WITH RISK; otherwise ✅ READY. Do not override the verdict; if the user disagrees, they can change the input data.
- Add the human part (this is YOUR job, after the script): edit the generated report to add a 2-3 sentence executive summary at the top, and a "Risks & blockers" section based on what the user told you. Never soften bad news.
- Offer to also produce a polished HTML version (Artifact) for sharing with managers.
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.

