惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
H
Help Net Security
云风的 BLOG
云风的 BLOG
Apple Machine Learning Research
Apple Machine Learning Research
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Hugging Face - Blog
Hugging Face - Blog
博客园_首页
D
Docker
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Blog — PlanetScale
Blog — PlanetScale
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
GbyAI
GbyAI
博客园 - Franky
B
Blog RSS Feed
Stack Overflow Blog
Stack Overflow Blog
L
LangChain Blog
量子位
V
Visual Studio Blog
Y
Y Combinator Blog
小众软件
小众软件
N
Netflix TechBlog - Medium
博客园 - 三生石上(FineUI控件)
Microsoft Security Blog
Microsoft Security Blog
雷峰网
雷峰网

Mintlify Blog

22 UX improvements to the web editor Introducing the Mintlify Help Center Starter Kit Introducing the collaborative editor built for teams and agents Workflows, rebuilt Is your documentation agent-ready? Mintlify raises $45M Series B led by Andreessen Horowitz and Salesforce Ventures 5 things you didn't know you could do in the Mintlify web editor The improved Mintlify CLI Docs on autopilot: From zero to self-maintaining with Mintlify The state of agent traffic in documentation (March 2026) How we built a virtual filesystem for our Assistant We Replaced Our Internal Wiki With a Slack Bot. You Should Too. 8 ways teams use Mintlify to keep docs updated automatically Documentation is your AI interface What three years of watching AI in production taught us Bridging two JSX runtimes: How we solved Astro's React children problem AI agents are shipping faster than anyone can document Knowledge management systems for technical teams Workflows: Automate documentation maintenance Mintlify acquires Helicone to redefine AI knowledge infrastructure Why more product managers are switching to Mintlify Auto-generating documentation sites from GitHub repos Your docs, your frontend, our content engine Take control of your documentation system Almost half your docs traffic is AI, time to understand the agent experience @mintlify for better docs, faster Mintlify for Enterprise Real llms.txt examples from leading tech companies (and what they got right) Mintlify + Claude Opus 4.6: Powering AI-native knowledge management Declaring Clankruptcy: An experiment in agent orchestration
skill.md: An open standard for agent skills
Michael Ryaboy · 2026-01-21 · via Mintlify Blog

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.

Update: Automatic Skills Discovery

You no longer need to point directly to the skill.md file. Just provide your docs URL and the skills CLI will automatically discover and install:

npx skills add https://mintlify.com/docs

Skills discovery in action

Deprecating install.md

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.

Why do skills matter?

Agents have access to all your documentation, yet they often write horrible code.

This isn't because models are unintelligent—with 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 see skill.md providing the most value. With the right up to date context, the quality of code produced by agents is massively improved. Mintlify regenerates the skill.md file every time you update your docs so it always contains the latest information.

Skill.md is the information you want agents to always have when working with your product. This can include personal taste, capabilities, limitations, and best practices. Documentation usually scatters this across dozens of pages, or skips it entirely because it would overwhelm or be irrelevant to human readers. Skill.md consolidates it for agents.

The spec is flexible, so here's what worked for us.

Decision tables for tribal knowledge

Instead of describing every component, we use tables:

NeedUse
Hide optional details<Accordion>
Sequential instructions<Steps>
Code in multiple languages<CodeGroup>

Agents often struggle making intelligent choices. If there are choices you can confidently make for them, you'll reduce their rate of error.

Explicit boundaries

We separate "what agents can configure" (redirects, SEO settings) from "requires dashboard setup" (custom domains, DNS). This prevents agents from attempting impossible tasks.

Gotchas section

Ours includes things like "Never use mint.json—it's deprecated, only use docs.json" and "Every MDX file needs a title at minimum." These are mistakes agents make repeatedly without explicit guidance.

The skill.md is a cheat sheet, and not a replacement for docs. We point to the full documentation via llms.txt for anything that needs more context.

For another approach, see the Vercel web design guidelines. It's written in a concise style that's not ideal for human browsing, but excellent for agents.

You can see our full skill.md here.

Skill.md lives at /.well-known/skills/default/skill.md. On Mintlify, we also serve it at /skill.md for convenience.

Humble ask from us, if you're a builder and Mintlify user, copy your autogenerated skill file into your repository. Make any updates to your personal taste about how best to use your tool. We will learn from your expertise to improve our generative agent over time.

We look forward to seeing how the standard evolves.