CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

format-markdown

Write or edit well-structured Markdown and MDX. Use for front matter, headings, lists, code fences, links, tables, other Markdown mechanics, and site-specific extensions. Pair with the write-technical-docs skill when changing prose.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/format-markdown/SKILL.md
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, well-structured conventions reference with concrete syntax examples and a single well-signaled one-level reference. It assumes Claude's competence and avoids padding; the main improvement would be consolidating repeated write-technical-docs cross-references and adding a few more copy-paste examples.

Suggestions

Consolidate the repeated 'follow write-technical-docs' pointers into one explicit boundary statement to reduce redundancy.

Add copy-paste examples for the rules currently stated only as negatives (e.g. heading-level skipping, trailing-whitespace handling).

Consider moving the longer syntax catalogs (alerts, definition lists) into a reference file to strengthen the overview-to-detail split.

DimensionReasoningScore

Conciseness

Lean bullet conventions with almost no over-explanation of concepts Claude already knows (no 'what is Markdown' padding). Not a 5 because some repeated cross-references to write-technical-docs across sections could be consolidated.

4 / 5

Actionability

Concrete, executable syntax guidance throughout ('## Section, not ##Section', 'Use 1. for every item', definition-list and alert examples). Not a 5 because a few areas give rules without a copy-paste example, leaving minor gaps.

4 / 5

Workflow Clarity

Well-organized into clear topical sections with an explicit precedence rule ('Apply these conventions unless the target project specifies otherwise'). Not a 5 because it is a multi-convention reference rather than a single unambiguous action, so the simple-skill 5 does not cleanly apply.

4 / 5

Progressive Disclosure

Good section structure with one clearly signaled, one-level-deep reference ('Read [Semantic line breaks](references/semantic-line-breaks.md)') that resolves to a real file. Not a 5 because most material is inline and the overview-vs-detail split could be more pronounced.

4 / 5

Total

16

/

20

Passed

Description

75%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 solid, concise description that names the domain, enumerates concrete mechanics, and includes an explicit 'Use for' trigger clause plus cross-skill boundary guidance. Main gap is that the 'when' mirrors the 'what' and natural trigger phrases could be more user-facing.

Suggestions

Add user-facing trigger phrasing to the 'when' clause, e.g. 'Use when the user asks to format, reformat, or fix Markdown/MDX'.

Include file extensions like '.md' and '.mdx' to broaden natural keyword coverage.

Differentiate the 'when' from the 'what' by naming triggering situations rather than restating the mechanics list.

DimensionReasoningScore

Specificity

Lists several concrete mechanics ('front matter, headings, lists, code fences, links, tables') though the actions themselves are generic ('Write or edit'). Not a 5 because the verbs are not multiple distinct concrete actions, and not a 3 because the enumerated mechanics give comprehensive, specific coverage.

4 / 5

Completeness

Explicitly answers both what ('Write or edit well-structured Markdown and MDX') and when ('Use for front matter, headings, lists...'). Not a 5 because the 'when' largely restates the 'what' rather than giving distinct user-facing trigger phrases ('when the user mentions X').

4 / 5

Trigger Term Quality

Good natural keyword coverage ('Markdown', 'MDX', 'headings', 'lists', 'tables', 'code fences', 'front matter') that users would actually say. Not a 5 because file extensions like '.md' and '.mdx' and common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Clear Markdown/MDX formatting niche with explicit boundary guidance ('Pair with the write-technical-docs skill when changing prose'). Not a 5 because of the inherent overlap with the prose/wording skill, though it is actively managed.

4 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

flutter/website

Path

.agents/skills/format-markdown/SKILL.md

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.