The WellKnownProvider implements a discovery mechanism for skills using RFC 8615 well-known URIs. It allows organizations to publish a collection of skills at a standardized location on their domain.
Discovery Paths
The provider checks the following paths in order of preference:
https://example.com/.well-known/agent-skills/index.json (Preferred)https://example.com/.well-known/skills/index.json (Legacy fallback)
Supported Index Formats
The provider supports two versions of the index.json schema:
v0.2.0 (Current)
Uses a $schema field pointing to https://schemas.agentskills.io/discovery/0.2.0/schema.json. It uses a single-artifact model where each skill entry provides a url and a digest (SHA-256) for a single file (either a skill-md or an archive).
v0.1.0 (Legacy)
Does not use a $schema field. It uses a directory-based model where each skill entry provides a name and a list of files located within a directory named after the skill.
How it works
When a user provides a URL (e.g., https://example.com/docs), the provider attempts to find the index by probing both the path-relative location (https://example.com/docs/.well-known/agent-skills/index.json) and the root location (https://example.com/.well-known/agent-skills/index.json).