Skip to main content
skill CX Codex

curate-a-team-library — Claude Code skill: what it does

curate-a-team-library — a skill for Claude Code, Codex, Cursor and other agents that walks an agent through building a team skills library: mapping shelves, adding entries with curator metadata, assembling a starter pack.

MIT 160 installs ★ 1,161 updated 2026-09-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add MoizIbnYousaf/ai-agent-skills --skill curate-a-team-library -a claude-code
Open on GitHub

What curate-a-team-library does

The skill structures the process in ordered steps: spin up a managed workspace with npx ai-agent-skills init-library <name>, ask the user no more than three questions about their stack, then map work to five shelves — frontend, backend, mobile, workflow, agent-engineering.

The discovery loop runs before any curation: npx ai-agent-skills list --area <work-area> and search first, mutations second. Every add, catalog or vendor call must carry explicit curator metadata — --area, --branch, and --why. The --why value is curator judgment, not filler: it names the stack the skill serves and the gap it fills. First pass stays at 3–8 skills; --featured is reserved for at most 2–3 per shelf.

Once the library reaches 5–8 entries, the skill prompts building a starter-pack collection via --collection starter-pack or npx ai-agent-skills curate. Branch names like “misc” or “stuff” are treated as a process error — the agent reads that as a sign the metadata is wrong.

What it helps with

  • build a team skill library from scratch for a specific stack
  • map skills to named shelves (frontend, backend, mobile and others)
  • attach curator reasoning explaining why each skill belongs in the library
  • assemble an onboarding starter pack for new team members
  • run a sanity check on the library before publishing it as a GitHub repo

Example prompts for the agent

  • Build a team skills library for a React Native and Node stack, map shelves, then create a starter pack
  • Add a mobile testing skill with --branch 'React Native / QA' and a meaningful --why
  • Curate a starter-pack collection from existing library entries and run build-docs

How to install curate-a-team-library

1Skills CLI (Vercel)

npx skills add MoizIbnYousaf/ai-agent-skills --skill curate-a-team-library -a claude-code

2Manually: put the files in place

~/.claude/skills/curate-a-team-library/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/curate-a-team-library/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about curate-a-team-library

How do I install curate-a-team-library in Claude Code?

Run npx skills add MoizIbnYousaf/ai-agent-skills --skill curate-a-team-library -a claude-code. The skill is placed at ~/.claude/skills/curate-a-team-library/SKILL.md.

What does the curate-a-team-library skill do?

It guides an agent through building a managed team skills library — from workspace init through shelf mapping, curator-annotated additions, and starter pack assembly.

Which platforms does curate-a-team-library support?

Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. Each platform has its own install command and SKILL.md path.

Source text

SKILL.md · MIT
---
name: curate-a-team-library
description: 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.
category: workflow
version: 4.1.0
---

# 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.

## 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

## 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.

## 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.

## 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`

## Writing Good `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.`

## 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 `--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.

## 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.

## 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

© MoizIbnYousaf · MIT · MoizIbnYousaf/ai-agent-skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set15

The whole set →
browse-and-evaluate The browse-and-evaluate skill helps you find, compare, and inspect catalog skills before adding them. Use it when catalog output needs to stay focused. CX Codex +1 177installs review-a-skill review-a-skill reviews a skill before it enters a library by checking metadata, structure, safety, and dependencies. Use it when the choice is keep, curate, or remove. CX Codex +1 177installs build-workspace-docs build-workspace-docs keeps README.md and WORK_AREAS.md aligned with a skills catalog. Run it after catalog changes or before committing workspace updates. CX Codex +1 172installs audit-library-health audit-library-health — a skill for diagnosing a skills library: validates structure, finds stale elements, checks documentation sync. Run before publishing or updating. CX Codex +1 170installs update-installed-skills update-installed-skills syncs previously installed agent skills to their upstream versions. Helps you inspect changes safely with dry-run flags before overwriting local setups. CX Codex +1 168installs share-a-library share-a-library — a skill that automates publishing a finished local library to GitHub and generates an install command for your teammates. CX Codex +1 161installs install-from-remote-library install-from-remote-library guides safe skill installs from shared repos. Inspects targets via --list and previews every action with a dry-run flag. CX Codex +1 161installs migrate-skills-between-libraries migrate-skills-between-libraries is a Claude Code skill that moves skills between library workspaces, including when switching from a personal library to a team one. CX Codex +1 158installs

Project sponsors

Companies that keep this analytics open