Test Reporting Agent Skill

Use this skill when you need to generate test reports with summary, metrics, defect analysis, and risk assessment; triggers include test reporting and QA status report.

8k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

144

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/naodeng/awesome-qa-skills --skill test-reporting

What comes with it

30 860 bytes besides the instruction

README.md

agents/openai.yaml

evals/cases/basic-success.yaml

evals/cases/edge-incomplete-input.yaml

evals/cases/edge-risk-priority.yaml

evals/eval.yaml

output-formats.md

output-templates/template-csv.csv

output-templates/template-excel.tsv

output-templates/template-json.json

output-templates/template-markdown.md

output-templates/template-word.md

output-templates/template-xmind.md

prompts/test-reporting.md

scripts/batch_convert_templates.py

scripts/convert_formats.py

scripts/convert_output_formats.py

scripts/convert_to_csv.py

scripts/convert_to_excel.py

scripts/convert_to_json.py

scripts/convert_to_markdown.py

scripts/convert_to_word.py

scripts/convert_to_xmind.py

scripts/parse_csv.py

scripts/parse_excel.py

scripts/parse_formats.py

scripts/parse_json.py

scripts/parse_markdown.py

scripts/parse_output_formats.py

scripts/parse_word.py

scripts/parse_xmind.py

The instruction itself

7 sections, as written by the author

Test Reporting

中文版： See the corresponding Chinese skill.

When to Use

Need help with test reporting in a real project context.
Need an output that can be used directly for execution, review, or follow-up.

Workflow

Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
Default to Markdown; switch formats only when the user asks.

Core Constraints

Prioritize by risk / business impact — do not treat everything equally.
Separate confirmed facts from current assumptions.
Do not invent endpoints, fields, environments, or root causes the user did not provide.
Keep output executable: concrete scenarios, clear priority, clear next steps.

Progressive Disclosure

Before producing output, read and follow prompts/test-reporting.md (minimum coverage, output structure, quality bar).
When Excel/CSV/JSON/Word is requested: read output-formats.md and honor the format.
When a ready-made template fits: use matching files under output-templates/.
For format conversion or helper checks: prefer existing scripts/ over reinventing.
For evaluating/regressing this skill: use evals/ with skill-up.

Pre-delivery Checklist

[ ] Followed the main prompt's output structure
[ ] Minimum coverage focus: scope tested, scope not tested, overall status, critical defects or blockers, risk summary, coverage confidence, environment or data issues, recommended release position, ... (details in main prompt)
[ ] Covered the minimum checklist, or explained omissions
[ ] High-risk items have explicit priority
[ ] Did not invent details the user did not provide
[ ] Assumptions and gaps are marked

Common Pitfalls

Do not pretend completeness when scope/context is missing.
Do not treat every item as equally important.
Do not skip assumptions and information gaps.
Do not dump generic theory unrelated to the current toolchain.

Other skills for the same job

different authors, same section of the catalogue

Seaborn

by ComeOnOliver

×3

Statistical visualization. Scatter, box, violin, heatmaps, pair plots, regression, correlation matrices, KDE, faceted plots, for exploratory analysis and publication figures.

Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.

2k tokens

Dbt Transformation Patterns

by ComeOnOliver

×1

Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or implementing analytics engineering best practices.

6k tokens

Dbt Transformation Patterns

by ComeOnOliver

×1

7k tokens

Keeper Stress Analysis

by ClickHouse

vendor

Analyze ClickHouse Keeper stress-test results from play.clickhouse.com / keeper_stress_tests data warehouse. Use whenever the user asks about Keeper performance, validates Keeper PRs against stress dashboards, investigates regressions or improvements in Keeper nightlies, asks about specific date windows / SHAs / PR-sets in Keeper stress tests, wants per-PR or window-vs-window comparisons, asks "did this PR break Keeper", asks "what changed in Keeper between dates", or wants a summary report of Keeper stress runs. Triggers on terms like "keeper stress", "keeper PR", "keeper p99", "keeper memory", "keeper rps", "keeper nightly", "keeper-stress-tests", "keeper validation", "keeper regression", or any question referencing the keeper-stress Grafana dashboard. ALWAYS prefer this skill over re-deriving the workflow from scratch — it captures hard-learned lessons about cgroup-vs-Keeper memory, bench-harness confounds, noise floors, and per-PR attribution limits.

40k tokens scripts

Dbt Transformation Patterns

Guide for writing tests for the Aspire Dashboard. Use this when asked to create, modify, or debug dashboard unit tests or Blazor component tests.

4k tokens

Canvas2d Data Visualization

by openai

vendor

Render data visualizations with Canvas2D. Use when the visualization needs high mark counts, fast redraws, immediate-mode rendering, custom hit testing, or a hybrid Canvas plus SVG or HTML architecture.

10k tokens

How to use it

Copy the folder

Take naodeng/test-reporting from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.