Build with the leaderboard
Discover agent skills and the repositories behind them with a simple, read-only JSON API.
Start with a request
Search published repositories by name, description, or category. No API key is required for these endpoints.
curl "https://www.skillleaderboard.com/api/v1/repositories?q=search&limit=10"Explore the data
GET /api/v1/repositories
Search repository metadata and leaderboard signals. Results follow leaderboard order.
GET /api/v1/skills
Search individual skill names, paths, and repositories in the published catalog. Results are ordered by repository and file path. The response links to the upstream file; it does not include source descriptions or file contents.
curl "https://www.skillleaderboard.com/api/v1/skills?q=research&limit=10"Parameters and responses
Both endpoints accept an optional case-insensitive substring query q (up to 200 characters), limit (1–100, default 25), and offset (0–10000, default 0). Responses include data, total, pagination values, and snapshotDate. Data can change between pages as snapshots update. The offset ceiling limits how far a query can be paged; narrow the query to explore further.
Invalid or repeated parameters return 400; an unavailable, mismatched, or not-yet-enabled developer publication returns 503. Repository responses may be cached for an hour, with stale responses served while revalidating. Skill responses use no-store; publication metadata may take up to 30 seconds to refresh.
Connect an AI assistant
Add https://www.skillleaderboard.com/mcp as a remote MCP server in a client that supports Streamable HTTP. No API key or sign-in is required. The server offers search_repositories and search_skills, using the same query and pagination limits as the API.
https://www.skillleaderboard.com/mcpAsk your assistant to find skills for a task, compare repositories, or look up upstream skill files. These tools only search public catalog metadata; they cannot install skills or change anything. Client setup varies: choose a remote HTTP server, not a local command.
Working with the catalog
The API is read-only and reflects published catalog metadata. A listing is not permission to reuse its source content; check each repository’s license. The existing catalog endpoint remains available for compatibility. The public MCP server exposes the same read-only discovery tools over Streamable HTTP.
See the methodology for how the leaderboard is assembled.