Token导航 LogoToken导航TokenDH.com
待分类只读github未标认证来源可访问许可证需确认审计通过

grad-ambidexterity研究生双元能力

Agent Skill

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

总安装

364

周安装

15

GitHub Stars

125

下载量

119
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

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

简介

grad-ambidexterity 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在开发协作中整理项目状态。

  • 适用于围绕代码变更、协作事项或仓库状态进行信息整合的场景。
  • 支持从 GitHub 获取 Issue、PR 和代码变更信息,辅助开发流程管理。
  • 安装方式:npx skills add https://github.com/asgard-ai-platform/skills --skill grad-ambidexterity
  • 建议确认权限范围、维护状态,以及是否涉及联网、命令执行或文件读写。

SKILL.md

Organizational Ambidexterity: Exploration vs Exploitation

Overview

Organizational ambidexterity refers to a firm's ability to simultaneously pursue exploration (innovation, experimentation, new opportunities) and exploitation (efficiency, refinement, execution of existing capabilities). March (1991) demonstrated that firms favoring one over the other face suboptimal outcomes: over-exploitation leads to competency traps, while over-exploration leads to failure traps.

When to Use

Trigger conditions:

  • User asks how to innovate without sacrificing current business performance
  • User is restructuring an organization to support both R&D and operations
  • User describes symptoms of a competency trap (good at the wrong things) or failure trap (too many experiments, no results)
  • User mentions "explore vs exploit", "innovation vs efficiency", or "ambidextrous organization"

When NOT to use:

  • For analyzing disruption from external entrants -> use grad-disruptive-innovation
  • For strategic alliances to access innovation -> use grad-coopetition
  • For internationalization decisions -> use grad-oli or grad-uppsala

Assumptions

IRON LAW: Over-Exploiting Kills Long-Term Innovation;
          Over-Exploring Kills Short-Term Revenue

Exploitation WITHOUT exploration leads to a COMPETENCY TRAP: the firm
becomes excellent at yesterday's business and is blindsided by change.

Exploration WITHOUT exploitation leads to a FAILURE TRAP: the firm
burns resources on experiments that never reach market scale.

There is no stable equilibrium — the balance must be actively managed.
  • Exploration and exploitation compete for scarce resources (attention, talent, budget)
  • The optimal balance shifts with industry dynamism and firm lifecycle stage
  • Senior leadership must actively manage the tension — it does not self-organize

Methodology

Step 1: Diagnose the Current Balance

Assess the organization's exploration-exploitation ratio:

IndicatorExploitation-HeavyBalancedExploration-Heavy
R&D spend (% revenue)< 3%5-15%> 20%
New product revenue (% total)< 10%20-40%> 50%
Time horizon of projects< 1 yearMixed> 3 years
Tolerance for failureVery lowModerateVery high
Process formalizationRigidAdaptiveChaotic

Step 2: Identify the Ambidexterity Mode

Choose the structural approach:

  • Structural ambidexterity (Tushman & O'Reilly): Separate exploration units from exploitation units with different cultures, processes, and metrics. Senior leadership integrates at the top.
  • Contextual ambidexterity (Gibson & Birkinshaw): Individual employees switch between exploration and exploitation based on context. Requires supportive culture (discipline + stretch + trust + support).
  • Sequential ambidexterity: Alternate between periods of exploration and exploitation (less common, suits smaller firms).

Step 3: Design the Integration Mechanism

For structural ambidexterity, define:

  • Separate unit boundaries (physical, cultural, reporting)
  • Integration points (shared senior team, knowledge transfer rituals)
  • Resource allocation rules (fixed exploration budget vs dynamic)

For contextual ambidexterity, define:

  • Behavioral expectations (% time on exploration vs exploitation)
  • Cultural enablers (psychological safety for experimentation)
  • Metrics that reward both (balanced scorecard approach)

Step 4: Monitor and Rebalance

Establish review cycles (quarterly pipeline health, annual market trends) to detect drift toward either trap. Define trigger conditions for rebalancing.

Output Format

# Ambidexterity Assessment: {Organization}

## Current State Diagnosis
- Balance: Exploitation-heavy / Balanced / Exploration-heavy
- Evidence: {key indicators}
- Risk: Competency trap / Failure trap / None

## Recommended Ambidexterity Mode
- Mode: Structural / Contextual / Sequential
- Rationale: {why this mode fits}

## Design Recommendations
- Exploration unit: {scope, budget, metrics, reporting}
- Exploitation unit: {scope, budget, metrics, reporting}
- Integration mechanism: {how they connect}

## Rebalancing Triggers
- {Condition 1}: shift toward more exploration
- {Condition 2}: shift toward more exploitation

Gotchas

  • Structural separation without integration is just a spin-off: If the exploration unit has no connection to the core business, you lose synergies. The senior team MUST integrate.
  • "Innovation theater" is not exploration: Hackathons and labs that never ship products waste resources. Exploration must have a path to market.
  • Context matters for mode selection: Structural ambidexterity suits large firms with resources to maintain separate units. Contextual suits smaller firms where everyone wears multiple hats.
  • The balance point shifts: A startup should be exploration-heavy. A mature firm in a stable industry can be exploitation-heavy. There is no universal ratio.
  • Metrics misalignment is the #1 killer: If exploration units are judged by exploitation metrics (quarterly revenue), they will be shut down before they can deliver.

References

  • For March (1991) formal model of adaptive systems, see references/march-1991-model.md
  • For Tushman & O'Reilly structural design templates, see references/structural-ambidexterity-design.md

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

35.28%
按下载量换算42

Claude

31.35%
按下载量换算37

Cursor

20.47%
按下载量换算24

Gemini CLI

8.67%
按下载量换算10

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills