coordination

Coordinate penetration testing engagements from planning through final reporting.

Updated May 27, 2026
One-click install
npx skills add https://github.com/hoanghn61/.agents --skill coordination-hoanghn61
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coordination
Source: https://github.com/hoanghn61/.agents/tree/main/skills/coordination
Command: npx skills add https://github.com/hoanghn61/.agents --skill coordination-hoanghn61

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the chaos of manual penetration testing coordination by standardizing engagement workflow, evidence handling, validation gating, and report-ready output structure.

Core Features & Use Cases

  • 7-phase engagement orchestration (PTES-aligned): drives initialization through reconnaissance, planning, testing, validation, aggregation, and reporting.
  • Parallel executor deployment guidance: ensures vulnerability testing and validation steps run in the intended order with the right “validated-only” constraints.
  • Strict, reusable deliverable structure: enforces a consistent outputs/ layout for data, reports, and logs so results are easy to review and export.
  • Report generation integration: specifies how to generate a branded Transilience PDF report using the transilience-report-style skill and a JSON export.

Quick Start

Use the coordination skill to create an engagement plan and produce a clean outputs/ folder structure aligned with Phase 2 reconnaissance, Phase 4 validation, and Phase 6 final reporting.

Frequently Asked Questions about coordination

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

FAQPage Schema
How do I orchestrate a complete penetration testing engagement from planning to final reporting?

Pentest orchestration coordinates a complete penetration testing engagement across seven phases, from scope initialization and reconnaissance through vulnerability testing, validation, aggregation, and final reporting. It enforces a strict outputs structure for data, reports, and logs.

What is the best way to structure penetration testing outputs for JSON and human-readable report artifacts?

To structure penetration testing outputs, enforce a consistent outputs directory layout separating data, reports, and logs. This structure supports generating a JSON export at outputs/data/pentest-report.json and a human-readable markdown source at outputs/reports/pentest-report-source.md.

How does evidence validation work during pentest vulnerability testing?

Evidence validation enforces validation-only findings and evidence-first traceability during vulnerability testing. This ensures that parallel executor deployment runs specific skills in the intended order with strict validated-only constraints before aggregation.

Can I generate a branded PDF report from pentest JSON export data?

Yes, you can generate a branded Transilience PDF report by integrating the transilience-report-style skill. It uses the JSON export and markdown source files from the outputs directory to produce the final PDF artifact.

Do I need parallel executors for reconnaissance and vulnerability testing in a security assessment workflow?

Parallel executors are recommended for security assessment workflows to run Phase 2 reconnaissance and Phase 4 vulnerability testing concurrently. This ensures specific skills execute in the intended order while maintaining validated-only constraints.

What phases does PTES-aligned penetration testing workflow orchestration include?

PTES-aligned penetration testing workflow orchestration includes seven phases: initialization, reconnaissance, planning, testing, validation, aggregation, and reporting. Each phase maintains strict evidence-first traceability and standardized deliverable structures.