skill-curation

Evaluates, vets, and adopts agent skills via catalog lookup, rubric scoring, and vendor pinning.

Updated Apr 8, 2017
One-click install
npx skills add https://github.com/localmin/dotfiles --skill skill-curation-localmin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-curation
Source: https://github.com/localmin/dotfiles/tree/main/coding-agents/skills/skill-curation
Command: npx skills add https://github.com/localmin/dotfiles --skill skill-curation-localmin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing which agent skills to add to a dotfiles environment is ad-hoc and risky: skills consume context, may overlap with existing ones, and come from sources of varying quality. This meta-skill provides a disciplined find-evaluate-adopt pipeline so skills are added deliberately rather than impulsively. ## Core Features & Use Cases - Catalog-first lookup: Checks a curated, pre-vetted catalog (references/catalog.md) matched to the environment's stack (Astro/Svelte/TS, C/C++, Python, CTF/security) before searching external sources. - Tiered cross-source search: Searches prioritized GitHub sources (anthropics/skills, skill registries, awesome-lists) only when the catalog misses, with a 7-axis rubric covering fit, non-redundancy, maintenance, license, frontmatter, body quality, and footprint. - Mandatory eval gate and vendored adoption: Requires waxa eval convergence before adoption, then pins accepted skills by commit SHA in coding-agents/vendor/manifest.tsv instead of using APM. - Use Case: When you ask "is there a skill for Playwright testing?", it checks the catalog, proposes the vetted candidate with its install line, and stops—avoiding unvetted wild searches. ## Quick Start Ask the agent to find and evaluate a skill for a specific task, for example whether a Playwright testing skill should be adopted into this environment.

Frequently Asked Questions about skill-curation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate a skill before adopting it?

Apply the 7-axis rubric covering fit, non-redundancy, maintenance activity, license, frontmatter validity, body quality, and footprint. Then run the waxa eval gate until it converges with zero unclear results twice in a row before pinning the skill.

How do I find agent skills on GitHub?

Check the curated catalog first, then search tiered sources in order: anthropics/skills and official plugin marketplaces, then registries like claude-skill-registry and awesome-agent-skills, and finally GitHub topic searches sorted by update date rather than stars.

Should I use APM or vendoring to install skills?

This environment uses vendoring, not APM. Add a REPO/PIN/LICENSE block and skill line to coding-agents/vendor/manifest.tsv, run fetch.sh to retrieve the payload, then install.sh to symlink it across all CLIs.

Why must skills be pinned to a commit SHA?

Floating refs like main or HEAD are forbidden because they can change after evaluation. Pinning the exact commit SHA that passed the waxa eval guarantees the adopted skill is the version that was actually vetted.

When should I not add a new skill?

Skip skill creation for one-off tasks that can be solved inline, and reject candidates that overlap with already-installed skills even if they fit the task. Rejections are recorded in references/rejection-log.md to avoid re-evaluating the same candidates.