Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
codewithshreyans avatar

Mintlify

  • 1.7k installs
  • Updated April 30, 2026
  • codewithshreyans/skills

This is a copy of mintlify by mintlify - installs and ranking accrue to the original listing.

mintlify is a documentation agent skill that generates and maintains interactive API reference docs from OpenAPI and AsyncAPI specs plus MDX manual pages for developers who need polished API documentation wired into Mint

About

mintlify is a codewithshreyans agent skill for setting up Mintlify API documentation from OpenAPI, AsyncAPI, and MDX sources. The skill configures docs.json api blocks for single or multiple OpenAPI specs, wires endpoint pages like GET /users into navigation groups, and applies OpenAPI extensions including x-hidden, x-excluded, and x-codeSamples for per-endpoint code examples. Developers reach for mintlify when shipping or refreshing API docs without hand-writing every endpoint page. The skill supports referencing individual endpoints in navigation and managing multiple spec versions side by side.

  • Supports OpenAPI, AsyncAPI, and custom MDX manual pages
  • Reference individual endpoints with group-level navigation
  • OpenAPI extensions including x-hidden, x-excluded, and x-codeSamples
  • Interactive API playground with configurable proxy behavior
  • Automatic generation of reference docs from spec files

Mintlify by the numbers

  • 1,705 all-time installs (skills.sh)
  • +1 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/codewithshreyans/skills --skill mintlify

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.7k
Security audit3 / 3 scanners passed
Last updatedApril 30, 2026
Repositorycodewithshreyans/skills

How do you generate API docs from OpenAPI in Mintlify?

Automatically generate and maintain beautiful, interactive API reference documentation from OpenAPI and AsyncAPI specs.

Who is it for?

API developers with OpenAPI or AsyncAPI specs who want Mintlify-powered interactive reference docs with navigation and custom endpoint examples.

Skip if: Teams using non-Mintlify doc platforms or projects without machine-readable API specifications.

When should I use this skill?

A developer needs Mintlify API docs from OpenAPI/AsyncAPI specs, endpoint navigation setup, or OpenAPI extension configuration.

What you get

docs.json configuration, OpenAPI-linked navigation pages, and interactive API reference with custom code samples.

  • docs.json configuration
  • API navigation structure
  • Interactive endpoint pages

Files

SKILL.mdMarkdownGitHub ↗

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. To find them, look in the same directory as this skill file (e.g., .claude/skills/mintlify/reference/).

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

Internal links

  • 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">

npm install package-name

  </Tab>
  <Tab title="yarn">

yarn add package-name

  </Tab>
</Tabs>
<CodeGroup>

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

  • npm i -g mint — Install the Mintlify CLI.
  • mint dev — Local preview at localhost:3000.
  • mint broken-links — Check internal links.
  • mint a11y — Check for accessibility issues.
  • mint validate — Validate documentation builds.
  • mint upgrade — Upgrade from mint.json to docs.json.

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).

Related skills

FAQ

How does mintlify configure OpenAPI in docs.json?

The mintlify skill adds an api.openapi field pointing to openapi.json or an array of spec paths in docs.json, then references individual endpoints like GET /users in navigation group pages for interactive Mintlify API docs.

What OpenAPI extensions does mintlify support?

The mintlify skill documents x-hidden to create pages omitted from navigation, x-excluded to drop endpoints entirely, and x-codeSamples to attach custom per-endpoint code examples in generated API reference pages.

Is Mintlify safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Documentationdocsintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.