CtrlK
BlogDocsLog inGet started
Tessl Logo

mastra-docs

Documentation guidelines for Mastra. Use this skill when creating, editing, moving, deleting, or reviewing Mastra documentation, sidebars, redirects, or docs components.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

An exemplary progressive-disclosure index: lean, well-organized, and routing readers to the right reference by page type. Its weakness is workflow clarity — the body indexes references rather than laying out an explicit, validated authoring sequence.

Suggestions

Add a short sequenced workflow for the most common task (e.g., edit -> update sidebar -> add redirect -> verify links) with an explicit validation/checkpoint step, so destructive operations like moves and deletions aren't only covered in a reference file.

Include one or two inline actionable snippets (e.g., the exact command or check used to verify redirects) so the body is executable without always opening a reference.

Make the relationship to the `docs-diagrams` skill explicit (when to use this skill vs. that one) to reduce overlap ambiguity for diagram-related doc edits.

DimensionReasoningScore

Conciseness

The body is extremely lean: a one-line directive, a numbered index with single-line reference descriptions, and two short closing notes — no padding and no explanation of concepts Claude already knows.

5 / 5

Actionability

Provides a concrete routing rule (path prefix to specific reference file, e.g. '/docs' -> DOC.md) and clear pointers, but defers all executable detail to the references rather than giving inline examples.

4 / 5

Workflow Clarity

The numbered list organizes reference categories but does not present an explicit multi-step workflow with validation checkpoints; for destructive doc operations (moves, deletions) verification is only referenced, not sequenced inline.

3 / 5

Progressive Disclosure

Clear overview pointing to eight real, one-level-deep reference files, each with a descriptive one-line label and a path-based selection rule, making navigation straightforward.

5 / 5

Total

17

/

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 concise, well-targeted description that explicitly answers both what it does and when to use it, with concrete actions and domain-specific trigger terms. The only minor gap is a few natural synonyms for documentation work.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('creating, editing, moving, deleting, or reviewing') across several specific objects ('Mastra documentation, sidebars, redirects, or docs components'), giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Clearly states what it does ('Documentation guidelines for Mastra') and gives an explicit 'when' with concrete trigger phrases ('Use this skill when creating, editing, moving, deleting, or reviewing...').

5 / 5

Trigger Term Quality

Natural, domain-relevant terms like 'documentation', 'sidebars', 'redirects', and 'docs components' are present and would be said by a user, but a few common synonyms ('writing/updating docs') are not covered.

4 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (Mastra documentation tooling) with distinct triggers, minimizing overlap with unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mastra-ai/mastra
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.