skill-factory

Skill Factory v2 - Skill Factory

Task Objective

This Skill is a full lifecycle management factory for skills, analogous to a production factory in the real world:

Raw materials → Technical documentation/URL/requirement description
Production line → Four-stage pipeline (production→processing→publishing→destruction)
Product → Structured SKILL.md skill package

Trigger conditions: Used when a skill needs to be created, modified, optimized, integrated, split, published, or retired.

Factory Panoramic Architecture

flowchart LR
    subgraph Phase1["1 生产 Production"]
        direction TB
        P1_R[researcher 研究]
        P1_A[analyzer 分析]
        P1_P[planner 规划]
        P1_G[generator 生成]
        P1_K[packager 验证]
        P1_R --> P1_A --> P1_P --> P1_G --> P1_K
    end

    subgraph Phase2["2 加工 Processing"]
        direction TB
        P2_E[enricher 丰富]
        P2_S[simplifier 简化]
        P2_B[beautifier 美化]
        P2_T[standardizer 规范]
    end

    subgraph Phase3["3 发布 Publishing"]
        direction TB
        P3_V[version 版本管理]
        P3_M[metadata 元数据]
        P3_R[release 发布操作]
        P3_V --> P3_M --> P3_R
    end

    subgraph Phase4["4 销毁 Destruction"]
        P4_D[destroyer 退役销毁]
    end

    Phase1 -->|产出技能包| Phase2
    Phase2 -->|加工完成| Phase3
    Phase3 -->|需退役| Phase4

    style Phase1 fill:#e8f5e9,stroke:#4caf50,color:#1b5e20
    style Phase2 fill:#fff3e0,stroke:#ff9800,color:#e65100
    style Phase3 fill:#e3f2fd,stroke:#2196f3,color:#0d47a1
    style Phase4 fill:#fce4ec,stroke:#e91e63,color:#880e4f

Four-stage positioning

Stage	Analogous real-world factory	Input	Output	Core question
① Production	Raw material→finished product	Documentation/URL/requirements	SKILL.md skill package	How to build?
② Processing	Finished product→fine processing	Existing skill	Upgraded skill	How to modify?
③ Publishing	Quality inspection→factory release	Processed skill	Version release record	How to release?
④ Destruction	Retirement→recycling	Outdated skill	deprecated marker	How to deprecate?

Four-dimensional classification system (runs through all stages)

flowchart TB
    subgraph 四维分类法
        direction LR
        L1["功能维度<br/>━━━━━━━━<br/>轻 单一功能<br/>重 多模块"]
        L2["内容维度<br/>━━━━━━━━<br/>厚 内容丰富<br/>薄 内容精简"]
    end
    
    Q1["轻+薄 简单技能<br/>单文件 SKILL.md"]
    Q2["重+薄 技能族-薄<br/>skills 子目录"]
    Q3["轻+厚 复杂单技能<br/>SKILL.md + refs"]
    Q4["重+厚 技能族-厚<br/>混合模式"]

    style Q1 fill:#e8f5e9,stroke:#4caf50,color:#1b5e20
    style Q2 fill:#e3f2fd,stroke:#2196f3,color:#0d47a1
    style Q3 fill:#fff3e0,stroke:#ff9800,color:#e65100
    style Q4 fill:#f3e5f5,stroke:#9c27b0,color:#4a148c

Dimension	Definition	Judgment criteria	Output structure
Light	Single function	1 core capability	Single SKILL.md
Heavy	Complex function	Multiple modules, can be used independently	`skills/{子}/SKILL.md`
Thin	Concise content	<300 lines can describe it clearly	No additional files needed
Thick	Rich content	Requires detailed explanations/examples/code	`references/` + optional `scripts/`

Stage One: Production

The complete pipeline for creating a new skill from scratch.

flowchart LR
    A[用户输入] --> R[researcher 信息研究]
    R --> N[需求文档]
    N --> AN[analyzer 技术分析]
    AN --> PL[planner 类型判定]
    PL --> GE[generator 按类型生成]
    GE --> PA[packager 结构验证]
    PA --> OUT[技能包]

    style A fill:#f5f5f5,color:#424242
    style R fill:#c8e6c9,stroke:#388e3c,color:#1b5e20
    style AN fill:#a5d6a7,stroke:#2e7d32,color:#1b5e20
    style PL fill:#81c784,stroke:#43a047,color:#ffffff
    style GE fill:#66bb6a,stroke:#388e3c,color:#ffffff
    style PA fill:#4caf50,stroke:#2e7d32,color:#ffffff
    style OUT fill:#e8f5e9,stroke:#4caf50,color:#1b5e20

Sub-skill index

Sub-skill	Responsibility	Core
researcher	Receive input, interactive confirmation, supplement information	Six-step research process + callback mechanism
analyzer	Extract technical information, assess volume	Completeness >= 80% determination
planner	Determine the four-dimensional classification of light/heavy/thin/thick	Two-step decision tree
generator	Generate files according to the four types	Four templates A/B/C/D
packager	Verify the completeness of the corresponding structure	Four verification modes + quality scoring

Typical scenario mapping

User requirement	Production process entry point
"Help me generate a skill based on this tutorial"	researcher → full process
"Turn this website into a skill"	researcher → full workflow
"I have a requirement I want to turn into a skill"	researcher → full workflow

Phase 2: Processing

Process existing skills, analogous to a factory's finishing workshop.

flowchart TD
    Input[已有技能] --> Operation{加工类型?}
    
    Operation -->|内容不够| E[enricher 丰富]
    Operation -->|内容太多| S[simplifier 简化]
    Operation -->|可读性差| B[beautifier 美化]
    Operation -->|格式不规范| T[standardizer 规范]
    
    Operation -->|多个要合并| I[整合模式]
    Operation -->|太复杂要拆| D[拆分模式]
    
    E & S & B & T --> Output[加工后技能]
    
    style Input fill:#fff3e0,stroke:#ff9800,color:#e65100
    style E fill:#ffe0b2,stroke:#fb8c00,color:#e65100
    style S fill:#ffe0b2,stroke:#fb8c00,color:#e65100
    style B fill:#ffe0b2,stroke:#fb8c00,color:#e65100
    style T fill:#ffe0b2,stroke:#fb8c00,color:#e65100
    style I fill:#ffcc80,stroke:#ef6c00,color:#e65100
    style D fill:#ffcc80,stroke:#ef6c00,color:#e65100
    style Output fill:#fff3e0,stroke:#ff9800,color:#e65100

2.1 Enricher

Responsibility: Supplement skill content to make it more complete

Operation	Description	Effect
Add examples	Add more usage examples	Possibly thin→thick
Add references	Split detailed implementation into references/	Thin→thick
Extend capabilities	Add new features on top of the existing foundation	Possibly light→heavy
Add Mermaid	Add visualization diagrams for the workflow	Increased thickness

2.2 Simplifier

Responsibility: Streamline redundant content to make the skill more concise

Operation	Description	Effect
Merge duplicates	Remove duplicate descriptions	Fewer lines
Refine language	Condense redundant wording	Fewer lines
Extract summaries	Keep an overview in the main file	Thick→thin (possibly)
Atomic splitting	Split complex skills into simple sub-skills	Heavy→many light

2.3 Beautifier

Responsibility: Improve the readability and visual presentation of the skill

Operation	Description	Example
Add Mermaid diagrams	Flowcharts, architecture diagrams, decision trees	flowchart / sequenceDiagram
Optimize layout	Unify heading levels, align tables	Markdown format optimization
Color scheme	Unify color semantics	Green=success/Red=error/Blue=information
Enhance navigation	Add table of contents, quick links	Anchor links

2.4 Standardizer

Responsibility: Make skills conform to standards and specifications

Operation	Description	Standard
Frontmatter calibration	name/version/description/tags	100-150 character description
Naming conventions	Directory names, file names in kebab-case	Lowercase + hyphens
Required sections	Task objectives/operational steps/examples/notes	Fill in any missing one
Link checking	Validity of internal links in references	No dead links

2.5 Special Processing Modes

Assembly

Merge multiple skills into one:

技能A + 技能B + 技能C → 整合技能族 (重+薄 或 重+厚)

Corresponds to the original scenario-integrate
Mode selection: sequential/parallel/nested
Output type determination: all simple children → heavy + thin / has complex children → heavy + thick

Disassembly

Split a complex skill into multiple:

复杂技能 (重+厚) → 技能A (轻+薄) + 技能B (轻+厚) + 技能C (轻+薄)

Corresponds to the original scenario-decompose
Split dimensions: function/scenario/complexity
Migration strategy: parallel maintenance → deprecated → retirement

Typical scenario mapping

User requirement	Processing entry point
"This skill has too little content, enrich it"	enricher
"This skill is too long, streamline it"	simplifier
"Add some charts to make it look better"	beautifier
"Check whether this complies with the standards"	standardizer
"Merge these skills"	Integration mode
"This skill is too complex, split it apart"	Split mode

Phase Three: Publishing

Version management and formal release.

flowchart LR
    V[version 版本判定] --> M[metadata 元数据更新]
    M --> R[release 发布执行]

    style V fill:#bbdefb,stroke:#1976d2,color:#0d47a1
    style M fill:#90caf9,stroke:#1565c0,color:#ffffff
    style R fill:#64b5f6,stroke:#1976d2,color:#ffffff

3.1 Version Manager

Change type	Version increment	Trigger condition
Fix	patch +1	Typos, description corrections
Feature	minor +1	New capabilities, new examples
Type Upgrade	minor +1	Light→heavy, thin→thick
Breaking	major +1	Interface changes, capability removal

3.2 Metadata Manager

Metadata field	Update timing
description	Re-evaluate 100-150 characters after each change
tags	Add or remove tags when capabilities change
dependency.parent	When refactoring parent-child relationships
dependency.children	When adding/removing child skills
version	Increment on each release

3.3 Release Publisher

git add .
git commit -m "<type>(<skill>): <变更说明>"
git tag -a v<版本> -m "Release v<版本>: <说明>"

Commit type prefix	Applicable scenario
`fix`	Bug fix
`feat`	New feature
`refactor`	Type upgrade/refactor
`feat!`	Breaking change

Typical scenario mapping

User requirement	Publishing entry point
"The changes are done, commit a version"	version → metadata → release
"What type is this change?"	version determination
"Update the metadata"	metadata

Phase Four: Destruction

Skill retirement and cleanup.

flowchart TD
    D[destroyer] --> Step1{退役原因?}
    
    Step1 -->|被拆分替代| S1[标记 deprecated]
    Step1 -->|已过时无用| S2[标记 deprecated]
    Step1 -->|有安全问题| S3[紧急标记]
    
    S1 --> Step2[编写迁移指引]
    S2 --> Step2
    S3 --> Step2
    
    Step2 --> Step3[设置迁移期]
    Step3 --> Step4[归档或删除]

    style D fill:#ffcdd2,stroke:#d32f2f,color:#b71c1c
    style S1 fill:#ef9a9a,stroke:#c62828,color:#b71c1c
    style S2 fill:#ef9a9a,stroke:#c62828,color:#b71c1c
    style S3 fill:#ef5350,stroke:#c62828,color:#ffffff

Destruction process

Step	Operation	Description
1. Determine the reason	Why retire?	Replaced/outdated/security
2. Mark as deprecated	Modify SKILL.md	Add [Deprecated] to description
3. Migration guidance	Tell users what to use instead	Link to the new skill
4. Set a migration period	30 days recommended	Give users buffer time
5. Archive/delete	Move to archive/ or delete	Clean up the repository

Deprecated template

---
name: <原技能>
version: v2.0.0
description: "[已废弃] 请使用以下替代技能:"
tags: [deprecated]
---

## 退役通知

本技能已于 {日期} 标记为废弃。

### 替代方案
- [<新技能A>](../<new-skill-a>/SKILL.md): <用途>
- [<新技能B>](../<new-skill-b>/SKILL.md): <用途>

### 迁移指南
<简要说明如何从旧技能迁移到新技能>

Typical scenario mapping

User requirement	Destruction entry point
"This skill is no longer used, retire it"	destroyer
"Already split, how should the old one be handled?"	destroyer (replaced mode)

Scenario Quick Routing

