Token导航 LogoToken导航TokenDH.com
前端设计external-servicegithub未标认证来源可访问许可证需确认审计提醒

evolution-analysis进化分析

Agent Skill

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

总安装

233

周安装

10

GitHub Stars

61

下载量

82
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:evolution-analysis(进化分析)
来源仓库:https://github.com/melodic-software/claude-code-plugins
仓库路径:skills/evolution-analysis
安装命令:
npx skills add https://github.com/melodic-software/claude-code-plugins --skill evolution-analysis
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/melodic-software/claude-code-plugins --skill evolution-analysis

简介

分析组件进化阶段、移动模式与气候因素对战略定位的影响。

  • 适用于 Codex、Claude、Cursor、Gemini CLI 中规划或设计阶段的进化策略制定。
  • 强制采用文档优先方法,先调用 docs-management 技能获取模式参考。
  • 建议基于 WWW 搜索与 Perplexity 服务器验证进化特征后再执行分析。
  • evolution-analysis 属于前端设计类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Evolution Analysis Skill

Analyze component evolution stages, movement patterns, and climatic forces affecting strategic positioning.

When to Use This Skill

Use this skill when:

  • Evolution Analysis tasks - Working on analyze component evolution and movement patterns
  • Planning or design - Need guidance on Evolution Analysis approaches
  • Best practices - Want to follow established patterns and standards

MANDATORY: Documentation-First Approach

Before analyzing evolution:

  1. Invoke docs-management skill for evolution patterns
  2. Verify evolution characteristics via MCP servers (perplexity)
  3. Base guidance on Wardley's climatic patterns

Evolution Framework

Evolution Stages and Characteristics:

Stage I: GENESIS
├── Poorly understood
├── Uncertain
├── Unpredictable
├── Constantly changing
├── Exciting/wonder
├── Low failure tolerance
└── Requires exploration

Stage II: CUSTOM-BUILT
├── Emerging understanding
├── Growing market
├── Increasing stability
├── Divergent approaches
├── Best practice emerging
└── Requires differentiation

Stage III: PRODUCT (+RENTAL)
├── Well understood
├── Feature competition
├── Stable architectures
├── Defined best practices
├── Market consolidation
└── Requires market fit

Stage IV: COMMODITY (+UTILITY)
├── Ubiquitous
├── Standardized
├── Cost-focused
├── Operational excellence
├── Highly predictable
└── Requires efficiency

Evolution Indicators

Stage Assessment Checklist

Genesis Indicators:
□ No established market
□ Uncertain about what's possible
□ High experimentation
□ Frequent pivots
□ Experts disagree on approach
□ No clear pricing model
□ Failure is expected

Custom Indicators:
□ Growing understanding
□ Talent is scarce
□ Multiple competing approaches
□ Early adopters engaged
□ Starting to see patterns
□ Custom development required
□ Premium pricing accepted

Product Indicators:
□ Clear market exists
□ Feature comparison possible
□ Documentation exists
□ Training available
□ Established vendors
□ Predictable delivery
□ Competitive pricing

Commodity Indicators:
□ Ubiquitous availability
□ Standard interfaces
□ Utility pricing
□ Focus on cost reduction
□ Scale operations
□ Interchangeable suppliers
□ SLA-driven decisions

Climatic Patterns

Patterns That Affect Evolution

Climatic Pattern Categories:

1. EVERYTHING EVOLVES
   - No component remains static
   - Evolution driven by competition
   - Supply and demand drives movement

2. CHARACTERISTICS CHANGE
   - What matters changes with evolution
   - Early: Functionality matters
   - Late: Price and reliability matter

3. NO ONE SIZE FITS ALL
   - Different methods for different stages
   - Agile for genesis, Six Sigma for commodity
   - Pioneer/Settler/Town Planner model

4. EFFICIENCY ENABLES INNOVATION
   - Commoditized components enable new genesis
   - Higher-order systems emerge from utilities
   - Cloud enabled SaaS explosion

5. HIGHER ORDER SYSTEMS CREATE NEW SOURCES OF WORTH
   - Combinations create new value
   - API economy examples
   - Platform plays

6. PAST SUCCESS BREEDS INERTIA
   - Success creates resistance to change
   - Organizational and individual inertia
   - Requires active management

Weak Signals of Evolution

Signs a Component is About to Evolve:

Genesis → Custom:
- Successful experiments being replicated
- Hiring for specific expertise
- Conference talks appearing
- Blog posts explaining "how we did X"

Custom → Product:
- Common patterns documented
- Books being written
- Training courses available
- Vendors appearing
- Open source implementations

Product → Commodity:
- Feature wars declining
- Price competition increasing
- API standardization
- Utility pricing models
- Cloud/SaaS offerings

Inertia Analysis

Types of Inertia

Inertia TypeDescriptionSigns
Success"It worked before"Resistance to change successful patterns
CapitalSunk costLarge investments in existing approach
PoliticalPower structuresEmpires built on current technology
SkillsTeam capabilitiesTeams expert in current approach
SupplierVendor relationshipsLong-term contracts, relationships
ConsumerUser expectationsUsers expect current approach

Overcoming Inertia

Inertia Management Strategies:

1. ACKNOWLEDGE
   - Recognize inertia exists
   - Don't fight it directly
   - Understand the source

2. CREATE ALTERNATIVES
   - Build parallel capability
   - Don't force immediate switch
   - Let new approach prove itself

3. MANAGE TRANSITION
   - Gradual migration
   - Clear sunset timelines
   - Training and support

4. ADDRESS ROOT CAUSES
   - Skill development
   - Relationship management
   - Political navigation

Movement Analysis

Predicting Movement

Movement Prediction Framework:

COMPETITIVE PRESSURE
├── High competition → Faster evolution
├── Low margins → Commodity imminent
└── Feature convergence → Product → Commodity

TECHNOLOGY SHIFTS
├── New enabling technology
├── Cost reduction breakthroughs
└── Standardization efforts

MARKET DYNAMICS
├── User demand patterns
├── Regulatory changes
└── Economic pressures

ECOSYSTEM EFFECTS
├── Adjacent commoditization
├── Platform availability
└── Developer adoption

Movement Speed

FactorFaster EvolutionSlower Evolution
CompetitionHighLow (monopoly)
StandardizationIndustry effortsProprietary lock-in
CapitalVC investmentLimited funding
RegulationMinimalHeavy regulation
Network effectsStrongWeak

Analysis Template

# Evolution Analysis: [Component/System]

## Current Position Assessment

### Component Inventory

| Component | Current Stage | Evidence |
|-----------|---------------|----------|
| [Name] | Genesis/Custom/Product/Commodity | [Indicators observed] |

### Evolution Evidence

**Genesis Stage Components:**
- [Component]: [Why it's in genesis]

**Evolving Components:**
- [Component]: Moving from [stage] to [stage]
- Evidence: [Signs of movement]

## Climatic Patterns Active

### Relevant Patterns
1. [Pattern]: [How it affects this context]
2. [Pattern]: [How it affects this context]

## Inertia Assessment

### Sources of Inertia

| Component | Inertia Type | Strength | Mitigation |
|-----------|--------------|----------|------------|
| [Name] | Success/Capital/Political | High/Med/Low | [Strategy] |

## Movement Forecast

### 6-Month Horizon
- [Component] likely to evolve to [stage]
- Trigger: [What will cause movement]

### 18-Month Horizon
- [Component] likely to evolve to [stage]
- Industry trend: [Supporting evidence]

## Strategic Implications

### Opportunities
- [Opportunity from evolution]

### Threats
- [Threat from evolution]

### Recommended Actions
1. [Action based on evolution analysis]
2. [Action based on inertia management]

Evolution Timeline Patterns

Typical Evolution Timelines:

FAST (2-5 years through all stages):
- Consumer internet services
- Mobile apps
- Cloud features
- AI/ML capabilities (currently)

MEDIUM (5-15 years):
- Enterprise software categories
- Development practices
- Infrastructure patterns

SLOW (15-30+ years):
- Physical infrastructure
- Regulated industries
- Deep technical systems

Acceleration Factors:
- Open source adoption
- Cloud availability
- Developer community
- VC investment
- API-first design

Workflow

When analyzing evolution:

  1. Inventory Components: List all relevant components
  2. Assess Current Stage: Use indicators checklist
  3. Identify Movement: Look for evolution signals
  4. Analyze Inertia: Understand resistance sources
  5. Predict Timing: Estimate movement speed
  6. Strategic Implications: What does this mean for decisions?

References

For detailed guidance:


Last Updated: 2025-12-26

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

35.83%
按下载量换算29

Claude

25.55%
按下载量换算21

Cursor

19.46%
按下载量换算16

Gemini CLI

9.38%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

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

来源信息

继续浏览同类 Skills