CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

59

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

46%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 good file-based structure and clear references, but is weighed down by extensive generic process boilerplate and delegates its central parse/render action to the reference without executable detail in SKILL.md. Tightening the template prose and inlining a minimal concrete loading snippet would substantially improve it.

Suggestions

Remove or collapse the generic template sections ('Required Inputs', 'Deterministic Output Rules', 'Output Contract', 'Failure Handling', 'Completion Checklist', 'Scope Reminder') that restate what Claude already knows, keeping only mindmap-specific guidance.

Inline a minimal, concrete Plain Text loading snippet (or the exact step for getting text into assets/local-mindmap/index.html) so the central rendering action is executable from SKILL.md rather than deferred to the reference.

Tighten the 'Recommended Workflow' and 'Quick Validation' so the validation checkpoint is specific to mindmap output (e.g. verify the node tree depth and that the HTML renders) instead of the current 'no local script validation step is required'.

DimensionReasoningScore

Conciseness

Roughly two-thirds of the body ('When Not to Use', 'Required Inputs', 'Recommended Workflow', 'Deterministic Output Rules', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', 'Completion Checklist', 'Scope Reminder') is generic process boilerplate that restates what Claude already knows rather than skill-specific guidance, making it noticeably padded.

2 / 5

Actionability

It names concrete files and gives a Plain Text example, but the core rendering step is delegated as 'follow the format and loading instructions described in references/...' with no executable parse/render code in SKILL.md, leaving the key execution details incomplete.

3 / 5

Workflow Clarity

A numbered Example Usage sequence and a Recommended Workflow with a validation pass exist, but the pivotal step 3 ('load/insert the Plain Text content') is left implicit and the Quick Validation states 'No local script validation step is required', leaving checkpoints weak.

3 / 5

Progressive Disclosure

SKILL.md acts as an overview with a clearly signaled, one-level-deep reference (references/streaming-implementation.md, which exists) and a named HTML asset, with only minor bloat from the generic boilerplate sections.

4 / 5

Total

12

/

20

Passed

Description

92%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.

The description is strong: it concretely names multiple capabilities and pairs a clear 'what' with an explicit 'use when' trigger clause, giving it a well-scoped niche. The only gap is slightly incomplete natural-term coverage (missing common synonyms/extensions).

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Generate mindmaps locally/offline with native HTML/CSS/JS', 'parse Plain Text node structures', 'map LLM outputs into an on-device visualization' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (generate/parse/map mindmaps with native HTML/CSS/JS) and 'when' via a concrete 'use when you need to parse Plain Text node structures or map LLM outputs into an on-device visualization' trigger clause.

5 / 5

Trigger Term Quality

Includes natural terms like 'mindmaps', 'Plain Text node structures', 'LLM outputs', and 'on-device visualization', but misses common synonyms and file extensions (e.g. 'mind map', '.html', 'tree diagram'), so it falls just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The offline/zero-dependency native HTML/CSS/JS mindmap niche is clearly distinct, with trigger phrases unlikely to fire for unrelated skills and minimal overlap risk.

5 / 5

Total

19

/

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.

Validation14 / 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
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.