Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hypnguyen1209/engagement-flow
Use when starting, planning, or running a multi-phase pentest or red-team engagement — to sequence the Cyber Kill Chain phases with quality gates instead of jumping straight to exploitation
Passed 19 of 22 test cases with the skill, and 7 of 22 without it.
and 18 more in the full report
12 fixed7 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are logging a potential remote code execution finding against host appserver.internal. A team member included a description and screenshot but omitted formal industry classifications. List the exact four metadata elements required for a finding before passing a gate.
| Checked | Without skill | With skill |
|---|---|---|
| Requires CWE classification for every finding. | Passed | Passed |
| Requires CVSS score for every finding. | Passed | Passed |
| Requires MITRE ATT&CK mapping and supporting evidence for every finding. | Missed | Passed |
The instructions your model reads when the skill loads.
A pentest/red-team engagement is a phased pipeline with gates, not a pile of techniques run ad hoc. This skill sequences the 9-phase Lockheed Martin Cyber Kill Chain and routes each phase to its commands, domain skills, and discipline checks. It is the offensive analog of brainstorming → writing-plans → executing-plans: scope the work, plan it, then execute phase by phase.
Don't jump to exploitation. Earlier phases earn the access that later phases need, and each gate keeps quality high before you advance.
digraph killchain {
rankdir=LR;
scope -> recon -> weaponize -> deliver -> exploit -> install -> c2 -> actions -> report;
scope [label="0 SCOPE"]; recon [label="1 RECON"]; weaponize [label="2 WEAPONIZE"];
deliver [label="3 DELIVER"]; exploit [label="4 EXPLOIT"]; install [label="5 INSTALL"];
c2 [label="6 C2"]; actions [label="7 ACTIONS"]; report [label="8 REPORT"];
}
Each transition requires a gate (/engage.gate): required artifacts present, findings carry
CWE+CVSS+ATT&CK+evidence, and the automated checks pass. Gate FAIL → fix the gap before advancing.
/engage.* commands..engage/scope/scope.json. REQUIRED: scope-discipline./engage.memory recall to start from what worked.[CONFIRMED] without proof.engine/engine.py runs the phases under a budget/loop/trace with --resume
(/engage.pickup); offensive actions stay operator-gated.test cases passed, vs 7 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.