Repository scope · kept separate

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.

  1. 01repository
    GitHub source · 18 indexed Skills

    anthropics/skills

    Sample: academy-guide, algorithmic-art, brand-guidelines, canvas-design, claude-api

    Stars
    173,046
    Forks
    20,545
    Open issues
    1,199
    API source ↗
  2. 02repository
    GitHub 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
    30,726
    Forks
    2,734
    Open issues
    174
    API source ↗
  3. 03repository
    GitHub source · 277 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
    5,324
    Forks
    765
    Open issues
    39
    API source ↗

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.