CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

graphical-abstract-generator

Converts a biomedical study storyline into a graphical abstract and, when direct image capability is available, generates the graphical abstract directly; otherwise it falls back to prompts, Mermaid flowcharts, or designer-facing briefs.

Quality

65%

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 ./awesome-med-research-skills/Academic Writing/graphical-abstract-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 has a genuinely clear workflow with validation checkpoints and a well-wired, one-level-deep reference bundle, but the body states each core rule four to eight times across overlapping sections and never defines its key artifact formats. Deduplicating and adding one compact example per deliverable route would substantially improve it.

Suggestions

State each directive exactly once: keep the Execution steps and Mandatory Output Structure, and delete the repeated formulations in Task, Core Function, Scope Boundary, Important Distinctions, Formatting Expectations, and What This Skill Should Not Do.

Remove the inline Hard Rules section entirely (it duplicates references/hard-rules.md) and replace it with a one-line pointer, or drop the duplicate reference file.

Define the citation-support marker concretely (e.g., its literal format) and add one compact example per route — a sample image-generation prompt, a sample Mermaid flowchart, and a sample designer-brief skeleton.

DimensionReasoningScore

Conciseness

The ~295-line body is heavily padded by repetition: 'prioritize direct generation when available / never pretend it is not' appears in Task item 7, Core Function 3-4, Step 5, Output Structure E and F, Formatting Expectations, Hard Rule 10, and Quality Standard; the ask-for-input directive recurs in Task item 6, Input Validation, Step 1, Step 8, Output Structure A and J, and Hard Rule 3; and the Hard Rules section fully duplicates references/hard-rules.md inline. This is noticeably below the mostly-efficient anchor and even further from lean, though it avoids explaining concepts Claude already knows, so it sits at 2 rather than 1.

2 / 5

Actionability

The nine Execution steps and the mandatory A-J output structure give a concrete scaffold, but key executable details are missing: the 'required citation-support marker' is never defined or exemplified, there is no example image-generation prompt, Mermaid flowchart, or designer-brief template, and no sample PubMed query format. This matches the anchor of some concrete guidance but incomplete, with key details missing.

3 / 5

Workflow Clarity

Steps 1-9 are clearly sequenced with explicit checkpoints: Step 1 (clarify before generating), the Input Match Check in Section A, Step 8 flagging remaining uncertainty, and the Claim Boundary Check in Section I. It falls short of 5 because the feedback loop is one-directional — there is no explicit 'once the user supplies the missing input, restart from Step 1' recovery path — and the redundancy across sections muddies which directives are operative.

4 / 5

Progressive Disclosure

The Reference Module Integration section lists all nine real bundle files with one-line purposes, and verification shows the references are one level deep with no nested pointers — good structure. However, content that belongs only in the reference files is duplicated inline (the Hard Rules section restates references/hard-rules.md verbatim, and the format-routing logic repeats references/format-routing-rules.md), which keeps it at the minor-organization-gaps anchor rather than 5.

4 / 5

Total

13

/

20

Passed

Description

62%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 specific, well-scoped description in third person that clearly names its niche and deliverable routes, but it lacks any 'Use when...' trigger clause and misses natural synonyms like 'visual abstract' or 'paper/manuscript'. Adding explicit trigger guidance would raise completeness and trigger-term quality.

Suggestions

Append a trigger clause such as 'Use when the user asks for a graphical abstract or visual abstract for a biomedical paper, manuscript, or study, or wants a Mermaid flowchart, image-generation prompt, or designer brief for one.'

Include the common synonym 'visual abstract' and user-facing nouns like 'paper' and 'manuscript' so retrieval matches how researchers naturally phrase the request.

Mention the citation-support annotation behavior, which the body treats as a mandatory part of every output, so the description reflects the full capability.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Converts a biomedical study storyline into a graphical abstract', 'generates the graphical abstract directly', 'falls back to prompts, Mermaid flowcharts, or designer-facing briefs' — naming the domain and enumerating the main deliverable routes. It falls short of the 5 anchor because secondary capabilities the body treats as core (citation-support annotation, clarification-first behavior) are absent, and 'study storyline' is somewhat abstract.

4 / 5

Completeness

The 'what' is clearly answered (convert biomedical study storylines into graphical abstracts, with direct generation and fallback routes), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, capping this dimension at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'graphical abstract' is the natural phrase users would say and it appears twice, plus 'Mermaid flowchart' and 'designer-facing briefs'. However common variations are missing — 'visual abstract' (a frequent synonym in biomedical publishing), 'paper', 'manuscript', 'journal figure' — so keyword coverage is partial rather than good.

3 / 5

Distinctiveness Conflict Risk

'biomedical study storyline into a graphical abstract' carves out a clear niche with distinct triggers — graphical abstract generation for biomedical research — that would not plausibly fire for document, data-analysis, or general figure skills, matching the clear-niche/minimal-conflict anchor.

5 / 5

Total

15

/

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

awesome-med-research-skills/Academic Writing/graphical-abstract-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.