mintlify-docs-updater

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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, actionable skill body with executable commands, a validation checkpoint, and well-structured one-level-deep references that match the actual bundle. The main gap is the lack of an explicit fix-and-retry loop around the validation step.

Suggestions

Add an explicit feedback loop after the Validate step (e.g., 'If docs.json is missing the route, re-run with the correct --group/--subgroup; if frontmatter is incomplete, edit the generated file before committing') to push workflow_clarity to 5.

Reduce repetition between the Workflow and Commands sections by referencing the canonical invocation once and listing only the variant flags in Commands.

Dimension	Reasoning	Score
Conciseness	Lean, well-organized body with no padding or explanation of concepts Claude already knows; the Commands section re-shows the same script invocation across variants, which is slightly repetitive but justified by distinct use cases, keeping it just under a 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready python3 commands with concrete flags (--source, --page, --group, --subgroup, --insert-after, --dry-run) and multiple examples covering the common cases.	5 / 5
Workflow Clarity	Clear numbered workflow with an explicit Validate step (confirm file exists, docs.json entry present, frontmatter present) and a dry-run suggestion; stops short of 5 because there is no validate-then-fix-retry feedback loop for the file/docs.json batch write.	4 / 5
Progressive Disclosure	Overview body points to clearly signaled one-level-deep references (references/docs-structure.md, references/content-format.md, scripts/ingest_markdown_doc.py), all of which exist as real bundle files, with content appropriately split rather than inlined.	5 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill does and when to use it, anchored to a specific repo and tooling. Minor gains available from more granular action enumeration and a few extra synonyms.

Dimension	Reasoning	Score
Specificity	Names the Mintlify-docs domain and several concrete actions ("add, update, or organize docs pages", "place new content under get_started/core/core/models/troubleshooting", "keep docs/docs.json navigation in sync"); falls short of 5 because the actions are stated at a slightly higher level than fully enumerated granular operations.	4 / 5
Completeness	Explicitly answers both "what" (maintain Mintlify docs from uploaded Markdown) and "when" ("Use when asked to add, update, or organize docs pages in docs/, place new content under ... and keep docs/docs.json navigation in sync") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ("add docs pages", "update", "organize docs pages", "Mintlify", "docs.json") but omits common synonyms like "documentation pages" or file-extension terms; not quite the comprehensive coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (this repository's Mintlify docs tree with named sections and docs.json) with distinct triggers, giving minimal conflict risk with unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: eigent-ai/agent-skills
Path: skills/coding-agents-and-ides/mintlify-docs-updater/SKILL.md
Commit: 9be8efc

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.