markdown-toc

Extract a Markdown heading tree with line numbers before editing or integrating notes. Use when you need to inspect a long Markdown file quickly and choose the best insertion point instead of editing blind.

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

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

The content is a tight, executable guide: a real bundled script, concrete invocation examples, and a clear workflow with no wasted tokens. The only minor gap is the lack of explicit verification steps, which is largely justified by the read-only nature of the task.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept padding (no explanation of what Markdown is), well-organized sections, and every block earning its place, matching the lean-and-efficient anchor.	5 / 5
Actionability	It provides a copy-paste-ready command with concrete example targets and shows the exact output format, fully covering the common case of extracting a TOC.	5 / 5
Workflow Clarity	A clear five-step sequence is present, but there are no explicit validation checkpoints; this is acceptable for a read-only inspection skill, placing it just below the explicit-validation anchor.	4 / 5
Progressive Disclosure	At under 50 lines with well-organized sections and a single one-level-deep, clearly signaled bundled script reference (verified to exist), it meets the simple-skill exception for full marks.	5 / 5
	Total	19 / 20 Passed

Description

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

The description clearly states a single concrete capability and pairs it with explicit, natural trigger guidance, making the what and when unambiguous. It is held back only by narrow action coverage and a few missing synonyms that would broaden trigger matching.

Suggestions

Add 1-2 more concrete actions (e.g., "list headings with line numbers, jump to a section") to lift specificity from a single action toward comprehensive coverage.

Include common synonyms in the trigger clause such as "table of contents", "outline", or ".md files" so users who phrase the need differently still match.

Sharpen the niche wording to reduce overlap with general markdown-editing skills, e.g., emphasize read-only heading inspection rather than editing.

Dimension	Reasoning	Score
Specificity	"Extract a Markdown heading tree with line numbers" names the domain and one concrete action, but lists no further capabilities, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It explicitly answers what ("Extract a Markdown heading tree with line numbers") and when ("Use when you need to inspect a long Markdown file quickly and choose the best insertion point") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases like "inspect a long Markdown file quickly" and "choose the best insertion point" are present, but common synonyms such as "table of contents", "outline", or ".md" are missing, leaving a few natural terms absent.	4 / 5
Distinctiveness Conflict Risk	Markdown heading-tree extraction is a mostly distinct niche with clear triggers, though it has minor overlap risk with general markdown-editing skills rather than minimal conflict risk.	4 / 5
	Total	16 / 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: huangruiteng/CS-Notes
Path: .codex/skills/markdown-toc/SKILL.md
Commit: 5d012c4

Reviewed: 7 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.