Ai-Agent-Skills curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful `whyHere` notes, and create a starter pack once the first pass is solid.
git clone https://github.com/MoizIbnYousaf/Ai-Agent-Skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/MoizIbnYousaf/Ai-Agent-Skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/curate-a-team-library" ~/.claude/skills/moizibnyousaf-ai-agent-skills-curate-a-team-library && rm -rf "$T"
skills/curate-a-team-library/SKILL.mdCurate 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.
First Move
Start with a managed workspace.
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
Shelf System
Use these 5 work areas as the shelf system:
: web UI, browser work, design systems, visual polishfrontend
: APIs, data, security, infrastructure, runtime systemsbackend
: iOS, Android, React Native, Expo, device testing, app deliverymobile
: docs, testing, release work, files, research, planningworkflow
: prompts, evals, tools, orchestration, agent runtime designagent-engineering
Map the user's stack to shelves before adding anything.
- Example:
maps toReact Native + Node backend
+mobile
.backend - Add
only when testing, release, docs, or research are real parts of the job.workflow - Add
only when the team is doing AI features, prompts, evals, or tooling.agent-engineering - Make sure the first pass covers every primary shelf the user explicitly named.
Discovery Loop
Browse before curating.
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.
Mutation Rules
Keep the first pass small: around 3 to 8 skills.
- Use
first for bundled picks and simple GitHub imports.add - Use
when you want an upstream entry without copying files intocatalog
.skills/ - Use
only for true house copies the team wants to edit or own locally.vendor
Every mutation must include explicit curator metadata like
--area, --branch, and --why.
Good branch names:
React Native / UIReact Native / QANode / APIsNode / DataDocs / Release
Bad branch names:
stuffmiscnotes
Writing Good whyHere
whyHerewhyHere 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.
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
Collections
After the library has about 5 to 8 solid picks, create a
starter-pack collection.
- Use
while adding new skills.--collection starter-pack - Or use
for existing entries.npx ai-agent-skills curate <skill> --collection starter-pack - Keep the collection small and onboarding-friendly.
Sanity Check
Before finishing:
npx ai-agent-skills list --area <work-area> npx ai-agent-skills collections npx ai-agent-skills build-docs
- Run
for each primary shelf you touched.list --area - If you created
, confirm the install command looks right.starter-pack - Make sure the final shelf mix still matches the user's actual stack.
Finish
Return:
- what you added
- which shelves you used and why
- which skills are featured
- what
contains, if you created onestarter-pack - whether the library is local-only or ready to share