CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-illustration

Generate publication-quality AI illustrations for academic papers using Gemini image generation. Creates architecture diagrams, method illustrations with Codex-supervised iterative refinement loop. Use when user says "生成图表", "画架构图", "AI绘图", "paper illustration", "generate diagram", or needs visual figures for papers.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/skills-codex/paper-illustration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

45%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 defines a genuinely well-sequenced iterative workflow with strong validation gates, but it is bloated by heavy repetition of the same style rules, monolithic inlining of material that belongs in reference files, and scripts with placeholders and gaps that never materialize several promised output artifacts. It reads as an over-stuffed prompt rather than a lean, executable skill.

Suggestions

State the color palette, arrow standards, and 科研风格 rules exactly once — move the full style guide into references/style-guide.md and have the Step 1 template and Step 3/5 checks reference it instead of re-inlining it.

Close the execution gaps: make Step 4 write review_log.json and copy the accepted render to figure_final.png, generate latex_include.tex in Step 8, and drive the iteration counter from a variable instead of the hardcoded `iteration = 1`.

Move the Step 2/3/4 bash scripts into a scripts/ directory (parameterized by prompt file and output path) so the SKILL.md body shrinks to the workflow, rules, and review template.

DimensionReasoningScore

Conciseness

The ~690-line body restates the same style guidance four times (style guide section, Step 1 prompt template, Step 3 verification request, Step 5 checklist) — the identical color palette and arrow rules appear repeatedly — plus heavy ❌/✅/═══ decoration and bilingual redundancy. It avoids explaining basic concepts Claude already knows, so it sits above the severely-verbose anchor but is clearly noticeably verbose.

2 / 5

Actionability

Concrete curl/python scripts exist, but they contain placeholder holes ("INITIAL_PROMPT='[Codex fills in the detailed prompt here]'"), a hardcoded "iteration = 1 # Codex increments this each iteration", fragile '''$VAR''' shell-into-Python quoting that breaks on quotes in the prompt, and no step that actually produces the declared figure_final.png, latex_include.tex, or review_log.json. This matches "some concrete guidance but incomplete; missing key details" rather than the mostly-executable anchor above.

3 / 5

Workflow Clarity

The Step 0–8 sequence is clear with an explicit decision point, a genuine feedback loop (score < 9 → targeted improvement prompt → back to Step 2), a MAX_ITERATIONS guard, and a detailed review checklist — near the top anchor. It falls short of 5 because the declared output artifacts (figure_final.png copy, review_log.json, latex_include.tex) are never produced by any scripted step, a real coherence gap.

4 / 5

Progressive Disclosure

The skill is a monolithic single file with no references/, scripts/, or assets/ bundle; the 200+ line CVPR style guide and the long prompt templates clearly belong in separate reference files. Section headers provide some structure, placing it above the unstructured anchor but squarely at "content that clearly belongs in separate files is inlined".

2 / 5

Total

11

/

20

Passed

Description

83%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 strong: it explicitly states concrete capabilities in third person and pairs them with an explicit, bilingual "Use when" trigger clause. Its main weaknesses are a garbled second sentence and slightly incomplete trigger synonym coverage.

Suggestions

Fix the mangled second sentence, e.g. "Creates architecture diagrams and method illustrations via a Codex-supervised iterative refinement loop."

Add common trigger synonyms such as "architecture diagram", "draw figure", and "论文配图" to reduce missed invocations.

DimensionReasoningScore

Specificity

"Generate publication-quality AI illustrations for academic papers" and "Creates architecture diagrams, method illustrations with Codex-supervised iterative refinement loop" list several concrete, third-person actions with only minor coverage gaps; the second sentence is grammatically muddled, keeping it below a 5.

4 / 5

Completeness

"Generate publication-quality AI illustrations... Creates architecture diagrams, method illustrations" answers what, and "Use when user says \"生成图表\"... or needs visual figures for papers" explicitly answers when with concrete trigger phrases — a direct match to the top anchor.

5 / 5

Trigger Term Quality

"生成图表", "画架构图", "AI绘图", "paper illustration", "generate diagram" are natural phrases users would say in both languages, though common synonyms like "architecture diagram", "论文配图", or "draw figure" are missing.

4 / 5

Distinctiveness Conflict Risk

The AI-image-generation-for-academic-papers niche via Gemini is mostly distinct, but generic triggers like "生成图表"/"generate diagram" could also fire on chart/plotting skills, creating minor overlap risk.

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (691 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex/paper-illustration/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.