CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

journal-cover-prompter

Use when creating journal cover images, generating scientific artwork prompts, or designing graphical abstracts. Creates detailed prompts for AI image generators to produce publication-quality scientific visuals.

Quality

67%

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/Academic Writing/journal-cover-prompter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%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 is heavily padded with template boilerplate and its primary code examples are non-executable: they reference a script file, class, methods, and CLI flags that do not exist in the bundle (only scripts/main.py with JournalCoverPrompter exists). The generic workflow and validation sections are serviceable but not task-specific, and the one real reference is properly linked.

Suggestions

Rewrite Quick Start, Core Capabilities, and CLI Usage to match the actual bundle: scripts/main.py defines JournalCoverPrompter with generate_prompt(research_topic, style, mood, colors, include_text) and CLI flags --topic/--style/--mood/--colors/--no-text; remove references to the nonexistent scripts/cover_prompter.py, CoverPrompter, create_prompt, generate, select_style, get_specs, and the --output flag.

Delete the duplicated description text in 'When to Use' and 'Key Features' and cut the generic governance sections (Implementation Details, Output Requirements, Response Template, Input Validation) that are not specific to journal-cover prompting, roughly halving the body.

Replace the generic five-step Workflow with the concrete task sequence — pick style/mood/colors from the documented options, run 'python scripts/main.py --topic "..."', review the printed main/negative prompt — anchored by the existing py_compile validation step.

DimensionReasoningScore

Conciseness

The frontmatter description is pasted verbatim twice into the body ('Use this skill when the task needs Use when creating journal cover images...' and 'Scope-focused workflow aligned to: Use when creating journal cover images...'), and roughly half the body is generic governance boilerplate ('Output Requirements', 'Response Template', 'Input Validation', 'Audit-Ready Commands' duplicating 'Quick Check'). This matches anchor 2 (noticeably verbose, several padded sections) rather than 1 because it does not explain basic concepts Claude already knows, and not 3 because the padding is pervasive, not incidental.

2 / 5

Actionability

Only the audit commands ('python -m py_compile scripts/main.py', 'python scripts/main.py --help') are executable against the actual bundle; the primary usage guidance is fabricated — 'from scripts.cover_prompter import CoverPrompter', 'prompter.create_prompt(...)', 'prompter.generate(...)', 'prompter.select_style(...)', 'prompter.get_specs(...)', and 'python scripts/cover_prompter.py --topic ... --output prompt.txt' reference a file, class, methods, and a flag that do not exist (scripts/main.py defines JournalCoverPrompter.generate_prompt with --topic/--style/--mood/--colors/--no-text). This matches anchor 2: following the main instructions fails immediately, which is worse than the incomplete-but-runnable guidance of anchor 3.

2 / 5

Workflow Clarity

The 'Workflow' section lists five ordered steps with scope validation ('Validate that the request matches the documented scope and stop early...'), 'Error Handling' documents a fallback path, and 'Quick Check' provides a concrete validation command — so sequence and checkpoints exist, matching anchor 3. Not 4 because the steps are generic governance rather than task-specific, and the entry point is contradictory: three different implementation surfaces are named (scripts/main.py, scripts/cover_prompter.py, CoverPrompter class), leaving the reader unsure which command actually produces a prompt.

3 / 5

Progressive Disclosure

The single reference is real and clearly signaled one level deep ('[references/audit-reference.md](references/audit-reference.md)') and scripts/main.py exists, giving real structure. However the body also navigates to a nonexistent file ('scripts/cover_prompter.py' in Quick Start and CLI Usage), points vaguely upward ('See `## Workflow` above for related details'), and inlines large boilerplate sections that should be trimmed or moved to references. This matches anchor 3 (some structure, could be better organized); not 4 because broken referenced paths exceed 'minor organization gaps'.

3 / 5

Total

10

/

20

Passed

Description

87%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 strong description: it states both what the skill does and when to use it with concrete, natural trigger phrases, and it occupies a distinct niche with minimal conflict risk. The only weakness is a slight over-claim ('creating journal cover images' versus generating prompts for them) that keeps specificity at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'creating journal cover images', 'generating scientific artwork prompts', 'designing graphical abstracts' — plus a clear mechanism ('Creates detailed prompts for AI image generators to produce publication-quality scientific visuals'), matching anchor 4. Not 5 because 'creating journal cover images' mildly over-claims (the skill produces prompts, not images) and coverage of the prompting workflow is not comprehensive.

4 / 5

Completeness

Explicitly answers when ('Use when creating journal cover images, generating scientific artwork prompts, or designing graphical abstracts') and what ('Creates detailed prompts for AI image generators to produce publication-quality scientific visuals') with concrete trigger phrases, exactly matching anchor 5. Not 4 because both halves are explicit and specific rather than one being merely present or weakly implied.

5 / 5

Trigger Term Quality

Natural phrases a researcher would actually say are present: 'journal cover images', 'scientific artwork', 'graphical abstracts', 'AI image generators' — good coverage matching anchor 4. Not 5 because common synonyms and variants are missing (e.g., 'cover art', ' graphical abstract', or specific generator names like Midjourney/DALL-E that users might mention).

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — scientific journal cover and graphical-abstract prompt generation — with triggers ('journal cover images', 'scientific artwork prompts', 'graphical abstracts') unlikely to fire for unrelated skills, matching anchor 5. Not 4 because there is no meaningful overlap risk with generic image-generation or academic-writing skills; the triggers are domain-specific.

5 / 5

Total

18

/

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.

Validation — 14 / 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: 1 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/journal-cover-prompter/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.