#skillscategoryauthorprice
skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / how to choose an agent skill
Skill names are short and often overlap, so begin with the task you want done and look in the matching category. For example, SEO and Marketing Skills both cover search work, Testing & QA holds three different A/B testing skills, and Project Management separates guides that describe a workflow from skills that act on a live account.
The directory contains near-duplicates, for instance two Airtable skills built on the same Rube MCP workflow by different authors. When that happens, read the review on each page and choose by fit: the strictest version for high-stakes work, the lightest for a quick check, or the one whose repository you already trust.
The page shows when the source repository was last updated and, where there is activity, its recent commits. A skill that has not changed in a long time is not automatically bad, since some are stable, but a skill that depends on a vendor's API should have been touched recently. Star counts are a weak signal about popularity, not quality.
Skills in the directory are published by their authors under licenses such as MIT or Apache-2.0, which allow reuse with attribution. If a repository has no license, you have no clear right to copy or redistribute it, which is why we link to those skills instead of hosting them.
A skill that does one job well is easier to review and less likely to interfere with others. Be cautious about large collections you do not need, and about two skills whose descriptions overlap, since the agent may pick either.
Install the skill on a branch or in a throwaway project, run it on a small real task and read what it did. If you cannot explain why it behaved as it did, keep reading its instructions or remove it. The install guide and safety checklist cover the practical steps.