skill

Skill-building tooling for the skill package. Build AI agent skills for any Python package by analyzing its code, tests, and docs. Use this skill when the user wants to create skills for a package, analyze a codebase to suggest what skills would be useful, generate SKILL.md files from existing code/tests/docs, or when someone says things like "make skills for this package", "what skills should this project have", "create a skill from this module", or "generate skills". Also trigger when the user points at a package and asks for AI-powered interfaces to it.

Skill documentation tooling for the skill package. Document a project's AI agent skills in the README and other formats. Use this skill when the user wants to add skills documentation to a README, explain what skills a project offers, write a "Skills" section, generate skill installation instructions, or when asked things like "document the skills", "add skills to the README", "how should I present skills to users", or "write skill usage examples". Also trigger when updating a README for a package that has skills in .claude/skills/ or {pkg}/data/skills/.

Ship a Python package's AI agent skills with `pip install` — and decide WHICH skills to ship. Use when the user asks how to include skills in their package distribution, make skills available after `pip install`, ship SKILL.md files with their package, set up `{pkg}/data/skills/`, configure package-data, add a skills installer/convenience function, or says "how do users get my skills after pip install", "ship skills with my package", "distribute skills", "package skills", or "enable skills in my library". Also trigger when working on pyproject.toml and the project has skills to distribute. The overall layout decision (where real files live, the `.claude/skills/` symlink bridge, spec compliance) is owned by **skill-package-setup**; this skill covers the pip-distribution mechanics and audience classification.

Skill management tooling for the skill package. Search, list, inspect, and manage AI agent skills across agents and projects. Use this skill when the user wants to find skills, see what skills are installed, check where skills are linked, inspect a skill's contents, install or uninstall skills, compare skills across agents (Claude Code, Cursor, Copilot), or says things like "what skills do I have", "find a skill for X", "show me the skill", "where are my skills", "install this skill", "remove that skill", "list skills", or "search skills". Trigger on any skill inventory, discovery, or housekeeping request.

Canonical, agent-agnostic policy for WHERE a package's AI agent skills live and HOW they are distributed so they're discoverable by `gh skill` (and any agent host — Copilot, Cursor, Codex, Gemini, Claude) AND, where wanted, shipped with `pip install`. Use this skill to set up skills for a new package, migrate an existing repo to the canonical layout, consolidate skills scattered across `.claude/skills/` / `skills/` / `{pkg}/data/skills/`, make every SKILL.md spec-clean, or answer "where should my package's skills live". Also the authority other skills defer to (e.g. wads-skillify). Triggers on "set up skills", "where should skills live", "make skills gh-skill installable", "migrate/restructure the skills layout", "skillify this repo". Maintainer skill.

Skill maintenance tooling for the skill package. Keep AI agent skills in sync with their source package code. Use this skill when a package's code, API, or behavior has changed and its skills may be outdated, when the user says "update the skills", "skills are stale", "sync skills with code", "refresh skills", or when you notice that skill instructions reference functions/classes/patterns that no longer exist in the codebase. Also use after major refactors, API changes, or version bumps.