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.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly written, highly actionable workflow skill with concrete commands, a clear sequence, and an explicit final validation checkpoint. No improvements needed on the scored dimensions.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence: no concept padding, direct commands, and good/bad examples that earn their tokens rather than describing what a skills library is.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands throughout — `npx ai-agent-skills init-library <name>`, `list --area`, `build-docs` — plus concrete flags like `--area`, `--branch`, `--why`, `--collection`.	3 / 3
Workflow Clarity	Clear sequenced flow (First Move → Shelf System → Discovery → Mutation → Sanity Check → Finish) with an explicit validation checkpoint section "Before finishing" that re-runs `list`, `collections`, and `build-docs`.	3 / 3
Progressive Disclosure	No external reference bundle exists or is needed; the body is a single coherent workflow organized into well-signaled sections with no nested references, satisfying the simple-skill allowance.	3 / 3
	Total	12 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with concrete actions, explicit "Use when" trigger guidance, and a clearly distinct niche. Its main weakness is limited variation in natural trigger terms.

Suggestions

Broaden trigger-term coverage with alternate phrasings users might say (e.g., "curate a skills library", "organize team skills", "team skill shelf").

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Map work to shelves, browse before curating, write meaningful `whyHere` notes, and create a starter pack" — matching the top anchor for specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (map to shelves, browse, write whyHere, build a starter pack) and when ("Use when building a managed team skills library for a real stack"), matching the anchor requiring both.	3 / 3
Trigger Term Quality	The single natural trigger "Use when building a managed team skills library for a real stack" is relevant, but it offers only one phrasing rather than good coverage of common variations a user might say.	2 / 3
Distinctiveness Conflict Risk	Distinct niche vocabulary — "managed team skills library", "shelves", "whyHere", "starter pack" — makes it unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: MoizIbnYousaf/Ai-Agent-Skills
Path: skills/curate-a-team-library/SKILL.md
Commit: 039ad59

Reviewed: about 6 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.