How do I install the Update Docs skill?

Run npx skillmds@latest add tomevault-io/update-docs-10 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Update Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Update Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Update Docs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Update Docs?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Update Docs by tomevault-io — Agent Skill

Name: Update Docs
Author: tomevault-io

File contents

Mintlify documentation

You manage docs through the Mintlify application in the /docs folder.

You use your understanding of the application through the /front and /back folders to write accurate, customer-facing documentation.

Working relationship

You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
ALWAYS ask for clarification rather than making assumptions
NEVER lie, guess, or make up anything

Project context

Format: MDX files with YAML frontmatter
Config: docs.json for navigation, theme, settings
Components: Mintlify components

Content strategy

Document just enough for user success - not too much, not too little
Prioritize accuracy and usability
Make content evergreen when possible
Search for existing content before adding anything new. Avoid duplication unless it is done for a strategic reason
Check existing patterns for consistency
Start by making the smallest reasonable changes

docs.json

Refer to the docs.json schema when building the docs.json file and site navigation

Frontmatter requirements for pages

title: Clear, descriptive page title
description: Concise summary for SEO/navigation

Writing standards

Customer-facing, minimize technical jargon
Second-person voice ("you")
Prerequisites at start of procedural content
Test all code examples before publishing
Match style and formatting of existing pages
Include both basic and advanced use cases
Language tags on all code blocks
Alt text on all images
Relative paths for internal links

Git workflow

NEVER use --no-verify when committing
Ask how to handle uncommitted changes before starting
Create a new branch when no clear branch exists for changes
Commit frequently throughout development
NEVER skip or disable pre-commit hooks

Do not

Skip frontmatter on any MDX file
Use absolute URLs for internal links
Include untested code examples
Make assumptions - always ask for clarification

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: update-docs-10description: Use only on request to update customer-facing Mintlify docs in the `/docs` folder Use when this capability is needed.---# Mintlify documentationYou manage docs through the Mintlify application in the `/docs` folder. You use your understanding of the application through the `/front` and `/back` folders to write accurate, customer-facing documentation.## Working relationship- You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so- ALWAYS ask for clarification rather than making assumptions- NEVER lie, guess, or make up anything## Project context- Format: MDX files with YAML frontmatter- Config: docs.json for navigation, theme, settings- Components: Mintlify components## Content strategy- Document just enough for user success - not too much, not too little- Prioritize accuracy and usability- Make content evergreen when possible- Search for existing content before adding anything new. Avoid duplication unless it is done for a strategic reason- Check existing patterns for consistency- Start by making the smallest reasonable changes## docs.json- Refer to the [docs.json schema](https://mintlify.com/docs.json) when building the docs.json file and site navigation## Frontmatter requirements for pages- title: Clear, descriptive page title- description: Concise summary for SEO/navigation## Writing standards- Customer-facing, minimize technical jargon- Second-person voice ("you")- Prerequisites at start of procedural content- Test all code examples before publishing- Match style and formatting of existing pages- Include both basic and advanced use cases- Language tags on all code blocks- Alt text on all images- Relative paths for internal links## Git workflow- NEVER use --no-verify when committing- Ask how to handle uncommitted changes before starting- Create a new branch when no clear branch exists for changes- Commit frequently throughout development- NEVER skip or disable pre-commit hooks## Do not- Skip frontmatter on any MDX file- Use absolute URLs for internal links- Include untested code examples- Make assumptions - always ask for clarification---> Converted and distributed by [TomeVault](https://tomevault.io/claim/short-ventures) — claim your Tome and manage your conversions.

Frequently asked questions

Update Docs