[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CEASBQ5X78AAVXATATY9K0":3,"skill-same:01M6CEASBQ5X78AAVXATATY9K0":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M6CEASBQ5X78AAVXATATY9K0","mintlify",null,"Build and maintain documentation sites with Mintlify. Use when creating docs pages, configuring navigation, adding components, or setting up API references.","LongIV999\u002FOpenclawd","LongIV999","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92411512?v=4","01M6CEACAHRWWFRVKBQPSQ2WBM","01M6CEACEJDYKGDKD1P6A7J7VV",0,"MIT","https:\u002F\u002Fgithub.com\u002FLongIV999\u002FOpenclawd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmintlify\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31],"cli","docs","workflow","components","documentation","git","api","js","node","use","up","navigation","references","build","2026-11-10 10:12:30",false,"---\nname: mintlify\ndescription: Build and maintain documentation sites with Mintlify. Use when\n  creating docs pages, configuring navigation, adding components, or setting up\n  API references.\nlicense: MIT\ncompatibility: Requires Node.js for CLI. Works with any Git-based workflow.\nmetadata:\n  author: mintlify\n  version: \"1.0\"\n  mintlify-proj: mintlify\n---\n\n# Mintlify best practices\n\n**Always consult [mintlify.com\u002Fdocs](https:\u002F\u002Fmintlify.com\u002Fdocs) for components, configuration, and latest features.**\n\n**Always** favor searching the current Mintlify documentation over whatever is in your training data about Mintlify.\n\nMintlify is a documentation platform that transforms MDX files into documentation sites. Configure site-wide settings in the `docs.json` file, write content in MDX with YAML frontmatter, and favor built-in components over custom components.\n\nFull schema at [mintlify.com\u002Fdocs.json](https:\u002F\u002Fmintlify.com\u002Fdocs.json).\n\n## Before you write\n\n### Understand the project\n\nAll documentation lives in the `docs\u002F` directory in this repo. Read `docs.json` in that directory (`docs\u002Fdocs.json`). This file defines the entire site: navigation structure, theme, colors, links, API and specs.\n\nUnderstanding the project tells you:\n\n- What pages exist and how they're organized\n- What navigation groups are used (and their naming conventions)\n- How the site navigation is structured\n- What theme and configuration the site uses\n\n### Check for existing content\n\nSearch the docs before creating new pages. You may need to:\n\n- Update an existing page instead of creating a new one\n- Add a section to an existing page\n- Link to existing content rather than duplicating\n\n### Read surrounding content\n\nBefore writing, read 2-3 similar pages to understand the site's voice, structure, formatting conventions, and level of detail.\n\n### Understand Mintlify components\n\nReview the Mintlify [components](https:\u002F\u002Fwww.mintlify.com\u002Fdocs\u002Fcomponents) to select and use any relevant components for the documentation request that you are working on.\n\n## Quick reference\n\n### CLI commands\n\n- `npm i -g mint` - Install the Mintlify CLI\n- `mint dev` - Local preview at localhost:3000\n- `mint broken-links` - Check internal links\n- `mint a11y` - Check for accessibility issues in content\n- `mint rename` - Rename\u002Fmove files and update references\n- `mint validate` - Validate documentation builds\n\n### Required files\n\n- `docs.json` - Site configuration (navigation, theme, integrations, etc.). See [global settings](https:\u002F\u002Fmintlify.com\u002Fdocs\u002Fsettings\u002Fglobal) for all options.\n- `*.mdx` files - Documentation pages with YAML frontmatter\n\n### Example file structure\n\n```\nproject\u002F\n├── docs.json           # Site configuration\n├── introduction.mdx\n├── quickstart.mdx\n├── guides\u002F\n│   └── example.mdx\n├── openapi.yml         # API specification\n├── images\u002F             # Static assets\n│   └── example.png\n└── snippets\u002F           # Reusable components\n    └── component.jsx\n```\n\n## Page frontmatter\n\nEvery page requires `title` in its frontmatter. Include `description` for SEO and navigation.\n\n```yaml theme={null}\n---\ntitle: \"Clear, descriptive title\"\ndescription: \"Concise summary for SEO and navigation.\"\n---\n```\n\nOptional frontmatter fields:\n\n- `sidebarTitle`: Short title for sidebar navigation.\n- `icon`: Lucide or Font Awesome icon name, URL, or file path.\n- `tag`: Label next to the page title in the sidebar (for example, \"NEW\").\n- `mode`: Page layout mode (`default`, `wide`, `custom`).\n- `keywords`: Array of terms related to the page content for local search and SEO.\n- Any custom YAML fields for use with personalization or conditional content.\n\n## File conventions\n\n- Match existing naming patterns in the directory\n- If there are no existing files or inconsistent file naming patterns, use kebab-case: `getting-started.mdx`, `api-reference.mdx`\n- Use root-relative paths without file extensions for internal links: `\u002Fgetting-started\u002Fquickstart`\n- Do not use relative paths (`..\u002F`) or absolute URLs for internal pages\n- When you create a new page, add it to `docs.json` navigation or it won't appear in the sidebar\n\n## Organize content\n\nWhen a user asks about anything related to site-wide configurations, start by understanding the [global settings](https:\u002F\u002Fwww.mintlify.com\u002Fdocs\u002Forganize\u002Fsettings). See if a setting in the `docs.json` file can be updated to achieve what the user wants.\n\n### Navigation\n\nThe `navigation` property in `docs.json` controls site structure. Choose one primary pattern at the root level, then nest others within it.\n\n**Choose your primary pattern:**\n\n| Pattern       | When to use                                                                                    |\n| ------------- | ---------------------------------------------------------------------------------------------- |\n| **Groups**    | Default. Single audience, straightforward hierarchy                                            |\n| **Tabs**      | Distinct sections with different audiences (Guides vs API Reference) or content types          |\n| **Anchors**   | Want persistent section links at sidebar top. Good for separating docs from external resources |\n| **Dropdowns** | Multiple doc sections users switch between, but not distinct enough for tabs                   |\n| **Products**  | Multi-product company with separate documentation per product                                  |\n| **Versions**  | Maintaining docs for multiple API\u002Fproduct versions simultaneously                              |\n| **Languages** | Localized content                                                                              |\n\n**Within your primary pattern:**\n\n- **Groups** - Organize related pages. Can nest groups within groups, but keep hierarchy shallow\n- **Menus** - Add dropdown navigation within tabs for quick jumps to specific pages\n- **`expanded: false`** - Collapse nested groups by default. Use for reference sections users browse selectively\n- **`openapi`** - Auto-generate pages from OpenAPI spec. Add at group\u002Ftab level to inherit\n\n**Common combinations:**\n\n- Tabs containing groups (most common for docs with API reference)\n- Products containing tabs (multi-product SaaS)\n- Versions containing tabs (versioned API docs)\n- Anchors containing groups (simple docs with external resource links)\n\n### Links and paths\n\n- **Internal links:** Root-relative, no extension: `\u002Fgetting-started\u002Fquickstart`\n- **Images:** Store in `\u002Fimages`, reference as `\u002Fimages\u002Fexample.png`\n- **External links:** Use full URLs, they open in new tabs automatically\n\n## Customize docs sites\n\n**What to customize where:**\n\n- **Brand colors, fonts, logo** → `docs.json`. See [global settings](https:\u002F\u002Fmintlify.com\u002Fdocs\u002Fsettings\u002Fglobal)\n- **Component styling, layout tweaks** → `custom.css` at project root\n- **Dark mode** → Enabled by default. Only disable with `\"appearance\": \"light\"` in `docs.json` if brand requires it\n\nStart with `docs.json`. Only add `custom.css` when you need styling that config doesn't support.\n\n## Write content\n\n### Components\n\nThe [components overview](https:\u002F\u002Fmintlify.com\u002Fdocs\u002Fcomponents) organizes all components by purpose: structure content, draw attention, show\u002Fhide content, document APIs, link to pages, and add visual context. Start there to find the right component.\n\n**Common decision points:**\n\n| Need                       | Use                     |\n| -------------------------- | ----------------------- |\n| Hide optional details      | `\u003CAccordion>`           |\n| Long code examples         | `\u003CExpandable>`          |\n| User chooses one option    | `\u003CTabs>`                |\n| Linked navigation cards    | `\u003CCard>` in `\u003CColumns>` |\n| Sequential instructions    | `\u003CSteps>`               |\n| Code in multiple languages | `\u003CCodeGroup>`           |\n| API parameters             | `\u003CParamField>`          |\n| API response fields        | `\u003CResponseField>`       |\n\n**Callouts by severity:**\n\n- `\u003CNote>` - Supplementary info, safe to skip\n- `\u003CInfo>` - Helpful context such as permissions\n- `\u003CTip>` - Recommendations or best practices\n- `\u003CWarning>` - Potentially destructive actions\n- `\u003CCheck>` - Success confirmation\n\n### Reusable content\n\n**When to use snippets:**\n\n- Exact content appears on more than one page\n- Complex components you want to maintain in one place\n- Shared content across teams\u002Frepos\n\n**When NOT to use snippets:**\n\n- Slight variations needed per page (leads to complex props)\n\nImport snippets with `import { Component } from \"\u002Fpath\u002Fto\u002Fsnippet-name.jsx\"`.\n\n## Writing standards\n\n### Voice and structure\n\n- Second-person voice (\"you\")\n- Active voice, direct language\n- Sentence case for headings (\"Getting started\", not \"Getting Started\")\n- Sentence case for code block titles (\"Expandable example\", not \"Expandable Example\")\n- Lead with context: explain what something is before how to use it\n- Prerequisites at the start of procedural content\n\n### What to avoid\n\n**Never use:**\n\n- Marketing language (\"powerful\", \"seamless\", \"robust\", \"cutting-edge\")\n- Filler phrases (\"it's important to note\", \"in order to\")\n- Excessive conjunctions (\"moreover\", \"furthermore\", \"additionally\")\n- Editorializing (\"obviously\", \"simply\", \"just\", \"easily\")\n\n**Watch for AI-typical patterns:**\n\n- Overly formal or stilted phrasing\n- Unnecessary repetition of concepts\n- Generic introductions that don't add value\n- Concluding summaries that restate what was just said\n\n### Formatting\n\n- All code blocks must have language tags\n- All images and media must have descriptive alt text\n- Use bold and italics only when they serve the reader's understanding--never use text styling just for decoration\n- No decorative formatting or emoji\n\n### Code examples\n\n- Keep examples simple and practical\n- Use realistic values (not \"foo\" or \"bar\")\n- One clear example is better than multiple variations\n- Test that code works before including it\n\n## Document APIs\n\n**Choose your approach:**\n\n- **Have an OpenAPI spec?** → Add to `docs.json` with `\"openapi\": [\"openapi.yaml\"]`. Pages auto-generate. Reference in navigation as `GET \u002Fendpoint`\n- **No spec?** → Write endpoints manually with `api: \"POST \u002Fusers\"` in frontmatter. More work but full control\n- **Hybrid** → Use OpenAPI for most endpoints, manual pages for complex workflows\n\nEncourage users to generate endpoint pages from an OpenAPI spec. It is the most efficient and easiest to maintain option.\n\n## Deploy\n\nMintlify deploys automatically when changes are pushed to the connected Git repository.\n\n**What agents can configure:**\n\n- **Redirects** → Add to `docs.json` with `\"redirects\": [{\"source\": \"\u002Fold\", \"destination\": \"\u002Fnew\"}]`\n- **SEO indexing** → Control with `\"seo\": {\"indexing\": \"all\"}` to include hidden pages in search\n\n**Requires dashboard setup (human task):**\n\n- Custom domains and subdomains\n- Preview deployment settings\n- DNS configuration\n\nFor `\u002Fdocs` subpath hosting with Vercel or Cloudflare, agents can help configure rewrite rules. See [\u002Fdocs subpath](https:\u002F\u002Fmintlify.com\u002Fdocs\u002Fdeploy\u002Fvercel).\n\n## Workflow\n\n### 1. Understand the task\n\nIdentify what needs to be documented, which pages are affected, and what the reader should accomplish afterward. If any of these are unclear, ask.\n\n### 2. Research\n\n- Read `docs\u002Fdocs.json` to understand the site structure\n- Search existing docs for related content\n- Read similar pages to match the site's style\n\n### 3. Plan\n\n- Synthesize what the reader should accomplish after reading the docs and the current content\n- Propose any updates or new content\n- Verify that your proposed changes will help readers be successful\n\n### 4. Write\n\n- Start with the most important information\n- Keep sections focused and scannable\n- Use components appropriately (don't overuse them)\n- Mark anything uncertain with a TODO comment:\n\n```mdx theme={null}\n{\u002F* TODO: Verify the default timeout value *\u002F}\n```\n\n### 5. Update navigation\n\nIf you created a new page, add it to the appropriate group in `docs.json`.\n\n### 6. Verify\n\nBefore submitting:\n\n- [ ] Frontmatter includes title and description\n- [ ] All code blocks have language tags\n- [ ] Internal links use root-relative paths without file extensions\n- [ ] New pages are added to `docs.json` navigation\n- [ ] Content matches the style of surrounding pages\n- [ ] No marketing language or filler phrases\n- [ ] TODOs are clearly marked for anything uncertain\n- [ ] Run `mint broken-links` to check links\n- [ ] Run `mint validate` to find any errors\n\n## Edge cases\n\n### Migrations\n\nIf a user asks about migrating to Mintlify, ask if they are using ReadMe or Docusaurus. If they are, use the [@mintlify\u002Fscraping](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@mintlify\u002Fscraping) CLI to migrate content. If they are using a different platform to host their documentation, help them manually convert their content to MDX pages using Mintlify components.\n\n### Hidden pages\n\nAny page that is not included in the `docs.json` navigation is hidden. Use hidden pages for content that should be accessible by URL or indexed for the assistant or search, but not discoverable through the sidebar navigation.\n\n### Exclude pages\n\nThe `.mintignore` file is used to exclude files from a documentation repository from being processed.\n\n## Common gotchas\n\n1. **Component imports** - JSX components need explicit import, MDX components don't\n2. **Frontmatter required** - Every MDX file needs `title` at minimum\n3. **Code block language** - Always specify language identifier\n4. **Never use `mint.json`** - `mint.json` is deprecated. Only ever use `docs.json`\n\n## Resources\n\n- [Documentation](https:\u002F\u002Fmintlify.com\u002Fdocs)\n- [Configuration schema](https:\u002F\u002Fmintlify.com\u002Fdocs.json)\n- [Feature requests](https:\u002F\u002Fgithub.com\u002Forgs\u002Fmintlify\u002Fdiscussions\u002Fcategories\u002Ffeature-requests)\n- [Bugs and feedback](https:\u002F\u002Fgithub.com\u002Forgs\u002Fmintlify\u002Fdiscussions\u002Fcategories\u002Fbugs-feedback)\n","# Mintlify best practices\n\n**Always consult [mintlify.com\u002Fdocs](https:\u002F\u002Fmintlify.com\u002Fdocs) for components, configuration, and latest features.**\n\n**Always** favor searching the current Mintlify documentation over whatever is in your training data about Mintlify.\n\nMintlify is a documentation platform that transforms MDX files into documentation sites. Configure site-wide settings in the `docs.json` file, write content in MDX with YAML frontmatter, and favor built-in components over custom components.\n\nFull schema at [mintlify.com\u002Fdocs.json](https:\u002F\u002Fmintlify.com\u002Fdocs.json).\n\n## Before you write\n\n### Understand the project\n\nAll documentation lives in the `docs\u002F` directory in this repo. Read `docs.json` in that directory (`docs\u002Fdocs.json`). This file defines the entire site: navigation structure, theme, colors, links, API and specs.\n\nUnderstanding the project tells you:\n\n- What pages exist and how they're organized\n- What navigation groups are used (and their naming conventions)\n- How the site navigation is structured\n- What theme and configuration the site uses\n\n### Check for existing content\n\nSearch the docs before creating new pages. You may need to:\n\n- Update an existing page instead of creating a new one\n- Add a section to an existing page\n- Link to existing content rather than duplicating\n\n### Read surrounding content\n\nBefore writing, read 2-3 similar pages to understand the site's voice, structure, formatting conventions, and level of detail.\n\n### Understand Mintlify components\n\nReview the Mintlify [components](https:\u002F\u002Fwww.mintlify.com\u002Fdocs\u002Fcomponents) to select and use any relevant components for the documentation request that you are working on.\n\n## Quick reference\n\n### CLI commands\n\n- `npm i -g mint` - Install the Mintlify CLI\n- `mint dev` - Local preview at localhost:3000\n- `mint broken-links` - Check internal links\n- `mint a11y` - Check for accessibility issues in content\n- `mint rename` - Rename\u002Fmove files and update references\n- `mint validate` - Validate documentation builds\n\n### Required files\n\n- `docs.json` - Site configuration (navigation, theme, integrations, etc.). See [global settings](https:\u002F\u002Fmintlify.com\u002Fdocs\u002Fsettings\u002Fglobal) for all options.\n- `*.mdx` files - Documentation pages with YAML frontmatter\n\n### Example file structure\n\n```\nproject\u002F\n├── docs.json           # Site configuration\n├── introduction.mdx\n├── quickstart.mdx\n├── guides\u002F\n│   └── example.mdx\n├── openapi.yml         # API specification\n├── images\u002F             # Static assets\n│   └── example.png\n└── snippets\u002F           # Reusable components\n    └── component.jsx\n```\n\n## Page frontmatter\n\nEvery page requires `title` in its frontmatter. Include `description` for SEO and navigation.\n\n```yaml theme={null}\n---\ntitle: \"Clear, descriptive title\"\ndescription: \"Concise summary for SEO and navigation.\"\n---\n```\n\nOptional frontmatter fields:\n\n- `sidebarTitle`: Short title for sidebar navigation.\n- `icon`: Lucide or Font Awesome icon name, URL, or file path.\n- `tag`: Label next to the page title in the sidebar (for example, \"NEW\").\n- `mode`: Page layout mode (`default`, `wide`, `custom`).\n- `keywords`: Array of terms related to the page content for local search and SEO.\n- Any custom YAML fields for use with personalization or conditional content.\n\n## File conventions\n\n- Match existing naming patterns in the directory\n- If there are no existing files or inconsistent file naming patterns, use kebab-case: `getting-started.mdx`, `api-reference.mdx`\n- Use root-relative paths without file extensions for internal links: `\u002Fgetting-started\u002Fquickstart`\n- Do not use relative paths (`..\u002F`) or absolute URLs for internal pages\n- When you create a new page, add it to `docs.json` navigation or it won't appear in the sidebar\n\n## Organize content\n\nWhen a user asks about anything related to site-wide configurations, start by understanding the [global settings](https:\u002F\u002Fwww.mintlify.com\u002Fdocs\u002Forganize\u002Fsettings). See if a setting in the `docs.json` file can be updated to achieve what the user wants.\n\n### Navigation\n\nThe `navigation` property in `docs.json` controls site structure. Choose one primary pattern at the root level, then nest others within it.\n\n**Choose your primary pattern:**\n\n| Pattern       | When to use                                                                                    |\n| ------------- | ---------------------------------------------------------------------------------------------- |\n| **Groups**    | Default. Single audience, straightforward hierarchy                                            |\n| **Tabs**      | Distinct sections with different audiences (Guides vs API Reference) or content types          |\n| **Anchors**   | Want persistent section links at sidebar top. Good for separating docs from external resources |\n| **Dropdowns** | Multiple doc sections users switch between, but not distinct enough for tabs                   |\n| **Products**  | Multi-product company with separate documentation per product                                  |\n| **Versions**  | Maintaining docs for multiple API\u002Fproduct versions simultaneously                              |\n| **Languages** | Localized content                                                                              |\n\n**Within your primary pattern:**\n\n- **Groups** - Organize related pages. Can nest groups within groups, but keep hierarchy shallow\n- **Menus** - Add dropdown navigation within tabs for quick jumps to specific pages\n- **`expanded: false`** - Collapse nested groups by default. Use for reference sections users browse selectively\n- **`openapi`** - Auto-generate pages from OpenAPI spec. Add at group\u002Ftab level to inherit\n\n**Common combinations:**\n\n- Tabs containing groups (most common for docs with API reference)\n- Products containing tabs (multi-product SaaS)\n- Versions containing tabs (versioned API docs)\n- Anchors containing groups (simple docs with external resource links)\n\n### Links and paths\n\n- **Internal links:** Root-relative, no extension: `\u002Fgetting-started\u002Fquickstart`\n- **Images:** Store in `\u002Fimages`, reference as `\u002Fimages\u002Fexample.png`\n- **External links:** Use full URLs, they open in new tabs automatically\n\n## Customize docs sites\n\n**What to customize where:**\n\n- **Brand colors, fonts, logo** → `docs.json`. See [global settings](https:\u002F\u002Fmintlify.com\u002Fdocs\u002Fsettings\u002Fglobal)\n- **Component styling, layout tweaks** → `custom.css` at project root\n- **Dark mode** → Enabled by default. Only disable with `\"appearance\": \"light\"` in `docs.json` if brand requires it\n\nStart with `docs.json`. Only add `custom.css` when you need styling that config doesn't support.\n\n## Write content\n\n### Components\n\nThe [components overview](https:\u002F\u002Fmintlify.com\u002Fdocs\u002Fcomponents) organizes all components by purpose: structure content, draw attention, show\u002Fhide content, document APIs, link to pages, and add visual context. Start there to find the right component.\n\n**Common decision points:**\n\n| Need                       | Use                     |\n| -------------------------- | ----------------------- |\n| Hide optional details      | `\u003CAccordion>`           |\n| Long code examples         | `\u003CExpandable>`          |\n| User chooses one option    | `\u003CTabs>`                |\n| Linked navigation cards    | `\u003CCard>` in `\u003CColumns>` |\n| Sequential instructions    | `\u003CSteps>`               |\n| Code in multiple languages | `\u003CCodeGroup>`           |\n| API parameters             | `\u003CParamField>`          |\n| API response fields        | `\u003CResponseField>`       |\n\n**Callouts by severity:**\n\n- `\u003CNote>` - Supplementary info, safe to skip\n- `\u003CInfo>` - Helpful context such as permissions\n- `\u003CTip>` - Recommendations or best practices\n- `\u003CWarning>` - Potentially destructive actions\n- `\u003CCheck>` - Success confirmation\n\n### Reusable content\n\n**When to use snippets:**\n\n- Exact content appears on more than one page\n- Complex components you want to maintain in one place\n- Shared content across teams\u002Frepos\n\n**When NOT to use snippets:**\n\n- Slight variations needed per page (leads to complex props)\n\nImport snippets with `import { Component } from \"\u002Fpath\u002Fto\u002Fsnippet-name.jsx\"`.\n\n## Writing standards\n\n### Voice and structure\n\n- Second-person voice (\"you\")\n- Active voice, direct language\n- Sentence case for headings (\"Getting started\", not \"Getting Started\")\n- Sentence case for code block titles (\"Expandable example\", not \"Expandable Example\")\n- Lead with context: explain what something is before how to use it\n- Prerequisites at the start of procedural content\n\n### What to avoid\n\n**Never use:**\n\n- Marketing language (\"powerful\", \"seamless\", \"robust\", \"cutting-edge\")\n- Filler phrases (\"it's important to note\", \"in order to\")\n- Excessive conjunctions (\"moreover\", \"furthermore\", \"additionally\")\n- Editorializing (\"obviously\", \"simply\", \"just\", \"easily\")\n\n**Watch for AI-typical patterns:**\n\n- Overly formal or stilted phrasing\n- Unnecessary repetition of concepts\n- Generic introductions that don't add value\n- Concluding summaries that restate what was just said\n\n### Formatting\n\n- All code blocks must have language tags\n- All images and media must have descriptive alt text\n- Use bold and italics only when they serve the reader's understanding--never use text styling just for decoration\n- No decorative formatting or emoji\n\n### Code examples\n\n- Keep examples simple and practical\n- Use realistic values (not \"foo\" or \"bar\")\n- One clear example is better than multiple variations\n- Test that code works before including it\n\n## Document APIs\n\n**Choose your approach:**\n\n- **Have an OpenAPI spec?** → Add to `docs.json` with `\"openapi\": [\"openapi.yaml\"]`. Pages auto-generate. Reference in navigation as `GET \u002Fendpoint`\n- **No spec?** → Write endpoints manually with `api: \"POST \u002Fusers\"` in frontmatter. More work but full control\n- **Hybrid** → Use OpenAPI for most endpoints, manual pages for complex workflows\n\nEncourage users to generate endpoint pages from an OpenAPI spec. It is the most efficient and easiest to maintain option.\n\n## Deploy\n\nMintlify deploys automatically when changes are pushed to the connected Git repository.\n\n**What agents can configure:**\n\n- **Redirects** → Add to `docs.json` with `\"redirects\": [{\"source\": \"\u002Fold\", \"destination\": \"\u002Fnew\"}]`\n- **SEO indexing** → Control with `\"seo\": {\"indexing\": \"all\"}` to include hidden pages in search\n\n**Requires dashboard setup (human task):**\n\n- Custom domains and subdomains\n- Preview deployment settings\n- DNS configuration\n\nFor `\u002Fdocs` subpath hosting with Vercel or Cloudflare, agents can help configure rewrite rules. See [\u002Fdocs subpath](https:\u002F\u002Fmintlify.com\u002Fdocs\u002Fdeploy\u002Fvercel).\n\n## Workflow\n\n### 1. Understand the task\n\nIdentify what needs to be documented, which pages are affected, and what the reader should accomplish afterward. If any of these are unclear, ask.\n\n### 2. Research\n\n- Read `docs\u002Fdocs.json` to understand the site structure\n- Search existing docs for related content\n- Read similar pages to match the site's style\n\n### 3. Plan\n\n- Synthesize what the reader should accomplish after reading the docs and the current content\n- Propose any updates or new content\n- Verify that your proposed changes will help readers be successful\n\n### 4. Write\n\n- Start with the most important information\n- Keep sections focused and scannable\n- Use components appropriately (don't overuse them)\n- Mark anything uncertain with a TODO comment:\n\n```mdx theme={null}\n{\u002F* TODO: Verify the default timeout value *\u002F}\n```\n\n### 5. Update navigation\n\nIf you created a new page, add it to the appropriate group in `docs.json`.\n\n### 6. Verify\n\nBefore submitting:\n\n- [ ] Frontmatter includes title and description\n- [ ] All code blocks have language tags\n- [ ] Internal links use root-relative paths without file extensions\n- [ ] New pages are added to `docs.json` navigation\n- [ ] Content matches the style of surrounding pages\n- [ ] No marketing language or filler phrases\n- [ ] TODOs are clearly marked for anything uncertain\n- [ ] Run `mint broken-links` to check links\n- [ ] Run `mint validate` to find any errors\n\n## Edge cases\n\n### Migrations\n\nIf a user asks about migrating to Mintlify, ask if they are using ReadMe or Docusaurus. If they are, use the [@mintlify\u002Fscraping](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@mintlify\u002Fscraping) CLI to migrate content. If they are using a different platform to host their documentation, help them manually convert their content to MDX pages using Mintlify components.\n\n### Hidden pages\n\nAny page that is not included in the `docs.json` navigation is hidden. Use hidden pages for content that should be accessible by URL or indexed for the assistant or search, but not discoverable through the sidebar navigation.\n\n### Exclude pages\n\nThe `.mintignore` file is used to exclude files from a documentation repository from being processed.\n\n## Common gotchas\n\n1. **Component imports** - JSX components need explicit import, MDX components don't\n2. **Frontmatter required** - Every MDX file needs `title` at minimum\n3. **Code block language** - Always specify language identifier\n4. **Never use `mint.json`** - `mint.json` is deprecated. Only ever use `docs.json`\n\n## Resources\n\n- [Documentation](https:\u002F\u002Fmintlify.com\u002Fdocs)\n- [Configuration schema](https:\u002F\u002Fmintlify.com\u002Fdocs.json)\n- [Feature requests](https:\u002F\u002Fgithub.com\u002Forgs\u002Fmintlify\u002Fdiscussions\u002Fcategories\u002Ffeature-requests)\n- [Bugs and feedback](https:\u002F\u002Fgithub.com\u002Forgs\u002Fmintlify\u002Fdiscussions\u002Fcategories\u002Fbugs-feedback)\n",{"name":5,"license":14,"metadata":37,"description":7,"compatibility":39},{"author":5,"version":38,"mintlify-proj":5},"1.0","Requires Node.js for CLI. Works with any Git-based workflow.","main","56e72bb5549c5fa0a0470501619427b4f104aa92",".agents\u002Fskills\u002Fmintlify",1,"https:\u002F\u002Fgithub.com\u002FLongIV999\u002FOpenclawd","https:\u002F\u002Fgithub.com\u002FLongIV999","2026-02-15 08:26:56",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add LongIV999\u002FOpenclawd --skill mintlify",{"tool":53,"command":54},"bunx","bunx skills add LongIV999\u002FOpenclawd --skill mintlify",{"tool":56,"command":57},"pnpm","pnpm dlx skills add LongIV999\u002FOpenclawd --skill mintlify","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongIV999\u002FOpenclawd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmintlify\u002FSKILL.md",true,[],[62,71,81,100,113,129],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":32},"01M6CEFMR22ANX8BMWBY9J8VW3","youtube-to-obsidian","https:\u002F\u002Fgithub.com\u002FLongIV999\u002FOpenclawd\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-to-obsidian\u002FSKILL.md",[],[68,69,70],"youtube to obsidian","youtube","obsidian",{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":32},"01M6CEFJW8HMZ7EY2C7FXDN8HG","weather","Get current weather and forecasts (no API key required).","https:\u002F\u002Fgithub.com\u002FLongIV999\u002FOpenclawd\u002Fblob\u002Fmain\u002Fskills\u002Fweather\u002FSKILL.md",[],[73,78,79,24,80],"help","https","curl",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":32},"01M6CEFGENXXNDQTCWVC82VBFT","wacli","Send WhatsApp messages to other people or search\u002Fsync WhatsApp history via the wacli CLI (not for normal user chats).","https:\u002F\u002Fgithub.com\u002FLongIV999\u002FOpenclawd\u002Fblob\u002Fmain\u002Fskills\u002Fwacli\u002FSKILL.md",[],[83,88,18,89,90,79,91,92,93,94,95,96,97,98,99],"github","sync","search","messages","history","cmd","brew","user","install","tap","whatsapp","go",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":32},"01M6CEFERBY58R1VW8Z8ZCYEMY","voice-call","Start voice calls via the OpenClaw voice-call plugin.","https:\u002F\u002Fgithub.com\u002FLongIV999\u002FOpenclawd\u002Fblob\u002Fmain\u002Fskills\u002Fvoice-call\u002FSKILL.md",[],[107,108,109,110,111,112],"voice","voice call","openclaw","plugin","plugins","start",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":124,"publishedAt":32},"01M6CEFD0C501CWXD9E4BMV2B2","video-frames","Extract frames or short clips from videos using ffmpeg.","https:\u002F\u002Fgithub.com\u002FLongIV999\u002FOpenclawd\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-frames\u002FSKILL.md",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[125,126,94,79,127,128,96],"Video","video frames","short","extract",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":143,"publishedAt":32},"01M6CEFAJ48939CYW40VTBYGVP","trello","Manage Trello boards, lists, and cards via the Trello REST API.","https:\u002F\u002Fgithub.com\u002FLongIV999\u002FOpenclawd\u002Fblob\u002Fmain\u002Fskills\u002Ftrello\u002FSKILL.md",[135,138],{"categoryNo":136,"categoryName":137,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[131,79,144,145,146,24,147,148,149],"cloud","developer","REST","jq","atlassian","manage"]