Install any skill in seconds. Free to start, no credit card required.
Get Started Free →okhp3/okhp3-stakeholder-and-role-mapping
Derive and validate a structured stakeholder register from a completed Process Intake Record.
Passed 19 of 23 test cases with the skill, and 7 of 23 without it.
and 14 more in the full report
12 fixed7 passed either way4 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.
In the validated legal review process intake, the VP of Legal is tagged as an approver actor type. Which engagement strategy must be assigned to this stakeholder?
| Checked | Without skill | With skill |
|---|---|---|
| Assigns Consult as the engagement strategy for approver actor types. | Missed | Passed |
The instructions your model reads when the skill loads.
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Derive a structured stakeholder register from a validated PIR. The register maps every actor to a stakeholder record with role classification, interest, influence, and engagement strategy — providing the role foundation for RACI matrices, governance documents, and process narrative authoring.
ready_for_narrative: true and you need a stakeholder register before writing the PNSprocess-intake-and-scopescripts/generate-stakeholder-register.mjs derives the register from pir.actors[]:
| Actor type | Engagement strategy |
|---|---|
initiator | Collaborate |
performer | Collaborate |
approver | Consult |
reviewer | Consult |
notified | Inform |
system | Monitor |
Each register entry contains:
stakeholder_id — from actors[].role_idname — from actors[].role_nametest cases passed, vs 7 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.