Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

restassured-reporting-stakeholder

Estrelas2

Forks0

Atualizado13 de maio de 2026 às 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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

jovd83

jovd83/restassured-skill

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Especialistas em gestão de projetosNegócios e Operações Financeiras·SOC 13-1082

Explorador de arquivos

2 arquivos

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.

Mais deste repositório

mesmo repositório

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.