mintlify-docs-updater
Skill27 starsChanged 8 months agoApache-2.0View on GitHub
Maintain this repository's Mintlify documentation from uploaded Markdown files. Use when asked to add, update, or organize docs pages in `docs/`, place new content under `get_started`, `core`, `core/models`, or `troubleshooting`, and keep `docs/docs.json` navigation in sync with new pages.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- webapp-testingSkill
- env-hubSkill
- mcp-builderSkill
- reviewSkill
- shipSkill
- skill-creatorSkill
- specSkill
- internal-commsSkill
- ml-failure-auditSkill
- changelog-generatorSkill
- algorithmic-artSkill
- canvas-designSkill
- instagram-reel-editorSkill
- remotionSkill
- slack-gif-creatorSkill
- ab-test-setupSkill
- copywritingSkill
- humanizerSkill
- instagram-postingSkill
- marketing-ideasSkill
- seo-auditSkill
- claude-for-legalSkill
- contract-review-risk-scoringSkill
- doc-coauthoringSkill
- docxSkill
- legal-work-pluginSkill
- pdfSkill
- pptxSkill
- xlsxSkill
- pm-skillsSkill
- resume-tailoringSkill
- last30daysSkill
- brand-guidelinesSkill
- excalidrawSkill
- frontend-designSkill
- open-designSkill
- theme-factorySkill
- web-artifacts-builderSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 3 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use this skill to ingest user-provided Markdown into the Mintlify docs tree, enforce required frontmatter, and update navigation entries in …
- Distinctive: line 11
Prefer the included script for deterministic page placement and nav updates.
- Very specific: line 15
Read the current site map in references/docs-structure.md.
- Very specific: line 26
Use --subgroup "Models" when adding pages under core/models.
- Very specific: line 27
Use --dry-run first when the target placement is uncertain.
- Distinctive: line 35
Add a new page and nav entry:
- Very specific: line 44
Add a new Core > Models page and place it after an existing page:
- Very specific: line 67
Keep page files in docs/<section>/<slug>.md.
- Very specific: line 68
Keep page references in docs/docs.json as absolute doc routes (for example, "/core/concepts").
- Distinctive: line 69
Keep frontmatter keys minimal and compatible with current docs:
- Very specific: line 74
Use /docs/images/<file> for image paths in Markdown/HTML blocks.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Mintlify Docs Updater
Overview
Use this skill to ingest user-provided Markdown into the Mintlify docs tree, enforce required frontmatter, and update navigation entries in docs/docs.json.
Prefer the included script for deterministic page placement and nav updates.
Workflow
- Read the current site map in
references/docs-structure.md. - Decide the destination page path (for example,
core/new-feature->docs/core/new-feature.md). - Ingest the uploaded Markdown file with the script:
python3 scripts/ingest_markdown_doc.py \
--source /absolute/path/to/upload.md \
--page core/new-feature \
--group "Core"- Use
--subgroup "Models"when adding pages undercore/models. - Use
--dry-runfirst when the target placement is uncertain. - Validate changes:
- Confirm the new file exists under
docs/. - Confirm
docs/docs.jsonincludes the new"/path/to/page"entry in the right group. - Confirm frontmatter includes
titleanddescription.
- Confirm the new file exists under
Commands
Add a new page and nav entry:
python3 scripts/ingest_markdown_doc.py \
--source /absolute/path/to/upload.md \
--page get_started/advanced-setup \
--group "Get Started"Add a new Core > Models page and place it after an existing page:
python3 scripts/ingest_markdown_doc.py \
--source /absolute/path/to/model-guide.md \
--page core/models/new-provider \
--group "Core" \
--subgroup "Models" \
--insert-after /core/models/kimiPreview changes without writing files:
python3 scripts/ingest_markdown_doc.py \
--source /absolute/path/to/upload.md \
--page troubleshooting/new-issue \
--group "Troubleshooting" \
--dry-runEditing Rules
- Keep page files in
docs/<section>/<slug>.md. - Keep page references in
docs/docs.jsonas absolute doc routes (for example,"/core/concepts"). - Keep frontmatter keys minimal and compatible with current docs:
title(required)description(required)icon(optional)
- Preserve existing Mintlify components and JSX blocks when present.
- Use
/docs/images/<file>for image paths in Markdown/HTML blocks.
References
references/docs-structure.md: Current Mintlify navigation map and folder structure for this repository.references/content-format.md: Frontmatter and content conventions for new docs pages.scripts/ingest_markdown_doc.py: Deterministic ingest/update script for uploaded Markdown files.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