flowchart TD
    Start[用户需求] --> Q{是什么操作?}

    Q -->|从零创建| P1[阶段一: 生产]
    Q -->|修改已有| Q2{改什么?}
    Q -->|发布版本| P3[阶段三: 发布]
    Q -->|不再需要| P4[阶段四: 销毁]

    Q2 -->|丰富内容| P2E[阶段二: 丰富]
    Q2 -->|精简内容| P2S[阶段二: 简化]
    Q2 -->|美化排版| P2B[阶段二: 美化]
    Q2 -->|规范检查| P2T[阶段二: 规范]
    Q2 -->|合并多个| P2I[阶段二: 整合]
    Q2 -->|拆分复杂| P2D[阶段二: 拆分]

    style P1 fill:#e8f5e9,stroke:#4caf50,color:#1b5e20
    style P2E fill:#fff3e0,stroke:#ff9800,color:#e65100
    style P2S fill:#fff3e0,stroke:#ff9800,color:#e65100
    style P2B fill:#fff3e0,stroke:#ff9800,color:#e65100
    style P2T fill:#fff3e0,stroke:#ff9800,color:#e65100
    style P2I fill:#ffcc80,stroke:#ef6c00,color:#e65100
    style P2D fill:#ffcc80,stroke:#ef6c00,color:#e65100
    style P3 fill:#e3f2fd,stroke:#2196f3,color:#0d47a1
    style P4 fill:#fce4ec,stroke:#e91e63,color:#880e4f

Index of All Sub-skills

Phase One: Production (5)

Sub-skill	File Path	Responsibility
researcher	`skills/skill-factory-researcher/SKILL.md`	Information Research
analyzer	`skills/skill-factory-analyzer/SKILL.md`	Technical Analysis
planner	`skills/skill-factory-planner/SKILL.md`	Type Determination
generator	`skills/skill-factory-generator/SKILL.md`	File Generation
packager	`skills/skill-factory-packager/SKILL.md`	Structure Validation

Phase Two: Processing (4)

Sub-skill	File Path	Responsibility
enricher	`skills/skill-factory-enricher/SKILL.md`	Content Enrichment
simplifier	`skills/skill-factory-simplifier/SKILL.md`	Content Simplification
beautifier	`skills/skill-factory-beautifier/SKILL.md`	Format Beautification
standardizer	`skills/skill-factory-standardizer/SKILL.md`	Normalization

Phase Three: Publishing (3)

Sub-skill	File Path	Responsibility
publisher-version	`skills/skill-factory-publisher-version/SKILL.md`	Version Management
publisher-metadata	`skills/skill-factory-publisher-metadata/SKILL.md`	Metadata Management
publisher-release	`skills/skill-factory-publisher-release/SKILL.md`	Publishing Execution

Phase Four: Destruction (1)

Sub-skill	File Path	Responsibility
destroyer	`skills/skill-factory-destroyer/SKILL.md`	Retirement and Destruction

Relationship with skill-lifecycle

All capabilities of skill-lifecycle have been integrated into skill-factory:

Original skill-lifecycle Content	Mapped to skill-factory
scenario-create	Phase One: Production (full process)
scenario-modify	Phase Two: Processing + Phase Three: Publishing
scenario-optimize	Phase Two: Processing (four processors)
scenario-integrate	Phase Two: Processing (integration mode)
scenario-decompose	Phase Two: Processing (split mode)
workflow-generation	One of the output types of Phase One: Production
skill-standards	Phase Two: Processing (normalizer)

Conclusion: skill-factory v10 is a superset of skill-lifecycle; skill-lifecycle can be regarded as an archived historical version.

Version History

Version	Date	Change Description
v10.0.0	2026-05-01	Major version upgrade: integrated skill-lifecycle, added three phases of processing/publishing/destruction, with a total of 13 sub-skills
v9.2.0	2026-04-30	Fixed Mermaid rendering issues
v9.0.0	2026-04-30	Added researcher phase
v7.0.0	2026-04-30	Introduced four-dimensional classification system

About this skill

Task Objective

Factory Panoramic Architecture

Four-stage positioning

Four-dimensional classification system (runs through all stages)

Stage One: Production

Sub-skill index

Typical scenario mapping

Phase 2: Processing

2.1 Enricher

2.2 Simplifier

2.3 Beautifier

2.4 Standardizer

2.5 Special Processing Modes

Assembly

Disassembly

Typical scenario mapping

Phase Three: Publishing

3.1 Version Manager

3.2 Metadata Manager

3.3 Release Publisher

Typical scenario mapping

Phase Four: Destruction

Destruction process

Deprecated template

Typical scenario mapping

Scenario Quick Routing

Index of All Sub-skills

Phase One: Production (5)

Phase Two: Processing (4)

Phase Three: Publishing (3)

Phase Four: Destruction (1)

Relationship with skill-lifecycle

Version History