Skill.md: An open standard for agent skills

https://news.ycombinator.com/rss Hits: 1
Summary

All Mintlify documentation sites now contain a /.well-known/skills/default/skill.md file at their base URL. In accordance with the Cloudflare RFC, agentskills proposal, and Vercel skills CLI. Skill files can be installed into 20+ major coding agents including Claude Code, OpenCode, and Cursor via Vercel's skills CLI. If you are a Mintlify user, you can replace the autogenerated skill.md file with your own by placing a skill.md file in the root of the git repository behind your project. You may want to do this if you have specific tastes which were not captured by our agent. Last Friday we announced install.md and it didn't see much adoption. We think skills are a better fit for the use case. They contain both installation and usage knowledge which agents can use more consistently. Most importantly, there's more momentum behind skills. Agents have access to all your documentation, yet they often write horrible code. This isn't because models are unintelligent鈥攚ith perfect context they excel in most tasks. It's because documentation is largely written for humans, and humans can't look at a block of text containing every feature and best practice and instantly apply them. Because of this, features and best practices are spread around our documentation for the human to consume as they browse. Often they don't go into much detail because it needs to be digestible to users with varied levels of technical understanding. Large language models have a different limitation. While they can understand content of arbitrary technical complexity, they can't hold massive amounts of tokens (like your entire site) in context and still perform at their full capacity. AI is also constantly out of date due to being trained on data from the past, and needs up to date context related to the task. This begs the questions: what information should you always include in the context of an agent so that they can perform to their full capacity? And how do you keep it up to date? This is where we ...

First seen: 2026-01-22 20:45

Last seen: 2026-01-22 20:45