Token导航 LogoToken导航TokenDH.com
效率需要联网clawhub未标认证来源可访问clear审计通过

business-definition业务定义

Agent Skill

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

总安装

5,611

周安装

241

GitHub Stars

公开资料未说明

下载量

1,909
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install business-definition

简介

business-definition 用于确定业务实体是统一还是分离,支持投资组合管理和战略规划。

  • 适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。
  • 通过 clawhub 安装,命令为 openclaw skills install business-definition。
  • 使用前需确认权限范围和维护状态,注意是否会触发联网或文件读写操作。
  • 适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。

SKILL.md

name
business-definition
description
Determine unified vs separated business entities. Use for portfolio management, strategic planning, and restructuring decisions.

Business Definition

Metadata

  • Name: business-definition
  • Description: Framework for defining unified vs separated businesses
  • Triggers: business definition, unified vs separated, portfolio structure, business units

Instructions

Apply business definition framework to determine organizational structure for strategic analysis.

Framework

The Definition Test

Unified Business IF:

1. Share customers?
2. Share brand?
3. Share assets/resources?
4. Share supply chain?
5. Share channels/distribution?

AND:

6. Economies of scale or scope apply?
7. Common management/leadership?
8. Integrated planning across business?

THEN → SAME BUSINESS

IF ANY 'NO' → SEPARATE BUSINESSES

Business Unit Categories

CategoryDescriptionWhen Unified
Product LeadershipSame products across units✅ Yes
Market LeadershipSame geographic focus✅ Yes
OperationsShared manufacturing, logistics✅ Yes
Sales & MarketingShared channels, brand✅ Yes
Innovation/R&DCentralized development✅ Yes
Finance/SupportShared treasury, HR✅ Yes

Organizational Structures

StructureAdvantagesDisadvantages
UnifiedSynergy, efficiency, coordinated strategyComplexity, slow decisions, potential conflicts
Holding CompanyPortfolio management, capital allocation, focused leadershipAgency costs, bureaucracy
Strategic AllianceFlexibility, shared expertise, reduced investmentCoordination costs, partner conflicts
Joint VentureRisk sharing, resource sharingProfit sharing, governance complexity
Federated/IndependentAgility, accountability, clear focusDuplication, lack of synergy

Output Process

  1. Analyze current state - What's the structure?
  2. Apply definition test - Should we unify or separate?
  3. Identify synergies - What value in integration?
  4. Define new structure - Target organizational design
  5. Evaluate feasibility - Culture, systems, capabilities
  6. Develop transition plan - Timeline, steps, governance
  7. Assess value capture - Benefits vs costs

Output Format

## Business Definition Analysis: [Company/Portfolio]

### Current Structure

**Structure Type:** [Unified/Holding/Federated/Independent]

**Business Units Analyzed:** N units

**Shared Capabilities:**
- [Capability 1] - [Description]
- [Capability 2] - [Description]
- [Capability 3] - [Description]

### Definition Test Results

| Test Question | Result | Implication |
|---------------|---------|--------------|
| Share customers? | ✅ Yes | Potential cross-selling |
| Share brand? | ✅ Yes | Brand consistency |
| Share assets? | ✅ Yes | Asset optimization |
| Share supply chain? | ✅ Yes | Cost efficiency |
| Share channels? | ❌ No | Channel conflicts |
| Common leadership? | ✅ Yes | Management coordination |
| Integrated planning? | ❌ No | Planning autonomy |
| Economies of scale? | ✅ Yes | Scale advantages |

**Conclusion:** [Unified/Separate business structure]

### Proposed Structure

**Target Structure:** [New structure type]

**Rationale:**
1. [Reason 1] - [Why change?]
2. [Reason 2] - [Strategic benefit]
3. [Reason 3] - [Operational necessity]

**Business Unit Alignment:**
- [Unit A] → [New parent/placement]
- [Unit B] → [New parent/placement]
- [Unit C] → [New parent/placement]

### Transition Plan

| Phase | Action | Owner | Timeline |
|--------|--------|---------|------------|
| Planning | Define new org structure | CEO | Q1 |
| Design | Create governance model | Legal | Q2 |
| Implementation | Transfer assets/people | Ops | Q3 |
| Stabilization | Optimize processes | All Units | Q4 |

### Value Capture Assessment

| Synergy Type | Estimated Value | Cost | Net Benefit |
|------------|-----------------|----------|------------|
| Cost reduction | $X M | $Y M | [Positive] |
| Revenue enhancement | $X M | $Y M | [Positive] |
| Capability leverage | $X M | $Y M | [Positive] |
| **Total** | $Z M | $W M | [Net Value] |

**ROI:** [Net Benefit / Cost] × 100%

---

### Risk Assessment

| Risk | Probability | Impact | Mitigation |
|------|---------|----------|-------------|
| Disruption risk | High | High | [Mitigation] |
| Synergy failure | Medium | High | [Mitigation] |
| Cost overruns | Medium | Medium | [Mitigation] |
| Governance complexity | Low | Low | [Mitigation] |

---

### Strategic Implications

1. **[Implication 1]** - [Analysis]
2. **[Implication 2]** - [Analysis]

### Governance Recommendations

1. **[Recommendation 1]** - [Description]
2. **[Recommendation 2]** - [Description]
3. **[Recommendation 3]** - [Description]

Tips

  • Don't force unification - structure should serve strategy
  • Consider cultural compatibility - can they work together?
  • Assess synergy potential realistically - don't assume automatic gains
  • Evaluate both benefits and costs - net value matters
  • Consider transition costs - often higher than expected
  • Governance is critical - define clear decision rights
  • Communicate transparently - manage expectations throughout

References

  • Various organizational design and strategy sources
  • M&A case studies and corporate restructuring literature

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

OpenClaw

82.75%
按下载量换算1,580

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills