How we curate
Methodology
Every signal on AgenticSkills is either verifiable against a primary source (GitHub) or labeled as editorial judgment. We do not fabricate metrics. This page is the long-form version of that promise.
What we show on every skill
Every skill page surfaces four kinds of signal. Each one has a primary source you can verify yourself.
Per-path last commit
Fetched from the GitHub commits API filtered to the skill's specific subdirectory. Solves the monorepo problem: anthropics/skills contains dozens of skills with different commit histories, and we show each one's actual freshness.
Source: GitHub commits API · path filter
Recent contributors
Unique author logins from the 100 most recent commits to the skill's path. Optimized for 'who is currently maintaining this' rather than lifetime contribution count.
Source: GitHub commits API · deduped authors
Stars · source repo
Stars on the GitHub repository the skill lives in. For monorepo skills this number is shared across all skills in that repo — we label it 'source repo' in the UI to make the scope clear.
Source: GitHub repo API · stargazers_count
Verified org badge
A binary indicator showing the GitHub org has been cross-checked against the company's official identity. Applies to the org, not to individual skill quality.
Source: Editorial — see Verified orgs section below
What we deliberately don't show
Install counts
Install counts cannot be independently measured by anyone outside the agent platform itself. Anthropic could tell you how many people installed a Claude skill; we can't. The skill ecosystem at large — GitHub, the major install CLIs (npx skills, openskills) — does not surface this number either, because nobody can.
We previously displayed install counts seeded from editorial judgment. We removed them entirely in May 2026 because the first question anyone reasonable would ask is "how do you know?" — and we did not have a credible answer. Stars, commits, and contributors are imperfect proxies for usage, but they are verifiable, and we'd rather show a smaller set of real numbers than a larger set of made-up ones.
If Anthropic or another platform ever publishes per-skill install telemetry through an official API, we'll integrate it and label it accordingly.
Editorial quality ranks
Quality ranks are editorial. They reflect our judgment about a skill's value to developers, not a popularity score derived from data. We label them as editorial in the UI so the distinction is clear.
Featured pick
Maintained by a verified org, exemplifies SKILL.md best practices, and (where applicable) appears in at least one workflow stack.
High quality
Clear documentation, recent maintenance, fits cleanly into common workflows. Solid choice in most contexts.
Functional
Works as advertised but with lower editorial confidence — narrow scope, less maintenance signal, or partial documentation.
Verified orgs program
A verified org has had its GitHub identity cross-checked against the company's official website, public communications, or staff GitHub profiles. The badge means "we believe this is really {Vercel Labs, Anthropic, Trail of Bits, etc.}" — not that every file in their repo is high quality.
Currently 131 skills come from verified orgs across the directory. See the full list at /authors.
If you maintain an org and want it verified, email hello@agenticskills.io from a domain that matches your GitHub org's public identity.
How skills enter the catalog
- Discovery. Editors track GitHub topics (
agent-skills,claude-skills), platform marketplaces, and community signals (Reddit, X). Anyone can also submit at /submit. - Review.We check that the skill has a published SKILL.md, an accessible source repo, a discernible scope, and that the author identity is real. Skills that don't pass these checks are declined; no listing fee, no expedited review.
- Classification. Editors assign a category, platforms, and an editorial rank.
- Continuous refresh. Per-path commit data, contributor count, and repo stars are refreshed by an automated script (
scripts/refresh-skill-stats.ts) against the GitHub API. The freshness date in the navbar reflects the most recent refresh. - Delisting. A skill is removed if its source repo disappears, the author requests removal, or a credible security finding goes unaddressed. See /incidents for the public incident log.
Watchers & auditors
We continuously monitor curated skills and MCP servers for security findings, source-repo disappearance, and license changes. The MCP audit framework currently surfaces results on every /mcp server page; the skill audit equivalent is being wired in.
Our model is "continuous monitoring of a curated set" rather than "one-time scan of every public skill." A directory that has scanned every skill once tells you about historical state. We tell you about current state on the skills that matter.
Found a problem?
If any number on the site looks wrong, or you suspect a skill should be delisted, email hello@agenticskills.io or use the "Report this skill" button on the skill page. Public incident log: /incidents.