CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mindmap-html-generator

Generate offline interactive mindmap HTML and convert Markdown, outlines, meeting notes, chapter structures, or JSON trees into markmap-compatible format. Use when organizing long text into mindmaps, converting meeting notes to mindmap pages, generating final HTML via markmap-cli, or adding browsable mindmaps to deliverables.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/mindmap-html-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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's core is strong: a well-sequenced workflow with real validation and feedback loops, and configuration guidance that matches the bundled script exactly. Its weakness is token efficiency — four overlapping rule sections repeat the same structural advice, and roughly half the tail of the file is generic boilerplate that dilutes the actionable content.

Suggestions

Collapse 'Content Richness Requirements', 'Information Extraction Priority', 'Paper Input Enhancement Rules', and 'Prohibited Behaviors' into one deduplicated 'Structuring rules' section (or move them into references/input-patterns.md alongside the templates), since they repeatedly state the same keep-details/don't-compress guidance.

Delete or drastically trim the generic boilerplate sections ('When to Use', 'When Not to Use', 'Required Inputs', 'Output Contract', 'Failure Handling', 'User Checkpoints', 'Input Validation', 'Quick Validation') — statements like 'Use this skill when the user explicitly needs to perform the core task of mindmap-html-generator' are circular and consume context without adding skill-specific guidance.

Add a short filled-in example of the CONFIG block (input_path, output_html_path, page_title set to real values) in step 3 so the configure-then-run path is fully copy-paste ready, closing the actionability gap.

DimensionReasoningScore

Conciseness

Four overlapping rule sections ("Content Richness Requirements", "Information Extraction Priority", "Paper Input Enhancement Rules", "Prohibited Behaviors") repeat the same guidance multiple ways ("conciseness does not mean deleting details", "do not sacrifice information density for brevity", "do not omit key numbers, key steps..."), and roughly 60 lines of generic boilerplate ("When to Use" — which circularly says to "perform the core task of mindmap-html-generator" — plus "Output Contract", "User Checkpoints", "Input Validation", "Quick Validation") add no skill-specific value. This goes beyond the 'some unnecessary explanation' of anchor 3 and matches anchor 2 (noticeably verbose, several padded sections), though it avoids anchor 1 since it never explains background concepts Claude already knows.

2 / 5

Actionability

The body gives the exact run command (`python scripts/generate_mindmap_html.py`), CONFIG option names that match the bundled script (input_path, output_html_path, auto_bold_levels, plain_text_root_max_children, and MARKMAP_INIT_OPTIONS["colorFreezeLevel"]), and concrete structural rules (depth 2-4 levels, at least 6 level-1 branches, 3-6 level-2 nodes). The main gap is that no filled-in CONFIG example is shown, so it sits at anchor 4 (mostly executable, minor gaps) rather than the fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

The workflow is a clearly sequenced 5-step process (determine input source, organize structure, configure script, run script, validate results) with explicit validation checks ("Confirm only level-1 and level-2 headings remain bold") and error-recovery feedback loops ("If nodes are too long, go back to compress input text, then re-run the script"; install Node.js if npx is missing), matching anchor 5. It does not fall to anchor 4 because checkpoints and retry loops are fully present rather than having minor gaps.

5 / 5

Progressive Disclosure

Both referenced bundle files exist and are clearly signaled one level deep ("Read when deciding how to organize input — contains recommended structure templates and examples"), and the Resources section accurately describes the script and reference file. However, ~80 lines of generic policy boilerplate (When to Use / When Not to Use / Required Inputs / Output Contract / Failure Handling / User Checkpoints / Input Validation / Quick Validation) sit inline in SKILL.md where they should be trimmed or split out, so content placement has minor organization gaps — anchor 4 rather than the appropriately-split anchor 5.

4 / 5

Total

15

/

20

Passed

Description

87%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: it explicitly states what the skill does and when to use it with concrete, natural trigger phrases, and it is tightly scoped to the markmap mindmap niche. Minor improvement is possible by adding a few more trigger synonyms or extensions, but nothing essential is missing.

DimensionReasoningScore

Specificity

"Generate offline interactive mindmap HTML and convert Markdown, outlines, meeting notes, chapter structures, or JSON trees into markmap-compatible format" names the output artifact, the tool (markmap-cli), and five concrete input types. It lists several specific actions but the action list reduces to two verbs with minor coverage gaps (e.g., intermediate Markdown, configuration/styling), fitting anchor 4 rather than the comprehensive multi-action coverage of anchor 5.

4 / 5

Completeness

Both halves are explicit: the what ("Generate offline interactive mindmap HTML and convert ... into markmap-compatible format") and the when ("Use when organizing long text into mindmaps, converting meeting notes to mindmap pages, generating final HTML via markmap-cli, or adding browsable mindmaps to deliverables") with four concrete trigger phrases, matching the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

Natural trigger terms are present and varied — "mindmaps", "meeting notes", "long text", "browsable mindmaps", "Markdown", "markmap-cli" — phrases a user would plausibly say. A few natural variants are missing (e.g., the spaced "mind map", file extensions like .md/.html), so it fits anchor 4 (good coverage, a few terms missing) rather than the synonym-and-extension-complete anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche — markmap-compatible mindmap HTML generation — with distinct, specific triggers ("markmap", "mindmap pages", "organizing long text into mindmaps") that are unlikely to fire for unrelated skills. Third-person voice is used throughout ("Generate", "convert"), and there is no generic language that would overlap with broad document or file skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/mindmap-html-generator/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.