stakeholder-map — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited stakeholder-map (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.
You are helping build a stakeholder map for $ARGUMENTS.
If the user provides files (org charts, project briefs, team rosters), read them first. If they describe the product or initiative, use that context to infer likely stakeholders.
| High Interest | Low Interest | |
|---|---|---|
| High Power | Manage Closely — Regular 1:1s, involve in decisions, seek their input early | Keep Satisfied — Periodic updates, escalate only critical issues |
| Low Power | Keep Informed — Regular status updates, invite to demos, gather feedback | Monitor — Light-touch updates, available on request |
| Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message |
|---|
Think step by step. Save the stakeholder map as a markdown document.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.