format-markdown-table

Generate well-formatted markdown tables from data with proper alignment and spacing. Use for report statistics, comparison tables, or summary data presentation.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/format-markdown-table/SKILL.md

Quality

Content

71%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 body is a clear, actionable, well-sequenced spec for formatting markdown tables with strong concrete examples. Its main weakness is progressive disclosure: it references a non-existent examples.md while inlining the example bulk, rather than keeping SKILL.md lean and pointing to real one-level-deep files.

Suggestions

Create the referenced examples.md (or remove the 'Supporting Files' line) so SKILL.md does not point at a dangling reference.

Move the four worked Examples into examples.md and keep only one representative example inline, reducing the body to a lean overview.

Make the column-width rule executable: show the concrete formula (max(header, values) + 2 padding, min 3) instead of describing it in prose.

Dimension	Reasoning	Score
Conciseness	Efficient and free of concepts Claude already knows, with lean step intros; minor trim possible where the Examples re-demonstrate the header/separator/row formats already shown in the steps.	4 / 5
Actionability	Provides copy-paste-ready format blocks for headers, separators with alignment indicators, and data rows, plus full input/output examples; just below a 5 because the column-width calculation is described in prose ('Determine maximum width', 'Add padding 1 space') rather than shown as a concrete algorithm.	4 / 5
Workflow Clarity	A clear 6-step sequence with per-step Expected Input/Output acting as implicit checkpoints and an Error Handling section for edge cases; not a 5 because there is no explicit validate-then-fix feedback loop and the Validation section is a static checklist rather than an in-workflow checkpoint.	4 / 5
Progressive Disclosure	Well-organized into sections, but the body is ~200 lines with bulk inlined examples while 'Supporting Files' references an examples.md that does not exist (no references/, scripts/, or assets/ bundles present), leaving a dangling reference and content that the doc itself says belongs in a separate file.	3 / 5
	Total	15 / 20 Passed

Description

70%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 clear, mostly-concise description that states both what it does and when to use it, with natural trigger phrases. It is held back from the top band by a single composite action (rather than several distinct ones) and trigger terms that lean on use cases rather than the artifact name itself.

Suggestions

Lead with the concrete artifact phrasing, e.g. 'Format data into markdown tables with column alignment and spacing' to sharpen specificity.

Add natural trigger synonyms users actually say, such as 'markdown table', 'format a table', or 'align table columns'.

Tighten the 'when' clause to name the deliverable explicitly, e.g. 'Use when outputting report statistics, comparison tables, or summary dashboards as markdown tables.'

Dimension	Reasoning	Score
Specificity	Names the domain and one composite concrete action ('Generate well-formatted markdown tables from data with proper alignment and spacing'), but does not enumerate multiple distinct actions, so it is not comprehensive.	3 / 5
Completeness	Both 'what' (generate formatted markdown tables with alignment and spacing) and 'when' (Use for report statistics, comparison tables, or summary data presentation) are present; the 'when' could be more explicit and trigger-rich.	4 / 5
Trigger Term Quality	'report statistics, comparison tables, or summary data presentation' are natural phrases a user might say, though a few common synonyms like 'markdown table' or 'table formatting' are missing.	4 / 5
Distinctiveness Conflict Risk	The markdown-table niche is fairly distinct; minor overlap risk with general reporting/presentation skills because the triggers are use-case oriented rather than artifact-specific.	4 / 5
	Total	15 / 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: maslennikov-ig/claude-code-orchestrator-kit
Path: .claude/skills/format-markdown-table/SKILL.md
Commit: 8c3b576

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