Stakeholder

Skill jovd83/playwright-skill/reporting/stakeholder

End-to-end Playwright skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.

Install

npx -y skills add jovd83/playwright-skill --skill stakeholder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Stakeholder-reporting skill for Playwright execution results. Use when Codex needs to turn raw Playwright runs into a concise, non-technical summary of tested scope, release health, business impact, and recommended next actions.

SKILL.md

1.5 KB, as published. Nobody here has run it

Playwright Stakeholder Reporting

Use this skill when the audience is a product manager, QA lead, or other stakeholder who does not want raw runner noise.

Inputs

Playwright HTML, JSON, or CI reports,
tested scope or release context,
any known blockers, waived failures, or environment qualifiers.

Output Contract

Produce a report with:

Executive summary
Scope covered
Overall outcome
Known issues and business impact
Recommended next actions

Writing Rules

Translate technical failures into business language.
Call out confidence limits if the run was partial or environment-constrained.
Keep stack traces and low-level logs out of the main report unless the user explicitly wants them.