CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

graphical-abstract-wizard

Generate graphical abstract layout recommendations based on paper abstracts.

Quality

60%

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/Data Analysis/graphical-abstract-wizard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 core usage content (commands, parameters, examples, output format) is concrete and backed by a real working script, but it is buried in generic template boilerplate with duplicated command blocks, contradictory dependency claims, and a misleading example. Cutting the padding and fixing the inconsistencies would roughly halve the file while improving reliability.

Suggestions

Remove the generic template sections (Key Features, Implementation Details, Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) or move them to a separate reference file; they add no skill-specific information.

Fix the inconsistencies: Example 2's '-a "abstract.txt"' should read '-a "$(cat abstract.txt)"', delete the OpenAI API dependency and the nonexistent requirements.txt reference, and de-duplicate the repeated py_compile command blocks.

Replace the 'See ## Usage above' / 'See ## Workflow above' stubs and the off-domain 'data analysis tasks' trigger bullet with direct, accurate pointers, and move the full example output into an examples reference file.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: template boilerplate sections ('Scope-focused workflow aligned to:', 'Execution model: validate the request, choose the packaged workflow...'), a misplaced 'data analysis tasks' trigger bullet, the same py_compile command repeated across 'Quick Check', 'Example Usage', and 'Audit-Ready Commands', and stub navigation like 'See ## Usage above for related details.'

2 / 5

Actionability

There is real executable guidance (a verified 719-line script, a parameters table, runnable example commands), but key details are wrong or inconsistent: Example 2 passes a filename to -a where the table says abstract text is required, 'pip install -r requirements.txt' references a nonexistent requirements.txt, and 'OpenAI API (optional)' contradicts both the Risk Assessment ('No external API calls') and the stdlib-only script.

3 / 5

Workflow Clarity

The Workflow section lists a reasonable sequence with fallback language, but validation checkpoints remain abstract template text rather than concrete per-step verifications (e.g. nothing validates the generated output), and contradictory dependency guidance undermines the sequence.

3 / 5

Progressive Disclosure

The single one-level reference to scripts/main.py is real and clearly signaled, but roughly half the body (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, and the full example output) is inline boilerplate that belongs in separate reference files; no references/ directory exists.

3 / 5

Total

11

/

20

Passed

Description

53%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 clear and domain-specific with a single concrete action, but it is incomplete: it names only one of several capabilities and provides no 'when to use' trigger guidance. Adding an explicit Use-when clause and natural synonyms would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user needs a graphical abstract, visual abstract, or journal summary figure for a paper.'

Enumerate the other concrete capabilities (visual element/icon recommendations, layout blueprints, Midjourney and DALL-E prompt generation) so specificity reaches comprehensive coverage.

Include common user phrasings and synonyms such as 'visual abstract', 'journal figure', and 'paper summary figure' to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names its domain ('graphical abstract', 'paper abstracts') and one concrete action ('Generate graphical abstract layout recommendations'), but omits the other capabilities documented in the body such as element suggestions and AI art prompts, so coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

It contains the natural core phrases 'graphical abstract' and 'paper abstracts', but misses common variations a user would actually say such as 'visual abstract', 'journal figure', or 'figure for my paper'.

3 / 5

Distinctiveness Conflict Risk

The graphical-abstract niche is specific and unlikely to collide with unrelated skills, with only minor overlap risk against generic image-generation skills; it lacks the distinct trigger phrasing needed for a 5.

4 / 5

Total

13

/

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/Data Analysis/graphical-abstract-wizard/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.