Generated banner for Mintlify
Generated logo for Mintlify

Mintlify

ClineOfficialPublished by Cline

  • Skill
  • Tool integration
  • Documents and content
  • Apache-2.0
  • Low risk

From the author

Comprehensive reference for building Mintlify documentation sites. Use when creating pages, configuring docs.json, adding components, setting up navigation, or working with API references. Routes to detailed reference files for all components and configuration options.
— the description by Cline

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured reference for developing documentation sites with Mintlify. It covers the essential workflow for creating pages, configuring site settings via docs.json, managing navigation, and implementing API documentation. It includes guidelines for file organization, frontmatter usage, and writing standards, alongside a complete reference for CLI commands and MDX components.

What it does

  • Provides guidance on configuring site settings, themes, and navigation structures.
  • Details the use of MDX components like callouts, tabs, cards, and code groups.
  • Outlines standards for page frontmatter, internal linking, and image accessibility.
  • Lists CLI commands for local development, site validation, and content quality checks.
  • Explains how to integrate API documentation using OpenAPI specifications.
  • Offers instructions for accessing site analytics and managing authentication.

When to use it

  • When initializing a new Mintlify documentation project.
  • When adding new pages or restructuring existing site navigation.
  • When implementing or updating API reference documentation.
  • When troubleshooting site configuration or build errors.
  • When performing quality assurance checks like link validation or accessibility audits.

Advantages

  • Centralizes configuration and component syntax for consistent documentation.
  • Provides clear standards for maintaining documentation quality and structure.
  • Facilitates efficient site management through integrated CLI command references.
  • Ensures proper integration of interactive API playgrounds and documentation.

Usage examples

“How do I add a new page to my Mintlify site?”
The agent explains creating an MDX file, adding the required frontmatter, and updating the docs.json navigation file to ensure the page appears in the sidebar.
“Show me how to use a tabbed code block.”
The agent provides the correct Tabs and Tab component syntax to display multiple code snippets in a single block.
“How can I check my documentation for broken links?”
The agent provides the mint broken-links command and explains the available flags for checking anchors and external URLs.
“What are the required fields for page frontmatter?”
The agent lists the required title field and optional fields like description, icon, and hidden status for SEO and navigation control.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/cline/mintlify/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip mintlify.zip -d .agents/skills

Documentation by Cline

Mintlify reference

Reference for building documentation with Mintlify. This file covers essentials that apply to every task. For detailed reference on specific topics, read the files listed in the reference index below.

Reference index

Read these files only when your task requires them. They are in the reference/ directory next to this file.

FileWhen to read
reference/components.mdAdding or modifying components (callouts, cards, steps, tabs, accordions, code groups, fields, frames, icons, tooltips, badges, trees, mermaid, panels, prompts, colors, tiles, updates, views).
reference/configuration.mdChanging docs.json settings (theme, colors, logo, fonts, appearance, navbar, footer, banner, redirects, SEO, integrations, API config). Also covers snippets, hidden pages, .mintignore, custom CSS/JS, and the complete frontmatter fields table.
reference/navigation.mdModifying site navigation structure (groups, tabs, anchors, dropdowns, products, versions, languages, OpenAPI in nav).
reference/api-docs.mdSetting up API documentation (OpenAPI, AsyncAPI, MDX manual API pages, extensions, playground config).

Before you start

Read the project's docs.json file first. It defines the site's navigation, theme, colors, and configuration.

Search for existing content before creating new pages. You may need to update an existing page, add a section, or link to existing content rather than duplicating.

Read 2-3 similar pages to match the site's voice, structure, and formatting.

File format

Mintlify uses MDX files (.mdx or .md) with YAML frontmatter.

project/
├── docs.json           # Site configuration (required)
├── index.mdx
├── quickstart.mdx
├── guides/
│   └── example.mdx
├── openapi.yml         # API specification (optional)
├── images/             # Static assets
│   └── example.png
└── snippets/           # Reusable components
    └── component.jsx
File naming
  • Match existing patterns in the directory

  • If no existing files or mixed file naming patterns, use kebab-case: getting-started.mdx

  • Add new pages to docs.json navigation or they won't appear in the sidebar

  • Use root-relative paths without file extensions: /getting-started/quickstart

  • Do not use relative paths (../) or absolute URLs for internal pages

Images

Store images in an images/ directory. Reference with root-relative paths. All images require descriptive alt text.

![Dashboard showing analytics overview](/images/dashboard.png)

Page frontmatter

Every page requires title in its frontmatter. Include description and keywords for SEO.

---
title: "Clear, descriptive title"
description: "Concise summary for SEO and navigation."
keywords: ["relevant", "search", "terms"]
---
Common frontmatter fields
FieldTypeRequiredDescription
titlestringYesPage title in navigation and browser tabs.
descriptionstringNoBrief description for SEO. Displays under the title.
sidebarTitlestringNoShort title for sidebar navigation.
iconstringNoLucide, Font Awesome, or Tabler icon name. Also accepts a URL or file path.
tagstringNoLabel next to page title in sidebar (e.g., "NEW").
hiddenbooleanNoRemove from sidebar. Page still accessible by URL.
modestringNoPage layout: default, wide, custom, frame, center.
keywordsarrayNoSearch terms for internal search and SEO.
apistringNoAPI endpoint for interactive playground (e.g., "POST /users").
openapistringNoOpenAPI endpoint reference (e.g., "GET /endpoint").

Quick component reference

Below are the most commonly used components. For full props and all 24 components, read reference/components.md.

Callouts
<Note>Supplementary information, safe to skip.</Note>
<Info>Helpful context such as permissions or prerequisites.</Info>
<Tip>Recommendations or best practices.</Tip>
<Warning>Potentially destructive actions or important caveats.</Warning>
<Check>Success confirmation or completed status.</Check>
<Danger>Critical warnings about data loss or breaking changes.</Danger>
Steps
<Steps>
  <Step title="First step">
    Instructions for step one.
  </Step>
  <Step title="Second step">
    Instructions for step two.
  </Step>
</Steps>
Tabs and code groups
<Tabs>
  <Tab title="npm">
    ```bash
    npm install package-name
    ```
  </Tab>
  <Tab title="yarn">
    ```bash
    yarn add package-name
    ```
  </Tab>
</Tabs>
<CodeGroup>

```javascript example.js
const greeting = "Hello, world!";
greeting = "Hello, world!"

</CodeGroup> ```

Cards and columns
<Columns cols={2}>
  <Card title="First card" icon="rocket" href="/quickstart">
    Card description text.
  </Card>
  <Card title="Second card" icon="book" href="/guides">
    Card description text.
  </Card>
</Columns>

Use <Columns> to arrange cards (or other content) in a grid. cols accepts 1-4.

Accordions
<AccordionGroup>
  <Accordion title="First section">Content one.</Accordion>
  <Accordion title="Second section">Content two.</Accordion>
</AccordionGroup>

CLI commands

Install the CLI with npm i -g mint.

Local development
  • mint dev — Start local preview at localhost:3000. --no-open skips browser launch. --groups <names> mocks user groups.

  • mint validate — Strict build validation; exits non-zero on warnings or errors.

  • mint export — Export a static site zip for air-gapped deployment. --output <file> sets the output path (default: export.zip).

Content quality
  • mint broken-links — Check for broken internal links. --check-anchors validates # anchors. --check-external checks external URLs. --check-snippets checks links inside <Snippet> components.

  • mint a11y — Accessibility checks (alt text, color contrast). --skip-contrast or --skip-alt-text to narrow scope.

Analytics
  • mint analytics stats — KPI numbers (views, visitors, searches). Options: --subdomain, --from, --to, --format (table/plain/json/graph), --agents/--humans to filter traffic, --page to filter to one path.

  • mint analytics search — Search analytics. --query filters by search term substring.

  • mint analytics feedback — Feedback analytics. --type (code or page).

  • mint analytics conversation list — List assistant conversations.

  • mint analytics conversation view <id> — View a single conversation.

  • mint analytics conversation buckets list — List conversation category buckets.

  • mint analytics conversation buckets view <id> — View conversations in a bucket.

Authentication
  • mint login — Authenticate your Mintlify account.

  • mint logout — Log out of your account.

  • mint status — Show current authentication status.

Configuration
  • mint config set <key> <value> — Persist a config value. Valid keys: subdomain, dateFrom, dateTo.

  • mint config get <key> — Read a stored config value.

  • mint config clear <key> — Remove a stored config value.

Project setup
  • mint new [directory] — Scaffold a new Mintlify docs site. --theme and --name set initial config.

  • mint workflow — Add a workflow to the docs repository.

Maintenance
  • mint update — Update the CLI to the latest version.

  • mint version — Show installed CLI and client versions.

Writing standards

  • Second-person voice ("you").

  • Active voice, direct language.

  • Sentence case for headings ("Getting started", not "Getting Started").

  • Sentence case for code block titles.

  • All code blocks must have language tags.

  • All images must have descriptive alt text.

  • No marketing language, filler phrases, or emoji.

  • Keep code examples simple, practical, and tested.

Common mistakes

  • Missing language tag on a code block (use ```python, not ```).

  • Using relative paths (../page) instead of root-relative (/section/page).

  • Forgetting to add new pages to docs.json navigation.

  • Images without alt text.

  • Adding file extensions to internal links (/page.mdx instead of /page).

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python, Needs Node.js

Security

What our scanner noticed· Low risk

  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Cline
Publisher
Cline (Official)
Source
cline/skills · skills/mintlify · commit 2637846
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Cline.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download mintlify.zip