CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

90%

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

92%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 lean, highly actionable skill body: executable commands with concrete repo examples, an unambiguous workflow, and a well-organized structure whose bundle reference checks out. The only trimmable content is the "Use this skill when" section, which duplicates the frontmatter description.

Suggestions

Cut or compress the "Use this skill when" bullet list, since it repeats the frontmatter description almost verbatim and adds little new information.

Consider folding the repository-specific example commands into a single line to save tokens.

DimensionReasoningScore

Conciseness

Sections are lean with concrete commands and no concept explanations, but the "Use this skill when" bullet list largely restates the frontmatter description — a minor instance of over-explanation that could be trimmed, placing it just below "every token earns its place".

4 / 5

Actionability

Fully executable, copy-paste-ready commands ("python3 \"{baseDir}/scripts/extract_toc.py\" ...", "sed -n '<start>,<end>p'", "nl -ba") plus concrete repo-specific examples and a sample of the output format cover the common cases.

5 / 5

Workflow Clarity

The 5-step workflow is an unambiguous sequence, and as a simple, read-only skill under 50 lines with no destructive or batch operation, it qualifies for the simple-skill exception: the single action chain is clear without explicit validation checkpoints.

5 / 5

Progressive Disclosure

At under 50 lines with no need for external references, the body is well-organized into clearly headed sections, and its one bundle reference (scripts/extract_toc.py) is real, correctly pathed, and clearly signaled.

5 / 5

Total

19

/

20

Passed

Description

82%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 that answers both what and when with concrete, natural trigger phrases and a clearly distinct niche. The only gap is that it names a single action and omits the "TOC"/"table of contents" synonym users might naturally say.

Suggestions

Add a second concrete action or outcome (e.g., "choose the best insertion point for new content") to the 'what' clause to lift specificity from one action to several.

Include "TOC" or "table of contents" as a trigger synonym, since the skill name itself (markdown-toc) is a phrase users would naturally say.

DimensionReasoningScore

Specificity

"Extract a Markdown heading tree with line numbers" names the domain and one concrete action, but no second distinct action is listed, matching the "1-2 concrete actions, not comprehensive" anchor rather than the "several specific actions" anchor above.

3 / 5

Completeness

Both "what" ("Extract a Markdown heading tree with line numbers") and an explicit, concrete "when" clause ("Use when you need to inspect a long Markdown file quickly and choose the best insertion point") are clearly stated, matching the top anchor rather than anchor 4's weaker 'when'.

5 / 5

Trigger Term Quality

Natural phrases like "inspect a long Markdown file", "editing", "notes", and "heading" are present, but "TOC"/"table of contents" — the skill's own name — is missing as a trigger synonym, fitting "good keyword coverage; a few natural terms missing".

4 / 5

Distinctiveness Conflict Risk

"Markdown heading tree" carves a clear niche with distinct triggers (Markdown files, headings, insertion points), with minimal overlap risk against other skills.

5 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

huangruiteng/CS-Notes

Path

.codex/skills/markdown-toc/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.