CtrlK
BlogDocsLog inGet started
Tessl Logo

mintlify

Build and maintain documentation sites with Mintlify. Use when creating docs pages, configuring navigation, adding components, or setting up API references.

88

1.07x
Quality

83%

Does it follow best practices?

Impact

97%

1.07x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 reference guide that earns its tokens with concrete commands, config snippets, and decision tables while deferring authoritative detail to the external docs. Main weakness is reference-style organization rather than an explicit validation-gated workflow, plus a few minor conciseness trim opportunities.

Suggestions

Weave the existing validation tools into an explicit pre-deploy sequence (e.g. run `mint validate` then `mint broken-links`, fix issues, then deploy) so the workflow has explicit checkpoints.

Tighten the opening by merging the redundant 'Always consult mintlify.com/docs' line and MCP paragraph with the Resources section at the end.

Add one short copy-pasteable JSX component example (e.g. a full `<Steps>` or `<Tabs>` block) so the most common components are actionable without an external lookup.

DimensionReasoningScore

Conciseness

The body is dense and efficient — terse decision tables and bullet lists with only one orienting sentence about the platform — but the opening MCP/redirect framing slightly overlaps the Resources section and could be trimmed.

4 / 5

Actionability

Provides executable CLI commands and exact config snippets (e.g. '"openapi": ["openapi.yaml"]', '"redirects": [...]'), with a minor gap that component JSX examples are deferred to mintlify.com/docs rather than shown inline.

4 / 5

Workflow Clarity

Content is organized into clear task-oriented sections with decision tables and named validation tools (mint validate, mint broken-links), though these are presented as reference commands rather than an explicit validate→fix→retry sequence.

4 / 5

Progressive Disclosure

Well-structured with clear section headers and one-level-deep, well-signaled external references to mintlify.com/docs for detail; no bundle files exist, and some sizable inline tables (navigation patterns, components) could arguably live in separate reference files.

4 / 5

Total

16

/

20

Passed

Description

92%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, well-scoped description that clearly states both capabilities and explicit trigger conditions for a named platform. Keyword coverage is the only mild weakness, missing synonyms and file extensions that users might naturally say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Build and maintain documentation sites', 'creating docs pages, configuring navigation, adding components, or setting up API references' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (build and maintain Mintlify documentation sites) and 'when' (Use when creating docs pages, configuring navigation, adding components, or setting up API references) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user-facing terms like 'docs pages', 'navigation', 'components', and 'API references', but lacks synonyms and file-extension variants (e.g. '.mdx', 'Mintlify site').

4 / 5

Distinctiveness Conflict Risk

Names a specific platform (Mintlify) with distinct triggers, making it unlikely to fire for unrelated documentation tasks and giving it minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
Arize-ai/phoenix
Reviewed

Table of Contents

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.