CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mindmap

Generate mindmaps locally/offline with native HTML/CSS/JS (no external libraries); use when you need to parse Plain Text node structures or map LLM outputs into an on-device visualization.

Quality

69%

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/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 has a clear getting-started shape (When to Use, Example Usage, Implementation Details) with a real one-level-deep reference file, but it is undermined by ~80 lines of generic filler boilerplate and by repeatedly pointing to assets/local-mindmap/index.html, which is missing from the bundle. As written, the documented end-to-end workflow cannot be executed.

Suggestions

Ship or remove the missing core asset: create assets/local-mindmap/index.html as described, or replace the 'open the template' step with actual inline instructions for producing the single-file HTML.

Delete the generic boilerplate sections (When Not to Use, Required Inputs, Recommended Workflow, Deterministic Output Rules, Output Contract, Validation and Safety Rules, Failure Handling, Completion Checklist, Scope Reminder) — they add no mindmap-specific knowledge and roughly halve the file for free.

Replace the empty 'Quick Validation' section with one concrete checkpoint, e.g. verify the parsed node count/depth against the input text or the expected browser rendering described in references/streaming-implementation.md.

DimensionReasoningScore

Conciseness

Roughly half the body (~80 lines across 'When Not to Use', 'Required Inputs', 'Recommended Workflow', 'Deterministic Output Rules', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', 'Completion Checklist') is generic boilerplate that applies to any skill and tells Claude things it already knows (e.g., "Validate required inputs before execution", "Do not fabricate... findings"). Several padded sections with no skill-specific value, matching the 'noticeably verbose' anchor.

2 / 5

Actionability

Concrete elements exist (a runnable mindmap.txt example, a real references/streaming-implementation.md), but the central artifact assets/local-mindmap/index.html does not exist, so the 'Open the renderer template' step cannot actually be executed, and step 3 defers entirely to the reference. Some concrete guidance, but the key executable piece is missing.

3 / 5

Workflow Clarity

The Example Usage section gives a well-defined 3-step sequence (create txt file → open template → load content), but there is no validation checkpoint anywhere; 'Quick Validation' explicitly declares "No local script validation step is required for this skill". Sequence present, checkpoints absent, matching the middle anchor.

3 / 5

Progressive Disclosure

Against the actual bundle: references/streaming-implementation.md exists, is one level deep and clearly signaled, but assets/local-mindmap/index.html is referenced three times and is absent (no assets/ directory), leaving the skill's most important pointer dangling. Structure exists but the broken core reference prevents a higher score.

3 / 5

Total

11

/

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: it states concrete capabilities in third person, includes an explicit 'use when' trigger clause, and carves out a recognizable niche. Its only weaknesses are incomplete synonym coverage for trigger terms and slight overlap risk with general visualization skills.

DimensionReasoningScore

Specificity

Names several concrete actions — "Generate mindmaps locally/offline with native HTML/CSS/JS", "parse Plain Text node structures", "map LLM outputs into an on-device visualization" — with only minor coverage gaps (layout/customization unmentioned). Fits the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.

4 / 5

Completeness

Explicitly answers both: what ("Generate mindmaps locally/offline with native HTML/CSS/JS (no external libraries)") and when ("use when you need to parse Plain Text node structures or map LLM outputs into an on-device visualization"). Both are concrete and trigger-shaped, matching the top anchor.

5 / 5

Trigger Term Quality

Natural terms like "mindmaps", "locally/offline", "LLM outputs", and "visualization" match what users would say, but synonyms such as "mind map" (two words), "concept map", or "tree diagram" are missing. Good coverage with a few natural terms absent.

4 / 5

Distinctiveness Conflict Risk

Offline, zero-dependency mindmap rendering is a clear niche with distinct triggers, but "map LLM outputs into an on-device visualization" has minor overlap risk with general visualization skills. Mostly distinct rather than fully conflict-free.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 3 missing, 3 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

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