Token导航 LogoToken导航

Agent Skill · 效率

partnering-maps(合作地图)

partnering-maps 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

partnering-maps 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 11,104。

总安装 4,774周安装 195GitHub Stars 公开资料未说明下载 1,544核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:partnering-maps(合作地图)
来源仓库:https://github.com/linuszz/partnering-maps
安装命令:
openclaw skills install partnering-maps
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install partnering-maps

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

确定关键活动的制造-购买合作伙伴关系,辅助战略联盟与供应链优化决策。适用于外包评估、供应商筛选及生产协作规划等效率提升场景。提供结构化分析框架,支持快速识别潜在合作方与风险点。安装命令:openclaw skills install partnering-maps。建议核实维护状态,避免依赖未经验证的外部数据接口。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install partnering-maps;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

partnering-maps 怎么安装?

在终端执行 openclaw skills install partnering-maps。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

partnering-maps 支持哪些 AI 工具?

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

partnering-maps 需要什么权限?

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

partnering-maps 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

partnering-maps 用的人多吗?

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

partnering-maps 安全吗?

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

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

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

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

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
partnering-maps

合作地图 · 本页

4,774—只读MIT-0通过

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

SKILL.md 原文

name
partnering-maps
description
Identify make-buy-partner relationships for key activities. Use for strategic alliances, outsourcing decisions, and supply chain optimization.

Partnering Maps

Metadata

  • Name: partnering-maps
  • Description: Relationship mapping for strategic decisions
  • Triggers: partnerships, alliances, make-buy-partner, outsourcing decisions

Instructions

Map relationship nature for each business activity to inform make-buy-partner decisions.

Framework

Make-Buy-Partner Decision

ACTIVITY
    │
    INTERNAL →
    ├── Do In-House
    │
    └── OR → Outsource to Partner

Relationship Spectrum

Relationship TypeDefinitionWhen Appropriate
Full IntegrationOwn entire processStable, high-volume operations
Joint VentureShared ownership, shared riskEntry to new markets
Strategic AlliancePartnership without ownershipCollaborative projects
Long-term ContractDedicated supplier/customerStable relationships
TransactionalArm's-length market buyFlexible, low switching cost
Do-YourselfNo partnership neededFull control

Map Components

For each activity, map:

  • Activity: What are we doing?
  • Partner Type: Who handles this?
  • Nature: How is the relationship?
  • Key Capabilities: What do they provide?
  • Alternatives: Who else could do this?
  • Strategic Importance: How critical is this activity?

Output Format

## Partnering Map: [Business Unit/Function]

### Activity Analysis

| # | Activity | Current Approach | Partner Type | Importance | Alternatives |
|----|--------|------------------|------------------|------------------|
| 1 | [Activity 1] | In-house | [Type] | High | [List] |
| 2 | [Activity 2] | Outsource | [Type] | Medium | [List] |
| 3 | [Activity 3] | Partnership | [Type] | High | [List] |
| 4 | [Activity 4] | In-house | [Type] | Low | [List] |
| 5 | [Activity 5] | Transactional | [Type] | Medium | [List] |

---

### Relationship Matrix

| Partner | Duration | Dependency | Switching Cost | Strategic Fit |
|----------|--------------|--------------|---------------|-------------|
| [Partner A] | Long-term | High | Low | 🟢 |
| [Partner B] | Medium-term | Medium | Medium | 🟡 |
| [Partner C] | Short-term | Low | High | 🔴 |

---

### Strategic Decisions

**Activity 1: [Activity 1]**
- **Current Approach:** [Description]
- **Recommended:** [Keep/Change]
- **Rationale:** [Reason 1], [Reason 2]
- **Timeline:** [When]

**Activity 2: [Activity 2]**
- **Current Approach:** [Description]
- **Recommended:** [Keep/Change]
- **Rationale:** [Reason 1], [Reason 2]
- **Timeline:** [When]

---

### Capabilities Gap Analysis

| Capability | Internal | Available via Partner | Gap | Priority |
|------------|------------------|-------------------|-----------|
| [Capability 1] | Strong | Weak | Medium | Build internal |
| [Capability 2] | Weak | Weak | Low | Outsource |
| [Capability 3] | Strong | Weak | High | Develop |

---

### Risk Assessment

| Risk | Partner | Impact | Mitigation |
|------|---------|----------|-------------|------------|
| [Risk 1] | [Partner A] | High | [Action] |
| [Risk 2] | [Partner B] | Medium | [Action] |
| [Risk 3] | [Partner C] | Low | [Action] |

---

### Next Steps

| Step | Action | Owner | Deadline |
|------|--------|---------|----------|----------|
| 1 | [Action 1] | [Name] | [Date] |
| 2 | [Action 2] | [Name] | [Date] |
| 3 | [Action 3] | [Name] | [Date] |

---

### Governance

**Decision Authority:** [Who approves partnerships]
**Review Process:** [When to review partner relationships]

---

### Portfolio Strategy

**Partnership Philosophy:** [Integrated vs. Arm's-length]
**Balance:** [Strategic priorities across relationships]

**Relationship Types Breakdown:**
- Core strategic: [Count] - %
- Important but non-core: [Count] - %
- Transactional: [Count] - %

---

### Value Capture

| Relationship Type | Value Created | Cost | Net Benefit |
|-------------------|------------------|-------------------|-----------|
| In-house | $X M | $Y M | [Positive] |
| Outsource | $Z M | $W M | [Mixed] |
| Partnership | $A M | $B M | [Positive] |

**Total Value:** $X M

---

### Strategic Implications

**Supply Chain Resilience:**
- [Analysis of dependency on key partners]

**Innovation Pipeline:**
- [Partners contributing to new capabilities]

---

### Exit Criteria

| Relationship | When to Consider Exit | Triggers |
|--------------|----------------------|-----------|
| [Partner A] | [Condition 1] | [Trigger 1] |
| [Partner B] | [Condition 2] | [Trigger 2] |
| [Partner C] | [Condition 3] | [Trigger 3] |

---

### Monitoring

| Metric | Frequency | Owner | Status |
|--------|----------|----------|----------|
| Partner performance | Quarterly | [Name] | 🟢 On track |
| Cost of outsourced activities | Monthly | [Name] | 🟡 Needs attention |

## Tips

- Consider total cost of ownership, not just price
- Look for strategic synergies beyond cost savings
- Assess switching costs and relationship investment
- Don't underestimate cultural alignment and trust
- Plan for governance and conflict resolution
- Build multiple relationship types based on activity needs
- Review relationships regularly - market conditions change

## References

- Various strategic alliance and partnership frameworks
- Joint venture and strategic alliance literature
- Make-or-buy decision frameworks
- Supply chain management best practices

平台分布

OpenClaw

81.91%
按下载量换算1,265

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills