agentleFS
eigent-aieigent-ai/agent-skills/skills/coding-agents-and-ides/mintlify-docs-updater/SKILL.md

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.

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
  1. Very specific:

    Use this skill to ingest user-provided Markdown into the Mintlify docs tree, enforce required frontmatter, and update navigation entries in …

    line 10
  2. Distinctive:

    Prefer the included script for deterministic page placement and nav updates.

    line 11
  3. Very specific:

    Read the current site map in references/docs-structure.md.

    line 15
  4. Very specific:

    Use --subgroup "Models" when adding pages under core/models.

    line 26
  5. Very specific:

    Use --dry-run first when the target placement is uncertain.

    line 27
  6. Distinctive:

    Add a new page and nav entry:

    line 35
  7. Very specific:

    Add a new Core > Models page and place it after an existing page:

    line 44
  8. Very specific:

    Keep page files in docs/<section>/<slug>.md.

    line 67
  9. Very specific:

    Keep page references in docs/docs.json as absolute doc routes (for example, "/core/concepts").

    line 68
  10. Distinctive:

    Keep frontmatter keys minimal and compatible with current docs:

    line 69
  11. Very specific:

    Use /docs/images/<file> for image paths in Markdown/HTML blocks.

    line 74

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Read the current site map in references/docs-structure.md.
  2. Decide the destination page path (for example, core/new-feature -> docs/core/new-feature.md).
  3. 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"
  1. Use --subgroup "Models" when adding pages under core/models.
  2. Use --dry-run first when the target placement is uncertain.
  3. Validate changes:
    • Confirm the new file exists under docs/.
    • Confirm docs/docs.json includes the new "/path/to/page" entry in the right group.
    • Confirm frontmatter includes title and description.

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/kimi

Preview changes without writing files:

python3 scripts/ingest_markdown_doc.py \
  --source /absolute/path/to/upload.md \
  --page troubleshooting/new-issue \
  --group "Troubleshooting" \
  --dry-run

Editing Rules

  1. Keep page files in docs/<section>/<slug>.md.
  2. Keep page references in docs/docs.json as absolute doc routes (for example, "/core/concepts").
  3. Keep frontmatter keys minimal and compatible with current docs:
    • title (required)
    • description (required)
    • icon (optional)
  4. Preserve existing Mintlify components and JSX blocks when present.
  5. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.