CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mindmap-helper

Organize requirements into Markdown/JSON mind map structures; use when you need a hierarchical outline for mind map tools (e.g., XMind, ProcessOn, FreeMind) or for documentation planning.

Quality

77%

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

Quality

Content

67%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 skill's core content is genuinely strong — concrete rules, sensible defaults, and a complete worked example — but it is wrapped in ~100 lines of generic template boilerplate (validation/safety/failure/checklist sections, a no-op Quick Validation block, and a verbatim Scope Reminder) that wastes tokens and buries the real guidance. Trimming to the skill-specific sections would materially improve it.

Suggestions

Delete the generic boilerplate sections (Required Inputs, Recommended Workflow, Deterministic Output Rules, Output Contract, Validation and Safety Rules, Failure Handling, Completion Checklist, and the verbatim Scope Reminder) — they contain no mind-map-specific information and consume roughly half the token budget.

Remove the 'Quick Validation' section entirely: its code block states 'No local script validation step is required for this skill', which is pure padding.

Consider moving the 65-line full example output into references/mindmap_formats.md (keeping a short excerpt inline) and keep step 4's 'Validate consistency' concrete by tying it to the specific naming rules (5-9 siblings, noun phrases, no duplicates).

DimensionReasoningScore

Conciseness

Roughly half the body is generic compliance boilerplate that adds no skill-specific value: "Dependencies: None", "Required Inputs", "Recommended Workflow", "Deterministic Output Rules", "Output Contract", "Validation and Safety Rules", "Failure Handling", "Completion Checklist", a "Quick Validation" code block that literally states "No local script validation step is required for this skill", and a "Scope Reminder" that repeats the frontmatter description verbatim. This matches anchor 2 ('several unnecessary explanations or padded sections'); it avoids anchor 1 because the core sections (When to Use, Key Features, Implementation Details) contain real, specific guidance with no basic-concept explanations.

2 / 5

Actionability

The guidance is fully executable for this instruction-only skill: a complete worked example (input prompt plus a full 4-5 level Markdown output), explicit defaults ("default to Markdown with 4-5 levels"), the JSON node schema ("root node contains title and children"), and concrete naming rules ("Target 5-9 children per parent; split into sub-levels if exceeded", TBD/Optional/To confirm markers). This matches the anchor-5 'specific examples cover the common cases' standard; the JSON template is one level deep in references/mindmap_formats.md, which exists and contains it.

5 / 5

Workflow Clarity

The Implementation Details workflow gives a clear four-step sequence (confirm topic/audience/scope/depth -> structural draft then refine -> choose format -> "Validate consistency") with a completion checklist, and the operation is neither destructive nor batch so no feedback-loop cap applies. It falls short of anchor 5 because the validation step is an abstract consistency check rather than an explicit, concrete verification action, and the 'Quick Validation' section is a no-op rather than a real checkpoint.

4 / 5

Progressive Disclosure

One reference file (references/mindmap_formats.md) is well-signaled, one level deep, and verified to exist, and section headers organize the body. It stops short of anchor 5 because the signal is a single bare blockquote line and the ~65-line full example output is inlined in SKILL.md rather than the reference, while generic boilerplate sections dilute the overview role.

4 / 5

Total

15

/

20

Passed

Description

78%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 a strong, well-formed trigger: it states a clear capability, output formats, and an explicit 'use when' clause anchored by concrete tool names. Its only weaknesses are slightly thin action coverage and a few missing natural synonyms/file extensions.

DimensionReasoningScore

Specificity

"Organize requirements into Markdown/JSON mind map structures" names the domain and one concrete action with two output formats, but does not list several distinct actions (anchor 4 requires 'several specific actions'). It clearly exceeds anchor 2, which only names a domain with generic actions.

3 / 5

Completeness

Both parts are explicit: "Organize requirements into Markdown/JSON mind map structures" answers what, and "use when you need a hierarchical outline for mind map tools ... or for documentation planning" answers when with concrete trigger phrases. This matches the anchor-5 example pattern exactly and exceeds anchor 4, whose 'when' is less specific.

5 / 5

Trigger Term Quality

Natural phrases like "mind map", "hierarchical outline", and tool names "XMind, ProcessOn, FreeMind" plus "documentation planning" give good keyword coverage users would actually say. A few natural synonyms/extensions are missing (e.g., .xmind/.mm file extensions, "brainstorm", "tree structure"), so it falls just short of the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Naming specific mind map tools (XMind, ProcessOn, FreeMind) carves out a mostly distinct niche with minor overlap risk against generic outlining/documentation skills. The broad clause "or for documentation planning" keeps it from the fully distinct anchor 5, while it is far more specific than anchor 3's 'Works with document files'.

4 / 5

Total

16

/

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