e2eexception

Orchestrate end-to-end vulnerability exception workflow tests with MCP-backed stacks.

1|Updated Apr 25, 2025

Search Tags:#testing #vulnerability #e2e #mcp #orchestration #exception

Ready to run

npx skills add https://github.com/schmalle/secman --skill e2eexception

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2eexception
Source: https://github.com/schmalle/secman/tree/main/.claude/skills/e2eexception
Command: npx skills add https://github.com/schmalle/secman --skill e2eexception

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill orchestrates end-to-end vulnerability exception workflow tests to validate the complete exception lifecycle using MCP, including starting services, running tests, and performing iterative fixes until all steps pass.

Core Features & Use Cases

Orchestrates full-stack E2E tests for vulnerability exception workflows across backend and frontend.
Runs the MCP-based test script, monitors health checks, and triggers retry loops with clean start/stop cycles.
Generates structured failure analysis and guided fixes to bring tests to green in bounded iterations.

Quick Start

Start the e2e exception workflow by launching the backend and frontend, running the test script, and iteratively applying fixes until the test passes or the retry budget is exhausted.

Frequently Asked Questions about e2eexception

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate end-to-end vulnerability exception testing with MCP?▼

You can orchestrate end-to-end vulnerability exception tests against an MCP-backed stack by running automated test scripts, monitoring health checks, and applying iterative failure remediation until all steps pass.

What is an E2E vulnerability exception workflow test?▼

An E2E vulnerability exception workflow test validates the complete vulnerability exception lifecycle across backend and frontend services using MCP, ensuring startup, test orchestration, log analysis, and controlled restarts achieve a green result.

How do I handle failing E2e tests and bring them to green automatically?▼

The orchestration script generates structured failure analysis and guided fixes, triggering retry loops with clean start and stop cycles bounded by a retry budget to bring failing E2E tests to green.

Do I need a separate test runner to orchestrate vulnerability exception tests?▼

No, this Skill orchestrates the full test lifecycle internally using scripts, handling service startup, health check monitoring, test execution, and controlled restarts without requiring an external test runner.

What happens when the retry budget is exhausted in E2E test orchestration?▼

When the bounded retry budget is exhausted, the orchestration stops performing iterative remediation and provides structured failure analysis from the test logs, allowing you to manually diagnose remaining vulnerabilities.