Reorganizes markdown documents into well-structured, consistent format while preserving content and improving readability. Use when Claude needs to: (1) Fix heading hierarchy issues (skipped levels, multiple h1s), (2) Generate or update table of contents, (3) Standardize formatting (lists, code blocks, emphasis, links), (4) Improve grammar and spelling, (5) Add missing standard sections (installation, usage, etc.), (6) Remove redundant or duplicate content, (7) Restructure technical docs, READMEs, or long-form content for better organization and flow.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill markdown-document-structurer88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates specific capabilities and provides explicit trigger conditions through a numbered list. The main weakness is trigger term coverage - while the technical actions are well-described, it could benefit from more natural user phrases that people might actually say when requesting this type of help.
Suggestions
Add natural user phrases like '.md files', 'clean up my markdown', 'format my README', or 'organize this document' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: fix heading hierarchy, generate/update TOC, standardize formatting, improve grammar/spelling, add missing sections, remove redundant content, and restructure documents. | 3 / 3 |
Completeness | Clearly answers both what (reorganizes markdown with specific actions listed) and when (explicit 'Use when Claude needs to:' clause with seven numbered trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'markdown', 'table of contents', 'READMEs', 'technical docs', but misses common user phrases like '.md files', 'format my document', 'clean up markdown', or 'organize my README'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on markdown document reorganization and formatting. The combination of markdown-specific actions (heading hierarchy, TOC, README restructuring) creates a distinct trigger profile unlikely to conflict with general writing or code skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and clear workflow progression. The main weakness is moderate verbosity - some sections explain concepts Claude already understands (basic grammar rules, what markdown formatting is) and could be trimmed. The progressive disclosure and workflow clarity are excellent, with appropriate references to external documents and clear step sequencing.
Suggestions
Trim the 'Grammar and Spelling' section - Claude knows basic grammar rules; focus only on domain-specific guidance like preserving technical terms
Condense 'Content Preservation Rules' into a shorter list - the distinctions between 'safe to modify' and 'never' are largely obvious to Claude
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation that Claude would already know (e.g., explaining what grammar fixes are, basic markdown concepts). Several sections could be tightened, such as the verbose 'Content Preservation Rules' and 'Grammar and Spelling' sections. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific examples throughout. The workflow steps are clear with actual commands, the formatting standards give exact syntax to use, and the redundancy handling includes before/after examples that are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit sequencing (analyze → identify → plan → apply → verify). The 'Apply Restructuring' section has ordered sub-steps, and the verification step provides a concrete checklist. The workflow is well-structured for a non-destructive document transformation task. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections and well-signaled one-level-deep references to external files (document-patterns.md, markdown-best-practices.md). Content is appropriately split between the main skill and reference documents, with inline content kept to actionable guidance. | 3 / 3 |
Total | 11 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Table of Contents
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.