Token导航 LogoToken导航

Agent Skill · 待分类

grad-coopetition(研究生合作竞争)

grad-coopetition 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

grad-coopetition 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 7,593。

总安装 353周安装 15GitHub Stars 125下载 124核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-coopetition

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

grad-coopetition 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在开发协作中整理项目状态。适用于围绕代码变更、协作事项或仓库状态进行信息整合的场景。支持从 GitHub 获取 Issue、PR 和代码变更信息,辅助开发流程管理。

安装方式:npx skills add https://github.com/asgard-ai-platform/skills --skill grad-coopetition 建议确认权限范围、维护状态,以及是否涉及联网、命令执行或文件读写。

来源仓库内路径:skills/grad-coopetition

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/asgard-ai-platform/skills --skill grad-coopeti…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

grad-coopetition 怎么安装?

在终端执行 npx skills add https://github.com/asgard-ai-platform/skills --skill grad-coopetition。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

grad-coopetition 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

grad-coopetition 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

grad-coopetition 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

grad-coopetition 用的人多吗?

公开数据是累计安装 353 次,近一周安装 15 次,下载 124 次,GitHub 125 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

grad-coopetition 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
grad-coopetition

研究生合作竞争 · 本页

353125需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Co-opetition: The Value Net (Brandenburger & Nalebuff, 1996)

Overview

Co-opetition recognizes that business relationships are never purely competitive or purely cooperative. The Value Net model extends Porter's focus on rivalry by adding complementors — players whose products increase the value of yours. The PARTS framework (Players, Added value, Rules, Tactics, Scope) provides a structured approach to changing the game rather than just playing it.

When to Use

Trigger conditions:

  • User is analyzing a relationship that is simultaneously cooperative and competitive
  • User asks about strategic alliances with competitors
  • User needs to identify complementors or map all players in a value network
  • User mentions "frenemy", "coopetition", "complementors", or "value net"

When NOT to use:

  • For pure competitive analysis -> use Porter's Five Forces
  • For internal organizational balance -> use grad-ambidexterity
  • For international market entry mode -> use grad-oli

Assumptions

IRON LAW: Every Business Relationship Contains BOTH Cooperative
          and Competitive Elements

There is NO purely competitive or purely cooperative relationship.
A supplier cooperates (provides inputs) AND competes (captures margin).
A competitor competes (takes share) AND cooperates (grows the category).

Any analysis that labels a player as ONLY competitor or ONLY partner
is incomplete. Always map BOTH dimensions.
  • Business is a game — but players can change the game, not just play it
  • Value creation is cooperative; value capture is competitive
  • The same player can be a competitor AND a complementor simultaneously

Methodology

Step 1: Map the Value Net

Place the focal firm at the center and map four player types: Customers, Suppliers, Competitors (whose products DECREASE your value), and Complementors (whose products INCREASE your value). Key insight: a player can occupy multiple roles (Samsung supplies displays to Apple AND sells competing phones).

Step 2: Assess Added Value

For each player, calculate added value:

  • Added value = Total value of the game WITH the player MINUS total value WITHOUT the player
  • A player can never capture more than their added value
  • Strategies should aim to increase YOUR added value and manage others'

Step 3: Apply PARTS Framework

Systematically evaluate five levers to change the game:

LeverQuestionAction
PlayersWho is in the game? Should we add/remove players?Bring in new complementors, attract new competitors to reduce supplier power
Added valueHow can we increase our added value?Differentiate, build switching costs, create loyal customers
RulesWhat rules govern the game? Can we change them?Contracts, regulations, industry standards, MFN clauses
TacticsHow do perceptions shape the game?Signaling, commitments, transparency vs fog
ScopeWhat is the boundary of the game?Link or de-link games, expand or narrow scope

Step 4: Design Co-opetition Strategy

For each key relationship, specify:

  • Where to cooperate (value creation): joint R&D, standard setting, market expansion
  • Where to compete (value capture): pricing, customer acquisition, differentiation
  • Boundary rules: what information to share, what to protect

Output Format

# Co-opetition Analysis: {Focal Firm}

## Value Net Map
- Customers / Suppliers / Competitors / Complementors: {list each, note dual roles}

## Added Value Assessment
| Player | Added Value | Leverage |
|--------|-------------|----------|
| {Focal firm} | {assessment} | {high/medium/low} |

## PARTS Analysis
| Lever | Current State | Recommended Change |
|-------|---------------|-------------------|
| Players / Added value / Rules / Tactics / Scope | {current} | {action} |

## Co-opetition Strategy
- Cooperate on: {activities} | Compete on: {activities} | Boundary rules: {policy}

Gotchas

  • Complementor identification is the hardest part: Force yourself to ask: "Whose product makes mine more valuable?" The biggest insights hide here.
  • Dual roles create tension: When a partner is also a competitor, define explicit information boundaries.
  • Added value is dynamic: Every major move changes everyone's added value. Reassess after launches or market entries.
  • Cooperation without boundaries leads to knowledge leakage: Alliances need explicit IP firewalls.
  • PARTS is about changing the game: If your analysis only describes the current game, you missed the point.

References

  • For game theory foundations of co-opetition, see references/coopetition-game-theory.md
  • For PARTS framework detailed application guide, see references/parts-framework-guide.md

平台分布

Codex

35.48%
按下载量换算44

Claude

31.24%
按下载量换算39

Cursor

20.13%
按下载量换算25

Gemini CLI

9.34%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills