agentsclimarketplace
Sign in

Stakeholder

Skill jovd83/Cypress-skill/reporting/stakeholder

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

Install
npx -y skills add jovd83/Cypress-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

  • 0 stars0 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.

SKILL.md

1.7 KB, 203 tokens by cl100k_base, as published. Nobody here has run it

Telemetry & Logging

[!IMPORTANT] All usage of this skill must be logged via the Skill Dispatcher to ensure audit logs and wallboard analytics are accurate: ./log-dispatch.cmd --skill <skill_name> --intent <intent> --model <model_name> --reason <reason> (or ./log-dispatch.sh on Linux)

Stakeholder Execution Report

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

Action

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, flaky, blocked, or environment-constrained.
  • Keep stack traces and low-level logs out of the main report unless the user explicitly wants them.

What ships with it: 1 file

320 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.