Back to Details

curate-a-team-library

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Curate A Team Library

整理团队技能库

Goal

目标

Build a managed skills library that another teammate or agent can actually browse, trust, and install.
Do not hand-edit 
skills.json
, 
README.md
, or 
WORK_AREAS.md
when the CLI already has the mutation you need.
构建一个可供其他团队成员或Agent实际浏览、信任并安装的托管式技能库。
如果CLI已经提供了你需要的变更操作，请勿手动编辑
skills.json
、
README.md
或
WORK_AREAS.md
。

First Move

第一步

Start with a managed workspace.
bash
npx ai-agent-skills init-library <name>
cd <name>
Ask at most 3 short questions before acting:
  • what kinds of work the library needs to support
  • whether the first pass should stay small and opinionated or aim broader
  • whether the output should stay local or end as a shareable GitHub repo
从创建托管工作区开始。
bash
npx ai-agent-skills init-library <name>
cd <name>
行动前最多询问3个简短问题：
  • 该技能库需要支持哪些类型的工作
  • 首轮内容是应该保持小而针对性强，还是覆盖面更广
  • 输出内容是仅保留在本地，还是最终作为可共享的GitHub仓库

Shelf System

分类架体系

Use these 5 work areas as the shelf system:
  • frontend
    : web UI, browser work, design systems, visual polish
  • backend
    : APIs, data, security, infrastructure, runtime systems
  • mobile
    : iOS, Android, React Native, Expo, device testing, app delivery
  • workflow
    : docs, testing, release work, files, research, planning
  • agent-engineering
    : prompts, evals, tools, orchestration, agent runtime design
Map the user's stack to shelves before adding anything.
  • Example: 
    React Native + Node backend
    maps to 
    mobile
    + 
    backend
    .
  • Add 
    workflow
    only when testing, release, docs, or research are real parts of the job.
  • Add 
    agent-engineering
    only when the team is doing AI features, prompts, evals, or tooling.
  • Make sure the first pass covers every primary shelf the user explicitly named.
使用以下5个工作区作为分类架体系：
  • frontend
    ：网页UI、浏览器相关工作、设计系统、视觉优化
  • backend
    ：APIs、数据、安全、基础设施、运行时系统
  • mobile
    ：iOS、Android、React Native、Expo、设备测试、应用交付
  • workflow
    ：文档、测试、发布工作、文件、调研、规划
  • agent-engineering
    ：提示词、评估、工具、编排、Agent运行时设计
添加任何内容前先将用户的技术栈映射到对应分类架。
  • 示例：
    React Native + Node backend
    对应
    mobile
    + 
    backend
  • 仅当测试、发布、文档或调研属于实际工作内容时，才添加
    workflow
    分类架
  • 仅当团队正在开发AI功能、编写提示词、做评估或工具开发时，才添加
    agent-engineering
    分类架
  • 确保首轮内容覆盖用户明确提及的所有主分类架

Discovery Loop

探索流程

Browse before curating.
bash
npx ai-agent-skills list --area <work-area>
npx ai-agent-skills search <query>
npx ai-agent-skills collections
If the user named multiple primary shelves, inspect each one before choosing skills.
整理前先浏览资源。
bash
npx ai-agent-skills list --area <work-area>
npx ai-agent-skills search <query>
npx ai-agent-skills collections
如果用户指定了多个主分类架，选择技能前请逐个检查。

Mutation Rules

变更规则

Keep the first pass small: around 3 to 8 skills.
  • Use 
    add
    first for bundled picks and simple GitHub imports.
  • Use 
    catalog
    when you want an upstream entry without copying files into 
    skills/
    .
  • Use 
    vendor
    only for true house copies the team wants to edit or own locally.
Every mutation must include explicit curator metadata like 
--area
, 
--branch
, and 
--why
.
Good branch names:
  • React Native / UI
  • React Native / QA
  • Node / APIs
  • Node / Data
  • Docs / Release
Bad branch names:
  • stuff
  • misc
  • notes
首轮内容保持精简：约3到8个技能。
  • 对于打包精选内容和简单的GitHub导入，优先使用
    add
  • 如果你想要上游条目但不将文件复制到
    skills/
    目录下，使用
    catalog
  • 仅当团队想要编辑或本地留存真正的内部副本时，才使用
    vendor
每次变更都必须包含明确的整理者元数据，例如
--area
、
--branch
和
--why
。
好的分支名示例：
  • React Native / UI
  • React Native / QA
  • Node / APIs
  • Node / Data
  • Docs / Release
坏的分支名示例：
  • stuff
  • misc
  • notes

Writing Good 
whyHere

编写高质量的
whyHere

whyHere
is curator judgment, not filler.
  • Mention the stack or workflow it supports.
  • Mention the gap it fills in this library.
  • Be honest about why it belongs here.
Good:
Covers React Native testing so the mobile shelf has a real device-validation option.
Bad:
I want this on my shelf.
whyHere
是整理者的判断说明，不是无效填充内容。
  • 说明它支持的技术栈或工作流
  • 说明它填补了该库的哪些空白
  • 如实说明它被收录的原因
好的示例：
覆盖React Native测试场景，因此mobile分类架有了实际的设备验证选项。
坏的示例：
我想把它放在我的分类架里。

Featured Picks

精选推荐

Use 
--featured
sparingly.
  • keep it to about 2 to 3 featured skills per shelf
  • reserve it for skills you would tell a new teammate to install first
谨慎使用
--featured
。
  • 每个分类架保留约2到3个精选技能
  • 仅保留你会建议新团队成员优先安装的技能

Collections

合集

After the library has about 5 to 8 solid picks, create a 
starter-pack
collection.
  • Use 
    --collection starter-pack
    while adding new skills.
  • Or use 
    npx ai-agent-skills curate <skill> --collection starter-pack
    for existing entries.
  • Keep the collection small and onboarding-friendly.
当技能库有了约5到8个稳定的精选内容后，创建一个
starter-pack
合集。
  • 添加新技能时使用
    --collection starter-pack
  • 或者对已有条目使用
    npx ai-agent-skills curate <skill> --collection starter-pack
  • 保持合集精简，适合新手上手

Sanity Check

合理性检查

Before finishing:
bash
npx ai-agent-skills list --area <work-area>
npx ai-agent-skills collections
npx ai-agent-skills build-docs
  • Run 
    list --area
    for each primary shelf you touched.
  • If you created 
    starter-pack
    , confirm the install command looks right.
  • Make sure the final shelf mix still matches the user's actual stack.
完成前：
bash
npx ai-agent-skills list --area <work-area>
npx ai-agent-skills collections
npx ai-agent-skills build-docs
  • 对你操作过的每个主分类架都运行
    list --area
    命令
  • 如果你创建了
    starter-pack
    ，确认安装命令正确无误
  • 确保最终的分类架组合仍然匹配用户的实际技术栈

Finish

收尾

Return:
  • what you added
  • which shelves you used and why
  • which skills are featured
  • what 
    starter-pack
    contains, if you created one
  • whether the library is local-only or ready to share
返回以下内容：
  • 你添加的内容
  • 你使用的分类架及对应原因
  • 精选技能清单
  • starter-pack
    包含的内容（如果你创建了该合集）
  • 该技能库是仅本地可用，还是已准备好共享