Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
A mechanism for discovering Agent Skills using the .well-known URI path prefix as specified in RFC 8615 for discovering Agent Skills.
| Date | Stars |
|---|---|
| 2026-08-02 | 329 |
| 2026-08-12 | 332 |
| 2026-08-18 | 335 |
| 2026-08-25 | 336 |
| 2026-08-26 | 337 |
| 2026-08-29 | 338 |
| 2026-08-31 | 339 |
| 2026-09-01 | 341 |
| 2026-09-02 | 341 |
| 2026-09-03 | 342 |
| 2026-09-05 | 343 |
| 2026-09-06 | 343 |
| 2026-09-13 | 344 |
| 2026-09-14 | 345 |
| 2026-09-18 | 345 |
| 2026-09-25 | 348 |
| 2026-09-26 | 347 |
| 2026-09-29 | 348 |
| 2026-10-02 | 349 |
| 2026-10-03 | 351 |
| 2026-10-04 | 352 |
| 2026-10-05 | 353 |
| 2026-10-06 | 354 |
| 2026-10-07 | 356 |
| 2026-10-09 | 356 |
| 2026-10-15 | 358 |
| 2026-10-16 | 359 |
| 2026-10-19 | 360 |
| 2026-10-20 | 361 |
| 2026-10-21 | 362 |
| 2026-10-30 | 363 |
| 2026-10-31 | 364 |
| 2026-11-01 | 366 |
| 2026-11-03 | 369 |
| 2026-11-04 | 369 |
Today
— stars today
This week
+7 stars this week
This month
+16 stars this month
Momentum
0.0
growth rate 1.93%/day
# Agent Skills Discovery via Well-Known URIs **Status**: Draft **Version**: 0.2.0 **Published Date**: 2026-01-17 **Updated Date**: 2026-03-12 ## Table of Contents 1. [Abstract](#abstract) 2. [Changelog](#changelog) 3. [Terminology](#terminology) 4. [Problem](#problem) 5. [Solution](#solution) 6. [URI Structure](#uri-structure) 7. [Skill Directory Contents](#skill-directory-contents) 8. [Progressive Disclosure](#progressive-disclosure) 9. [Discovery Index](#discovery-index) 10. [Integrity and Verification](#integrity-and-verification) 11. [Archive Distribution](#archive-distribution) 12. [Examples](#examples) 13. [HTTP Considerations](#http-considerations) 14. [Client Implementation](#client-implementation) 15. [Security Considerations](#security-considerations) 16. [Relationship to Existing Specifications](#relationship-to-existing-specifications) 17. [References](#references) ## Abstract This document defines a mechanism for discovering [Agent Skills](https://agentskills.io/) using the `.well-known` URI path prefix as specified in [RFC 8615](https://datatracker.ietf.org/doc/html/rfc8615). Skills are currently scattered across GitHub repositories, documentation sites, and other sources. A well-known URI provides a predictable location for agents and tools to discover skills published by an organization or project. ## Changelog #### v0.2.0 - rename well-known URI from `/.well-known/skills/` to `/.well-known/agent-skills/` - replace `version` field with `$schema` URI (`https://schemas.agentskills.io/discovery/0.2.0/schema.json`) - replace `files` array and `package` object with a flat single-artifact model: each skill entry now has `type` (`"skill-md"` or `"archive"`), `url`, and `digest` - `digest` is now the SHA-256 of the single artifact (not a manifest-derived skill-level digest) - add archive safety guidance: path traversal, symlinks, decompression bombs - add URL resolution semantics per RFC 3986 - add RFC 2119 / RFC 8174 keyword conventions - strengthen script execution guidance — clients SHALL NOT execute scripts by default - add "Integrity and Verification" section - add "Archive Distribution" section - add backward-compatibility guidance for v0.1.0 clients #### v0.1.0 - initial draft ## Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119) [RFC 8174](https://datatracker.ietf.org/doc/html/rfc8174) when, and only when, they appear in all capitals, as shown here. ## Problem Agent Skills give AI agents domain-specific capabilities through structured instructions, scripts, and resources. Today, discovering skills requires: - Searching GitHub repositories - Reading vendor documentation - Following links shared on social media - Manual configuration by end users There is no standard way to answer: "What skills does example.com publish?" ## Solution Register `agent-skills` as a well-known URI suffix. Organizations can publish skills at: ``` https://example.com/.well-known/agent-skills/ ``` This provides a **single, predictable location** where agents and tooling can discover and fetch skills without prior configuration. ## URI Structure Publishers MUST provide an index at: ``` /.well-known/agent-skills/index.json ``` Each skill in the index includes a `url` field pointing to its artifact. While publishers conventionally host skill files under `/.well-known/agent-skills/`, the `url` field allows skills to be hosted at any location (e.g., on a CDN or at a versioned path). Skill names MUST conform to the [Agent Skills specification](https://agentskills.io/specification): - 1-64 characters - Lowercase alphanumeric and hyphens only (`a-z`, `0-9`, `-`) - MUST NOT start or end with a hyphen - MUST NOT contain consecutive hyphens ## Skill Directory Contents A skill consists of a requir
Excerpt of 22,581 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:048acb691e729117, topic:agents