Migrate skills discovery from v0.1 to v0.2 (agent-skills-discovery-rfc)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 35
- Forks
- 13
- Avg merge
- 19h 10m
- Merged PRs (30d)
- 22
Description
Context
The Cloudflare Agent Skills Discovery RFC published draft v0.2.0 (PR #8, merged 2026-03-12) with breaking changes from v0.1.
We currently serve a v0.1-style index. We should migrate to v0.2 to stay spec-compliant and benefit from the improvements — notably the required url field, which directly prevents the URL construction failures we've observed (agents guessing wrong filenames instead of using SKILL.md).
What changed in v0.2
| v0.1 (current) | v0.2 | |
|---|---|---|
| Well-known path | /.well-known/skills/ |
/.well-known/agent-skills/ |
| Version field | version |
$schema (URI) |
| Skill entry fields | name, description, files |
name, type, description, url, digest |
files array |
Present | Removed — single artifact per skill |
type |
N/A | Required: "skill-md" or "archive" |
digest |
N/A | Required: sha256:{hex} integrity hash |
Path rename rationale: IANA's RFC 8615 discourages generic well-known paths. "skills" is too broad. Google's A2A had the same issue (agent.json → agent-card.json).
Migration checklist
Endpoints
- Add new endpoints at
/.well-known/agent-skills/index.jsonand/.well-known/agent-skills/{name}/SKILL.md - Update
index.jsonschema: replaceversionwith$schema, addtype,url,digestfields, removefilesarray - Keep
/.well-known/skills/index.jsonalive serving identical content for backwards compatibility (old consumers followurlfields to new paths naturally) - Plan deprecation of old path once external references are updated
llms.txt
- Update index URL to
/.well-known/agent-skills/index.json - Instructions should direct agents to use the
urlfield from the index (already done in current improvements, just needs path update)
Multi-file skills
icp-cli(references) andcanhelp(scripts): usetype: "skill-md"— agents discover references via relative paths in the SKILL.md body. No need fortype: "archive"at this stage.- The
SKILL.zipendpoint can optionally be kept as a convenience but is not required by the spec.
External references to update
- icp-cli docs
llms.txt— see dfinity/icp-cli#478 - icp-cli-templates
AGENTS.md— see dfinity/icp-cli-templates#24 - Any other
llms.txtorAGENTS.mdfiles referencing/.well-known/skills/
Validation
- Ensure
skill-validatorsupports v0.2 index format (or update it) - Verify
npx skills add dfinity/icskillsstill works after migration
Recommended external instructions format
For AGENTS.md and external llms.txt files, the skills section should be:
## Skills
Tested implementation patterns for ICP development are available as agent skills.
1. Fetch the skills index and remember each skill's name, description, and url:
https://skills.internetcomputer.org/.well-known/agent-skills/index.json
2. When a task matches a skill\'s description, use it if already loaded in your
context. Otherwise, fetch the skill content from its url.
Do not construct skill URLs manually.
Example: for the skill named "internet-identity", its url is:
https://skills.internetcomputer.org/.well-known/agent-skills/internet-identity/SKILL.md
If a response contains HTML instead of markdown, the URL is wrong.
3. Skills contain correct dependency versions, configuration formats, and common
pitfalls that prevent build failures.
Always prefer skill guidance over general documentation when both cover the same topic.
Key principles:
- No URL templates (
{name}/{file}) — agents misinterpret these and guess wrong filenames - Direct agents to the
urlfield in the index — machine-readable, no construction needed - Concrete example anchors
SKILL.mdas a literal filename - HTML detection hint helps agents identify wrong URLs (asset canister SPA fallback returns HTML for 404s)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the current /.well-known/skills/index.json and llms.txt references, then compare them with the linked agent-skills-discovery RFC v0.2. Update the new endpoints and index fields, retain the old path for compatibility, and revise external references named in the issue. Run skill-validator and verify that npx skills add dfinity/icskills still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100