skill-evolution-manager

kkkkhazix/khazix-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/kkkkhazix/khazix-skills --skill skill-evolution-manager
0 commentsdiscussion
summary

这是整个 AI 技能系统的“进化中枢”。它不仅负责优化单个 Skill,还负责跨 Skill 的经验复盘和沉淀。

skill.md

Skill Evolution Manager

这是整个 AI 技能系统的“进化中枢”。它不仅负责优化单个 Skill,还负责跨 Skill 的经验复盘和沉淀。

核心职责

  1. 复盘诊断 (Session Review):在对话结束时,分析所有被调用的 Skill 的表现。
  2. 经验提取 (Experience Extraction):将非结构化的用户反馈转化为结构化的 JSON 数据(evolution.json)。
  3. 智能缝合 (Smart Stitching):将沉淀的经验自动写入 SKILL.md,确保持久化且不被版本更新覆盖。

使用场景

Trigger:

  • /evolve
  • "复盘一下刚才的对话"
  • "我觉得刚才那个工具不太好用,记录一下"
  • "把这个经验保存到 Skill 里"

工作流 (The Evolution Workflow)

1. 经验复盘 (Review & Extract)

当用户触发复盘时,Agent 必须执行:

  1. 扫描上下文:找出用户不满意的点(报错、风格不对、参数错误)或满意的点(特定 Prompt 效果好)。
  2. 定位 Skill:确定是哪个 Skill 需要进化(例如 yt-dlpbaoyu-comic)。
  3. 生成 JSON:在内存中构建如下 JSON 结构:
    {
      "preferences": ["用户希望下载默认静音"],
      "fixes": ["Windows 下 ffmpeg 路径需转义"],
      "custom_prompts": "在执行前总是先打印预估耗时"
    }
    

2. 经验持久化 (Persist)

Agent 调用 scripts/merge_evolution.py,将上述 JSON 增量写入目标 Skill 的 evolution.json 文件中。

  • 命令: python scripts/merge_evolution.py <skill_path> <json_string>

3. 文档缝合 (Stitch)

Agent 调用 scripts/smart_stitch.py,将 evolution.json 的内容转化为 Markdown 并追加到 SKILL.md 末尾。

  • 命令: python scripts/smart_stitch.py <skill_path>

4. 跨版本对齐 (Align)

skill-manager 更新了某个 Skill 后,Agent 应主动运行 smart_stitch.py,将之前保存的经验“重新缝合”到新版文档中。

核心脚本

  • scripts/merge_evolution.py: 增量合并工具。负责读取旧 JSON,去重合并新 List,保存。
  • scripts/smart_stitch.py: 文档生成工具。负责读取 JSON,在 SKILL.md 末尾生成或更新 ## User-Learned Best Practices & Constraints 章节。
  • scripts/align_all.py: 全量对齐工具。一键遍历所有 Skill 文件夹,将存在的 evolution.json 经验重新缝合回对应的 SKILL.md。常用于 skill-manager 批量更新后的经验还原。

最佳实践

  • 不要直接修改 SKILL.md 的正文:除非是明显的拼写错误。所有的经验修正应通过 evolution.json 通道进行,这样可以保证在 Skill 升级时经验不丢失。
  • 多 Skill 协同:如果一次对话涉及多个 Skill,请依次为每个 Skill 执行上述流程。
how to use skill-evolution-manager

How to use skill-evolution-manager on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add skill-evolution-manager
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/kkkkhazix/khazix-skills --skill skill-evolution-manager

The skills CLI fetches skill-evolution-manager from GitHub repository kkkkhazix/khazix-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/skill-evolution-manager

Reload or restart Cursor to activate skill-evolution-manager. Access the skill through slash commands (e.g., /skill-evolution-manager) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.461 reviews
  • Dhruvi Jain· Dec 24, 2024

    Solid pick for teams standardizing on skills: skill-evolution-manager is focused, and the summary matches what you get after install.

  • Kwame Sharma· Dec 20, 2024

    Useful defaults in skill-evolution-manager — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Maya Reddy· Dec 20, 2024

    Registry listing for skill-evolution-manager matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Kwame Abebe· Dec 12, 2024

    skill-evolution-manager is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Maya Sethi· Dec 4, 2024

    We added skill-evolution-manager from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Hana Khan· Nov 23, 2024

    Solid pick for teams standardizing on skills: skill-evolution-manager is focused, and the summary matches what you get after install.

  • Oshnikdeep· Nov 15, 2024

    We added skill-evolution-manager from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Aditi Chawla· Nov 11, 2024

    Registry listing for skill-evolution-manager matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Charlotte Kim· Nov 11, 2024

    Useful defaults in skill-evolution-manager — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Maya Sharma· Oct 14, 2024

    skill-evolution-manager has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 61

1 / 7