GitHub Agent Skill Repository Popularity
GitHub stars describe a repository, not every Skill stored inside it. This chart deduplicates repositories first, then shows how many fixed Skill records SkillVetAI currently indexes from each source.
- 01repositoryGitHub source · 18 indexed Skills
anthropics/skills
Sample: academy-guide, algorithmic-art, brand-guidelines, canvas-design, claude-api
- Stars
- 196,267
- Forks
- 23,035
- Open issues
- 1,549
- 02repositoryGitHub source · 9 indexed Skills
vercel-labs/agent-skills
Sample: deploy-to-vercel, vercel-cli-with-tokens, vercel-composition-patterns, vercel-optimize, vercel-react-best-practices
- Stars
- 34,243
- Forks
- 2,986
- Open issues
- 199
- 03repositoryGitHub source · 278 indexed Skills
openai/plugins
Sample: accessibility-and-inclusive-visualization, adobe-batch-edit-photos, adobe-create-mockups, adobe-create-social-variations, adobe-design-from-template
- Stars
- 7,980
- Forks
- 1,034
- Open issues
- 47
How to interpret repository popularity
Stars can reflect visibility, community interest, a broader product, documentation, or many assets beyond a single Skill. Forks and issues are also repository-level activity signals rather than package quality scores.
SkillVetAI records the canonical repository, fixed commit, Skill path, file inventory, and current release hash separately. Open a Package record when you need evidence about one exact Skill.
Natural positions use repository stars, then forks, then repository name as a stable tie-break. Sponsorship cannot alter this order.