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

85%

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: a verified runnable script, an explicit workflow with a clear insert-vs-create decision rule, and a literal output example. The only weaknesses are a redundant "Use this skill when" section duplicating the frontmatter description, repository-specific example paths that add noise, and no validation step after the edit is made.

Dimension	Reasoning	Score
Conciseness	The body is lean with no explanations of concepts Claude already knows, but the "Use this skill when" section largely duplicates the frontmatter description and the second quick-start block of repository-specific example paths is niche filler, so it fits the 4 anchor (minor trimmable over-content) rather than the fully lean 5.	4 / 5
Actionability	Fully executable and copy-paste ready: "python3 {baseDir}/scripts/extract_toc.py /absolute/path/to/file.md" (the bundled script exists at scripts/extract_toc.py), concrete neighborhood-reading commands "sed -n '<start>,<end>p'" or "nl -ba", and a literal output-format example, matching the 5 anchor.	5 / 5
Workflow Clarity	A clear five-step sequence with an explicit decision rule ("Insert into an existing section when possible. Create a new section only when the file truly lacks a clean landing spot"), but there is no post-edit validation checkpoint, fitting the 4 anchor; the destructive/batch cap of 3 does not apply since this is a read-then-insert flow, not a batch or destructive operation.	4 / 5
Progressive Disclosure	Under 50 lines with well-organized sections and no need for external reference files; the only bundle reference (scripts/extract_toc.py) is real, correctly pathed, and one level deep, so per the under-50-lines guideline this matches the 5 anchor.	5 / 5
	Total	18 / 20 Passed

Description

83%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: third-person, concrete about both capability and trigger, with an explicit Use-when clause covering the inspect-and-insert flow. The only gaps are missing common synonyms ("table of contents", "outline", ".md") and a slightly broad editing context that could overlap other note-editing skills.

Dimension	Reasoning	Score
Specificity	"Extract a Markdown heading tree with line numbers" plus "inspect a long Markdown file quickly and choose the best insertion point" names the domain and several concrete actions in third person, matching the 4 anchor; not 5 because a single-purpose skill lists one core capability rather than a comprehensive set of actions.	4 / 5
Completeness	Both parts are explicit: the what ("Extract a Markdown heading tree with line numbers before editing or integrating notes") and a concrete when ("Use when you need to inspect a long Markdown file quickly and choose the best insertion point instead of editing blind"), mirroring the structure of the 5 anchor example.	5 / 5
Trigger Term Quality	Natural phrases like "Markdown", "editing", "integrating notes", "long Markdown file", and "insertion point" are present and user-sayable, but common synonyms such as "table of contents", "outline", "TOC", or the ".md" extension are missing, so it fits the 4 anchor rather than 5.	4 / 5
Distinctiveness Conflict Risk	"Markdown heading tree with line numbers" is a clear, distinct niche, but the use-context "before editing or integrating notes" is broad enough to overlap generic markdown/note-editing skills, placing it at 4 rather than 5.	4 / 5
	Total	17 / 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: 77c775d

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