CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

56

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

56%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 is well-structured with clear progressive disclosure to 9 reference files and a solid sequenced workflow, but it suffers from heavy cross-sectional repetition and lacks concrete worked examples of its deliverables.

Suggestions

Consolidate the redundant guidance across Task / Core Function / Execution / Hard Rules / What This Skill Should Not Do / Quality Standard into a single authoritative section to reduce token bloat.

Add at least one worked example deliverable (a sample image-generation prompt, a sample Mermaid flowchart, or a sample designer handoff brief) to lift actionability.

Trim the restated 'recommend uploading protocol/title-abstract/figure-list' instruction, which appears in at least four separate sections.

DimensionReasoningScore

Conciseness

The same core guidance (clarify first, don't overclaim, route by capability, explain logic, recommend uploads) is restated across Task, Core Function, Execution, Mandatory Output Structure, Formatting Expectations, Hard Rules, What This Skill Should Not Do, and Quality Standard — noticeably verbose with several padded, duplicative sections.

2 / 5

Actionability

Provides a concrete Mandatory Output Structure (sections A-J with specific sub-bullets) and named block categories, but lacks any worked example (no sample prompt, Mermaid, or storyline), leaving key execution details unspecified.

3 / 5

Workflow Clarity

A clear 9-step numbered sequence with explicit validation checkpoints (Step 1 input clarification, Step 8 uncertainty flagging, Output A Input Match Check, Output I Claim Boundary Check); minor gaps in that checkpoints are clarification-oriented rather than validate-fix-retry loops.

4 / 5

Progressive Disclosure

Body is an overview pointing to 9 real, one-level-deep reference files in references/, each well-signaled with a 'Use to/Use when' note; all referenced paths exist and navigation is easy.

5 / 5

Total

14

/

20

Passed

Description

75%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 specific and distinctive with concrete actions in proper third-person voice, but it omits an explicit 'when to use' trigger clause, which caps completeness and leaves trigger guidance implicit.

Suggestions

Add an explicit 'Use when...' clause listing natural trigger phrases (e.g., 'Use when the user asks to generate a graphical abstract, convert a paper into a visual summary, or produce a Mermaid/figure version of a study').

Include common synonyms users might say such as 'figure', 'visual summary', or 'graphical summary' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person — 'Converts a biomedical study storyline into a graphical abstract', 'generates the graphical abstract directly', 'falls back to prompts, Mermaid flowcharts, or designer-facing briefs' — covering the domain comprehensively.

5 / 5

Completeness

Has a clear 'what' (converts storyline to graphical abstract with direct/fallback routing) but no explicit 'Use when...' clause or trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('graphical abstract', 'Mermaid flowcharts', 'designer-facing briefs') but misses common synonyms a user might naturally say such as 'figure', 'visual summary', or 'graphical summary'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — biomedical study storyline to graphical abstract — with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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.

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