Creates summary reports from test results with support for Slack, TestRail, and local dashboards.
Install
mkdir -p .claude/skills/report && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3308" && unzip -o skill.zip -d .claude/skills/report && rm skill.zipInstalls to .claude/skills/report
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Generate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".Key capabilities
- →Extracts test result metadata from JSON
- →Categorizes passed, failed, and flaky tests
- →Integrates with Slack webhooks
- →Generates summary tables for markdown output
- →Calculates total test duration
How it works
Executes standard test runner commands with reporting flags and parses the resulting JSON to format text summaries for common output channels.
Inputs & outputs
When to use report
- →Show test status summary
- →Generate test failure dashboard
- →Analyze test results duration
About this skill
Smart Test Reporting
Generate test reports that plug into the user's existing workflow. Zero new tools.
Steps
1. Run Tests (If Not Already Run)
Check if recent test results exist:
ls -la test-results/ playwright-report/ 2>/dev/null
If no recent results, run tests:
npx playwright test --reporter=json,html,list 2>&1 | tee test-output.log
2. Parse Results
Read the JSON report:
npx playwright test --reporter=json 2> /dev/null
Extract:
- Total tests, passed, failed, skipped, flaky
- Duration per test and total
- Failed test names with error messages
- Flaky tests (passed on retry)
3. Detect Report Destination
Check what's configured and route automatically:
| Check | If found | Action |
|---|---|---|
TESTRAIL_URL env var | TestRail configured | Push results via /pw:testrail push |
SLACK_WEBHOOK_URL env var | Slack configured | Post summary to Slack |
.github/workflows/ | GitHub Actions | Results go to PR comment via artifacts |
playwright-report/ | HTML reporter | Open or serve the report |
| None of the above | Default | Generate markdown report |
4. Generate Report
Markdown Report (Always Generated)
# Test Results — {{date}}
## Summary
- ✅ Passed: {{passed}}
- ❌ Failed: {{failed}}
- ⏭️ Skipped: {{skipped}}
- 🔄 Flaky: {{flaky}}
- ⏱️ Duration: {{duration}}
## Failed Tests
| Test | Error | File |
|---|---|---|
| {{name}} | {{error}} | {{file}}:{{line}} |
## Flaky Tests
| Test | Retries | File |
|---|---|---|
| {{name}} | {{retries}} | {{file}} |
## By Project
| Browser | Passed | Failed | Duration |
|---|---|---|---|
| Chromium | X | Y | Zs |
| Firefox | X | Y | Zs |
| WebKit | X | Y | Zs |
Save to test-reports/{{date}}-report.md.
Slack Summary (If Webhook Configured)
curl -X POST "$SLACK_WEBHOOK_URL" \
-H 'Content-Type: application/json' \
-d '{
"text": "🧪 Test Results: ✅ {{passed}} | ❌ {{failed}} | ⏱️ {{duration}}\n{{failed_details}}"
}'
TestRail Push (If Configured)
Invoke /pw:testrail push with the JSON results.
HTML Report
npx playwright show-report
Or if in CI:
echo "HTML report available at: playwright-report/index.html"
5. Trend Analysis (If Historical Data Exists)
If previous reports exist in test-reports/:
- Compare pass rate over time
- Identify tests that became flaky recently
- Highlight new failures vs. recurring failures
Output
- Summary with pass/fail/skip/flaky counts
- Failed test details with error messages
- Report destination confirmation
- Trend comparison (if historical data available)
- Next action recommendation (fix failures or celebrate green)
When not to use it
- →When testing framework is not Playwright
- →When no existing test artifacts are accessible
Prerequisites
Limitations
- →Limited to the output data format of the underlying test runner
- →Requires pre-configuration of env vars for external notification routing
- →Cannot analyze code coverage beyond raw test success metrics
How it compares
It routes reporting to pre-configured destinations automatically without additional tool dependencies.
Compared to similar skills
report side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| report (this skill) | 1 | 5mo | Review | Beginner |
| qa-tester | 29 | 9mo | No flags | Intermediate |
| qa-expert | 14 | 9mo | Review | Intermediate |
| agent-benchmark-suite | 3 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by alirezarezvani
View all by alirezarezvani →You might also like
qa-tester
svilupp
Browser automation QA testing skill. Systematically tests web applications for functionality, security, and usability issues. Reports findings by severity (CRITICAL/HIGH/MEDIUM/LOW) with immediate alerts for critical failures.
qa-expert
daymade
This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.
agent-benchmark-suite
ruvnet
Agent skill for benchmark-suite - invoke with $agent-benchmark-suite
cicd-diagnostics
dotCMS
Diagnoses DotCMS GitHub Actions failures (PR builds, merge queue, nightly, trunk). Analyzes failed tests, root causes, compares runs. Use for "fails in GitHub", "merge queue failure", "PR build failed", "nightly build issue".
e2e
getsentry
Run E2E tests for Sentry JavaScript SDK test applications
running-performance-tests
jeremylongshore
Execute load testing, stress testing, and performance benchmarking. Use when performing specialized testing. Trigger with phrases like "run load tests", "test performance", or "benchmark the system".