CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-illustration-image2

Generate publication-quality academic illustrations through a local Codex app-server bridge that uses Codex native image generation. This is a separate experimental alternative to `paper-illustration`, intended for Claude Code users who want a GPT-image-style renderer without modifying the original skill.

Quality

64%

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 ./skills/paper-illustration-image2/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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's core workflow is exemplary — fully sequenced, gated, and verifiable with concrete commands — but it is wrapped in substantial padding and duplication that costs roughly 40% of its ~400 lines. Style-guide and resolver content belong in reference files rather than the main SKILL.md.

Suggestions

Cut the ~50-line ASCII workflow diagram (the numbered Workflow section already conveys it), the "Phase 3.2 (Arch C)" migration commentary, and the duplicated Key Rules / Repair Path / Model Summary sections, which restate Steps 0–7 nearly verbatim.

Move the CVPR/ICLR/NeurIPS style guide and the multi-layer helper-resolution script into files under references/ (e.g. references/style-guide.md, references/helper-resolution.md) and link to them in one line each.

Replace unfilled placeholders (<cwd>, <best_png>) with concrete example values, and either explain the opening reviewer-routing blockquote in plain language or move it to the referenced reviewer-backends file, since it is unintelligible without external context.

DimensionReasoningScore

Conciseness

Roughly 40% of the body is padding: a ~50-line ASCII workflow diagram that restates the Workflow section, a ~25-line layered helper-resolution script with installation error messages, "Phase 3.2 (Arch C) moved the canonical implementation" changelog commentary, and Key Rules / Repair Path / Model Summary sections that repeat Steps 0–7 nearly verbatim. There is even an untranslated Chinese sentence ("目标:既不保守也不花哨,找到平衡点"). This is noticeably below the midpoint — several unnecessary or duplicated sections — rather than "mostly efficient with some tightening" (anchor 3).

2 / 5

Actionability

Guidance is mostly executable: exact helper commands ("python3 \"$IMAGE2_HELPER\" preflight --workspace <cwd> --json-out figures/ai_generated/preflight.json"), concrete MCP call parameters (prompt, cwd, outputPath, system, timeoutSeconds), specific refinement feedback examples, and a ready LaTeX snippet. It falls short of anchor 5 because commands carry unfilled placeholders (<cwd>, <best_png>), depend on the preceding resolution script, and the opening reviewer-routing blockquote gives direction ("preserve this slot's tier, fresh contexts... deterministic gates") too cryptic to act on without external context.

4 / 5

Workflow Clarity

Steps 0–7 are clearly sequenced with every validation checkpoint explicit: the preflight gate ("If preflight is not `ok=true`, stop and say so clearly"), the acceptance gate ("Score ≥ 9?" with targeted refinement feedback looping back), and final "finalize" + "verify" receipts — plus a rendered pre-flight checklist. This matches the top anchor (explicit validation, feedback loops, checklist); the confusing preamble and the Model Summary's omission of Step 6 are noise, not validation gaps.

5 / 5

Progressive Disclosure

The bundle's scripts/paper_illustration_image2.py exists and is correctly referenced, and section headers are clear, but a ~75-line CVPR/NeurIPS style guide and the helper-resolution plumbing are inlined in SKILL.md when they clearly belong in reference files. The two markdown links point outside the bundle (../shared-references/reviewer-backends.md, ../shared-references/integration-contract.md) and no references/ directory exists in the skill. Structure is present but content that should be separate is inline — anchor 3.

3 / 5

Total

14

/

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 states a clear capability and usefully positions the skill against its sibling, but it omits any "Use when..." trigger guidance and covers only a single action verb, leaving both completeness and trigger-term coverage at the midpoint. Users asking for a "paper figure" or "architecture diagram" would not naturally be captured by the current phrasing.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating paper figures such as architecture diagrams, method illustrations, or conceptual diagrams for academic manuscripts."

Enumerate the concrete capabilities (plan the figure brief, refine layout, verify conference style, iterate via review scoring, emit LaTeX include), so more than one action is named.

Include natural synonyms users actually say — "paper figure", "figure", "diagram", "CVPR/NeurIPS-style illustration" — to improve trigger-term coverage and reduce misfires to the sibling skill.

DimensionReasoningScore

Specificity

The description names its domain ("publication-quality academic illustrations") and one concrete action ("Generate ... illustrations"), but the remainder describes mechanism ("through a local Codex app-server bridge that uses Codex native image generation") and skill lineage rather than additional capabilities. It does not list several specific actions (refinement loop, style checks, LaTeX output), so it matches anchor 3 rather than 4.

3 / 5

Completeness

The "what" is clear (generate publication-quality academic illustrations via the bridge), but there is no "Use when..." clause or equivalent trigger guidance; "intended for Claude Code users who want a GPT-image-style renderer" states an audience, not when to invoke the skill. Per the judging guidelines, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords exist ("publication-quality", "academic illustrations", "GPT-image-style renderer"), but common natural terms users would say are missing — "figure", "paper figure", "diagram", "architecture diagram" — and no synonyms or extensions are covered. This sits at anchor 3 (some relevant keywords, missing variations), below anchor 4's good-but-incomplete coverage.

3 / 5

Distinctiveness Conflict Risk

It explicitly differentiates from the sibling skill ("separate experimental alternative to `paper-illustration`") and gives a selection criterion ("want a GPT-image-style renderer"), making it mostly distinct. It is not 5 because both skills cover the same paper-illustration task domain, so a request like "make a figure for my paper" could plausibly trigger either.

4 / 5

Total

13

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

13

/

16

Passed

Repository

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

Path

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