report

Generate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./engineering-team/playwright-pro/skills/report/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured, actionable, and token-efficient, giving Claude concrete commands and a clear routing table for report destinations. Its primary weakness is workflow clarity: batch test runs and external publishing steps lack explicit validation checkpoints before results are pushed or posted.

Suggestions

Add an explicit validation checkpoint before publishing — e.g., verify the JSON report parsed successfully and that passed/failed counts are non-zero before pushing to TestRail or posting to Slack.

Include a feedback loop for the outward-facing steps (send -> confirm delivery -> retry on failure), especially for the Slack webhook and TestRail push, since these are hard to reverse once sent.

De-duplicate the test execution between steps 1 and 2: have step 2 parse the JSON already produced in step 1 rather than re-running 'npx playwright test --reporter=json'.

Dimension	Reasoning	Score
Conciseness	The body is efficient with a brief intro and directly executable commands, avoiding explanations of concepts Claude already knows; minor redundancy (e.g., re-running 'npx playwright test --reporter=json' in step 2 after step 1 already produced JSON) keeps it just below the lean anchor.	4 / 5
Actionability	It provides concrete, mostly executable commands (ls, npx playwright, curl) and a filled-in markdown template, but placeholder-laden snippets like the Slack curl with {{passed}} and the delegation 'Invoke /pw:testrail push' leave minor gaps versus fully copy-paste-ready guidance.	4 / 5
Workflow Clarity	Steps 1-5 are clearly sequenced with a routing table, but the workflow involves batch test execution and outward-facing actions (pushing to TestRail, posting to Slack) with no explicit validation/verification checkpoints before publishing, so the batch-operation cap of 3 applies.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clearly labeled sections with no nested references, and at ~120 lines with no bundle files the inlined markdown template is reasonable; it falls just short of the score-5 anchor only because no one-level-deep reference structure is used or signaled.	4 / 5
	Total	15 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and effectively answers both what the skill does and when to use it, with a strong set of natural trigger phrases. Its main limitation is thin capability specificity (a single action) and minor trigger overlap with generic results language.

Dimension	Reasoning	Score
Specificity	The phrase 'Generate test report' names the domain and one concrete action, but offers only a single action with no elaboration of what the report contains or how it is produced, matching the '1-2 concrete actions, not comprehensive' anchor rather than the multi-action score 4.	3 / 5
Completeness	It explicitly states what the skill does ('Generate test report') and gives an explicit 'Use when' clause with concrete trigger phrases, matching the anchor that requires both what and when with concrete triggers.	5 / 5
Trigger Term Quality	It lists six natural phrases users would say ('test report', 'results summary', 'test status', 'show results', 'test dashboard', 'how did tests go'), giving good keyword coverage with synonyms, but a few common variations like 'test results' or 'did the tests pass' are absent, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The test-reporting niche is mostly distinct with specific triggers, but generic phrases like 'show results' and 'results summary' carry minor overlap risk with other results-oriented skills, placing it just below the minimal-conflict anchor.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: engineering-team/playwright-pro/skills/report/SKILL.md
Commit: 19392f7

Reviewed: ~9 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.