
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.
- Installs
- 158
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/moizibnyousaf/ai-agent-skills --skill curate-a-team-library- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads curate-a-team-library automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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.
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 polishbackend: APIs, data, security, infrastructure, runtime systemsmobile: iOS, Android, React Native, Expo, device testing, app deliveryworkflow: docs, testing, release work, files, research, planningagent-engineering: prompts, evals, tools, orchestration, agent runtime design
Map the user's stack to shelves before adding anything.
- Example:
React Native + Node backendmaps tomobile+backend. - Add
workflowonly when testing, release, docs, or research are real parts of the job. - Add
agent-engineeringonly 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.
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
addfirst for bundled picks and simple GitHub imports. - Use
catalogwhen you want an upstream entry without copying files intoskills/. - Use
vendoronly 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 / UIReact Native / QANode / APIsNode / DataDocs / Release
Bad branch names:
stuffmiscnotes
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-packwhile adding new skills. - Or use
npx ai-agent-skills curate <skill> --collection starter-packfor existing entries. - 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
list --areafor 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-packcontains, if you created one - whether the library is local-only or ready to share
FAQ
What does the curate-a-team-library skill do?
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.
How do I install curate-a-team-library?
Run npx skills add https://github.com/moizibnyousaf/ai-agent-skills --skill curate-a-team-library in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/curate-a-team-library/ (personal) or .claude/skills/curate-a-team-library/ (project).
Which AI agents can use curate-a-team-library?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is curate-a-team-library safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains curate-a-team-library?
It is published by moizibnyousaf in moizibnyousaf/ai-agent-skills. It has 158 recorded installs.
More from moizibnyousaf/ai-agent-skills
code-review
moizibnyousaf/ai-agent-skills
Automated code review for pull requests using specialized review patterns. Analyzes code for quality, security, performance, and best practices. Use when reviewing code changes, PRs, or doing code audits.
backend-development
moizibnyousaf/ai-agent-skills
Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.
database-design
moizibnyousaf/ai-agent-skills
Database schema design, optimization, and migration patterns for PostgreSQL, MySQL, and NoSQL databases. Use for designing schemas, writing migrations, or optimizing queries.
code-refactoring
moizibnyousaf/ai-agent-skills
Code refactoring patterns and techniques for improving code quality without changing behavior. Use for cleaning up legacy code, reducing complexity, or improving maintainability.
code-documentation
moizibnyousaf/ai-agent-skills
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
best-practices
moizibnyousaf/ai-agent-skills
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available