Soc Stakeholder

What it does

When your agent uses it

• The user needs to map stakeholders for a project
• Manage conflicting interests
• Prioritize communication
• Build a stakeholder engagement plan — even if they say who needs to approve this

Example prompts

• “who needs to approve this”
• “how do I get buy-in”
• “who might block this project”
• “/soc-stakeholder”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1Identify all stakeholders (internal and external)
2. 2Assess each on Power (ability to influence outcome) and Interest (degree of concern)
3. 3Classify into the four quadrants
4. 4Understand each stakeholder's position: supportive, neutral, or resistant
5. 5Design engagement strategy per quadrant and position
6. 6Monitor for shifts in power or interest over time

What it can do on your machine

Read from SKILL.md and the folder at commit 4e7f4f8. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Soc Stakeholder loads about 1.4k tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 484 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~103

When it runs · the whole SKILL.md, loaded when a task matches

~1.4k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~4.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from asgard-ai-platform/skills at commit 4e7f4f8, republished under its MIT licence (© asgard-ai-platform). 484 words, ~1,406 tokens.

name

soc-stakeholder

description

Conduct stakeholder analysis using identification, Power-Interest matrix classification, and influence strategy development. Use this skill when the user needs to map stakeholders for a project, manage conflicting interests, prioritize communication, or build a stakeholder engagement plan — even if they say 'who needs to approve this', 'how do I get buy-in', or 'who might block this project'.

metadata.category

WP-18 社會科學院

metadata.tags

social-science, stakeholder-analysis, project-management

IRON LAW: Map ALL Stakeholders Before Engaging Any

Identify the full stakeholder landscape FIRST. Engaging one powerful
stakeholder before understanding the others' positions can create
unintended alliances against you. A stakeholder you forgot to include
becomes your biggest risk.

# Stakeholder Analysis: {Project/Decision}

## Stakeholder Map
| Stakeholder | Role | Power | Interest | Position | Quadrant |
|-------------|------|-------|----------|----------|----------|
| {name/role} | {relationship} | H/M/L | H/M/L | Support/Neutral/Resist | {strategy} |

## Power-Interest Matrix
| | Low Interest | High Interest |
|---|---|---|
| **High Power** | {names} | {names} |
| **Low Power** | {names} | {names} |

## Engagement Plan
| Stakeholder | Strategy | Frequency | Channel | Key Message |
|-------------|---------|-----------|---------|-------------|
| {name} | {approach} | {weekly/monthly/ad-hoc} | {meeting/email/report} | {tailored message} |

## Conflict Points
| Conflict | Stakeholders | Resolution Approach |
|----------|-------------|-------------------|
| {issue} | {A vs B} | {proposed resolution} |

© asgard-ai-platform, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in soc-stakeholder of asgard-ai-platform/skills.

• SKILL.md
• examples/sample_scenario.md
• references/negotiation-tactics.md

Open the folder on GitHubat commit 4e7f4f8