Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

soc-stakeholder社会利益相关者

Agent Skill

soc-stakeholder 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

360

周安装

15

GitHub Stars

125

下载量

120
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:soc-stakeholder(社会利益相关者)
来源仓库:https://github.com/asgard-ai-platform/skills
仓库路径:skills/soc-stakeholder
安装命令:
npx skills add https://github.com/asgard-ai-platform/skills --skill soc-stakeholder
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/asgard-ai-platform/skills --skill soc-stakeholder

简介

soc-stakeholder 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 适用于利益相关者识别、角色分析与影响力评估等社会研究项目。
  • 通过关键词或任务场景输入,Agent 可返回匹配的候选结果列表。
  • 安装命令:npx skills add https://github.com/asgard-ai-platform/skills --skill soc-stakeholder。
  • 使用前请确认权限范围、维护状态及是否涉及联网或文件操作。

SKILL.md

Stakeholder Analysis

Overview

Stakeholder analysis identifies everyone who affects or is affected by a decision, classifies them by power and interest, and designs engagement strategies for each group. It prevents surprises from forgotten stakeholders and focuses effort on the relationships that matter most.

Framework

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.

Power-Interest Matrix

Low InterestHigh Interest
High PowerKeep Satisfied — Monitor, inform proactively, don't bore with detailsManage Closely — Active engagement, regular communication, involve in decisions
Low PowerMonitor — Minimal effort, watch for changes in power or interestKeep Informed — Regular updates, address concerns, leverage as advocates

Analysis Steps

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

Engagement Strategies by Position

PositionStrategy
SupporterEmpower them, give them information to advocate on your behalf
NeutralEducate about benefits, reduce perceived risk, address concerns early
ResistantUnderstand their concerns deeply, find common ground, involve in design

Conflict Management

When stakeholders have conflicting interests:

  1. Identify the specific points of conflict
  2. Separate positions (what they say they want) from interests (why they want it)
  3. Find solutions that address underlying interests of both parties
  4. Escalate only when negotiation fails — and escalate to a stakeholder with power over both

Output Format

# 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} |

Examples

Correct Application

Scenario: Stakeholder analysis for implementing a new CRM system at a mid-size company

StakeholderPowerInterestPositionStrategy
CEOHighLowNeutralKeep Satisfied — monthly summary, focus on ROI
Sales VPHighHighSupporterManage Closely — co-design, champion role
IT DirectorHighHighResistant (worried about integration)Manage Closely — involve early, address technical concerns
Sales repsLowHighResistant (don't want to change tools)Keep Informed — training, show time savings, address concerns
FinanceMediumLowNeutralMonitor — inform about budget when needed

Key insight: IT Director is high-power + resistant = biggest risk. Address integration concerns before the project gets blocked ✓

Incorrect Application

  • Only mapped internal stakeholders, forgot that the CRM vendor, existing tool vendor (who might resist), and key customers (who'll be affected by the transition) are also stakeholders. Violates Iron Law: map ALL stakeholders.

Gotchas

  • Power shifts: A stakeholder who's low-power today may gain power (promotion, organizational change). Reassess quarterly.
  • Hidden stakeholders: Executive assistants, board members' advisors, union representatives — people with informal but real influence.
  • Don't over-engage low-power stakeholders: It's tempting to spend time on the most vocal critics, but if they have low power, their resistance won't block you. Focus energy on the high-power quadrants.
  • Resistance ≠ enemy: Resistant stakeholders often have legitimate concerns. Their input can improve the project. Treat resistance as data, not opposition.
  • Stakeholder fatigue: Over-communicating with everyone wastes their time and yours. Match communication frequency to the quadrant.

References

  • For negotiation techniques with resistant stakeholders, see references/negotiation-tactics.md

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.56%
按下载量换算44

Claude

30.17%
按下载量换算36

Cursor

17.77%
按下载量换算21

Gemini CLI

7.81%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills