保持代理技能并具备函数式编程的纪律。

中文版 README

功能技能是一种工程方法论，设计用于复杂的技能维护和迭代。 结合跟踪日志和单元测试，使技能模块化、可追踪且可测试：

• 将每个Step视为带有显式Input/Output的Function（先纯函数）
• SKILL.md 只协调 Function 的流水线，只消耗 external inputs 和 reference dependencies
• 跨Function的共享规则进入references/
• 由Function调用的确定性逻辑变为scripts/
• 为每个本地运行的Function添加跟踪日志，记录输入/输出/令牌消耗/持续时间
• 为每个Function配备单元测试和端对端测试，确保既不涉及单个函数，也不涉及完整流水线回归

快速启动

安装

通过 skills.sh 安装。添加 -a 以针对一个代理;仅在支持全局安装时添加 -g。

---

用途

创建——工作流程简报中的新功能：

迁移——将现有的旧技能目录转换为功能性技能：

迁移通道显示了整个技能包——“技能。

Functional Skill Creator

Maintain Agent Skills with functional programming discipline.

中文版 README

Functional Skill is an engineering methodology, designed for complex Skill maintenance and iteration. Combined with trace logging and unit testing, it makes Skills modular, traceable, and testable:

• Treat each Step as a Function with explicit Input/Output (pure function first)
• SKILL.md only orchestrates the pipeline of Functions, consuming only external inputs and reference dependencies
• Shared rules across Functions go into references/
• Deterministic logic called by Functions becomes scripts/
• Add trace logging for every Function, running locally, recording input/output/token consumption/duration
• Equip every Function with unit tests and E2E tests, ensuring neither individual Functions nor the full pipeline regress

Quick Start

Install

npx skills add AGI-comming/functional-skill-creator --skill fskill-creator -y

Install via skills.sh. Add -a to target one agent; add -g only if it supports global install.

---

Usage

Create — new functional skill from a workflow brief:

/fskill-creator create a functional skill for 

Migrate — convert an existing legacy skill directory into a functional skill:

/fskill-creator migrate 

The migrate lane reads the whole skill package — SKILL.md, references/, scripts/, and other companion files — not a single markdown file in isolation.

Optional: include_report, include_unittest, include_viewers (on by default; set to false to skip).

Why

Your Skill is getting bloated.

As your Skill’s capabilities iterate, your SKILL.md and references/*.md grow longer, rules pile up, edge cases get patched ever more finely — slowly turning into an unmaintainable wall of prose.

A typical example is when everything keeps getting stuffed into a handful of markdown files:

Before: monolithic prose wall

flowchart TB
  subgraph mono["Monolithic Skill — tangled dependencies"]
    SKILL["SKILL.mdGoal · Workflow · Rules · Output · Known issues"]
    W["Workflow + Step 1.5 patch"]
    RL["Rules · edge cases · stop rules"]
    OUT["Output handler · validation"]

    RULES["references/rules.mdTerms · policies · snippets"]
    EX["references/examples.mdSuccess · failures · workarounds"]

    S1["parse_input.js"]
    S2["parse_input_new.js"]
    S3["fix_edge_case_once.sh"]
    S4["migrate_old_do_not_delete.js"]
  end

  SKILL  W
  SKILL  RL
  W  RL
  RL  OUT
  SKILL  RULES
  RULES  EX
  EX  W
  OUT  EX
  W --> S1
  RL --> S2
  S1  S2
  S2 --> S3
  S3  EX
  OUT --> S4
  S4  SKILL
  S3  RL
  S1 --> OUT

  style mono fill:#fff5f5,stroke:#c53030
  style SKILL fill:#fde8e8,stroke:#c53030
  style W fill:#fde8e8,stroke:#c53030