Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

restassured-reporting-stakeholder

Sterne2

Forks0

Aktualisiert13. Mai 2026 um 06:22

Use when Codex needs to summarize Rest Assured API test execution for non-technical stakeholders in clear business terms instead of raw test runner output.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

jovd83

jovd83/restassured-skill

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

ProjektmanagementspezialistenWirtschafts- und Finanzberufe·SOC 13-1082

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	restassured-reporting-stakeholder
description	Use when Codex needs to summarize Rest Assured API test execution for non-technical stakeholders in clear business terms instead of raw test runner output.
metadata	{"author":"jovd83","version":"1.0","dispatcher-category":"testing","dispatcher-capabilities":"stakeholder-reporting, api-stakeholder-reporting","dispatcher-accepted-intents":"summarize_api_test_results","dispatcher-input-artifacts":"execution_results, tested_scope, release_context","dispatcher-output-artifacts":"stakeholder_summary, release_health_report","dispatcher-stack-tags":"restassured, reporting, stakeholder","dispatcher-risk":"low","dispatcher-writes-files":false}

Stakeholder Reporting

1. Summarize Business Impact

State what feature area was tested.
State the overall result.
State the user or business impact of failures.

2. Avoid Low-Signal Detail

Do not dump stack traces.
Do not list raw JSON payloads unless necessary.
Translate technical failures into business-readable risk.

3. Include Next Actions

State whether release scope is blocked, degraded, or acceptable.
State the next owner and next action when known.

Mehr aus diesem Repository

gleiches Repository

restassured-skill

jovd83/restassured-skill

Use when Codex needs to design, implement, run, document, or report Rest Assured API tests for REST services, contract-driven service tests, JUnit 5 automation, CI pipelines, or test-management integrations.

2026-05-132

restassured-analysis-contracts

jovd83/restassured-skill

Use when Codex needs to derive Rest Assured test scenarios from OpenAPI or Swagger contracts, including endpoints, methods, schemas, auth rules, status codes, and error conditions.

2026-05-132

restassured-analysis-contracts-soap

jovd83/restassured-skill

Use when Codex needs to derive service-test scenarios from WSDL or SOAP contracts and translate them into HTTP and XML checks that can still be implemented with Rest Assured where appropriate.

2026-05-132

restassured-analysis-requirements

jovd83/restassured-skill

Use when Codex needs to extract testable API behavior from epics, user stories, acceptance criteria, tickets, markdown docs, or other prose requirements before generating Rest Assured scenarios.

2026-05-132

restassured-bootstrap

jovd83/restassured-skill

Use when Codex needs to scaffold, retrofit, or normalize a Java Rest Assured test module with JUnit 5, Maven or Gradle, shared specifications, and an initial runnable smoke test.

2026-05-132

restassured-ci

jovd83/restassured-skill

Use when Codex needs to configure or troubleshoot Rest Assured API tests in CI pipelines, including JUnit 5 execution, tags, Docker, containers, artifacts, quality gates, and provider-specific pipeline examples.

2026-05-132

name	restassured-reporting-stakeholder
description	Use when Codex needs to summarize Rest Assured API test execution for non-technical stakeholders in clear business terms instead of raw test runner output.
metadata	{"author":"jovd83","version":"1.0","dispatcher-category":"testing","dispatcher-capabilities":"stakeholder-reporting, api-stakeholder-reporting","dispatcher-accepted-intents":"summarize_api_test_results","dispatcher-input-artifacts":"execution_results, tested_scope, release_context","dispatcher-output-artifacts":"stakeholder_summary, release_health_report","dispatcher-stack-tags":"restassured, reporting, stakeholder","dispatcher-risk":"low","dispatcher-writes-files":false}

Stakeholder Reporting

1. Summarize Business Impact

State what feature area was tested.
State the overall result.
State the user or business impact of failures.

2. Avoid Low-Signal Detail

Do not dump stack traces.
Do not list raw JSON payloads unless necessary.
Translate technical failures into business-readable risk.

3. Include Next Actions

State whether release scope is blocked, degraded, or acceptable.
State the next owner and next action when known.