CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

imagegenskill

Generate renderable, scientific-style SVG graphics directly from natural-language requirements (no image models). Use when users ask for an image/picture/scientific diagram/visualization poster or explicitly request SVG output for web-embeddable vector graphics.

Quality

76%

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/Other/imagegenskill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 genuinely actionable — a copy-paste-ready example, concrete tuning parameters, and a clear inspect-and-adjust workflow — and reasonably lean apart from a duplicated workflow section and an unresolved Dependencies note. Its most serious defect is bundle integration: none of the five bundled reference files are linked from SKILL.md, and they describe an inconsistent OpenAI image-API toolchain rather than the SVG generator the skill documents.

Suggestions

Add a references section linking the bundled files (e.g., '**CLI reference**: See [references/cli.md](references/cli.md); **Prompt recipes**: See [references/sample-prompts.md](references/sample-prompts.md)') so the bundle is discoverable — or remove the files if they are not part of this skill.

Resolve the bundle mismatch: references/*.md document scripts/image_gen.py and the OpenAI Image API (gpt-image-1.5, OPENAI_API_KEY), which contradicts SKILL.md's 'no image models' SVG pipeline; align or delete them.

Merge the 'Workflow' section into 'Example Usage' (they repeat the same four steps) and replace the Dependencies placeholder note with the actual dependency list after checking svg_gen.py's imports; also state default values/ranges for the tuning parameters.

DimensionReasoningScore

Conciseness

The body mostly respects token budget — no explaining of concepts Claude already knows — but has real tightening opportunities: the 'Workflow' section (steps 1–4) restates the numbered steps already shown in 'Example Usage', and the Dependencies note ('No third-party Python packages are specified in the provided documentation. If scripts/svg_gen.py imports external libraries, add them here...') is authoring meta-commentary that spends tokens without instructing the agent. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'. Not 4: the duplication and the placeholder note are more than 'minor instances'; not 2: there is no concept-teaching padding of the kind in the bad examples.

3 / 5

Actionability

The Example Usage block is a copy-paste-ready bash sequence: heredoc to create input/brief.txt, a sed one-liner to switch STYLE, the run command, and expected output paths. Tuning advice is parameter-specific ('decrease node_count or noise_points'). This matches 'mostly executable guidance; concrete code or commands with minor gaps'. Not 5: the tuning parameters are never given actual values or ranges (the reader must open svg_gen.py to know what node_count defaults to), and configuration requires editing the script rather than passing arguments.

4 / 5

Workflow Clarity

The sequence (write brief → adjust config → run → open output/svggen/latest.svg) is clear and command-anchored, and the 'Tuning / Troubleshooting Parameters' section supplies an inspect-then-adjust feedback loop for the main failure modes (too dense, too empty, style mismatch). This matches 'clear sequence with most checkpoints present; minor validation gaps'. Not 5: there is no explicit verification step (e.g., confirm the SVG parses or renders) and the loop is stated as one-way hints rather than a validate→fix→retry cycle. This is a non-destructive generation skill, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

The body itself is well-sectioned and appropriately sized, but it fails as a hub for the actual bundle: five reference files exist (references/cli.md, codex-network.md, image-api.md, prompting.md, sample-prompts.md) and not one is mentioned or linked anywhere in SKILL.md — the only referenced path is scripts/svg_gen.py. Worse, those reference files document a different tool (an OpenAI Image API CLI, scripts/image_gen.py, gpt-image-1.5), contradicting the skill's stated 'no image models' approach. This fits 'some structure but could be better organized; references present but not clearly signaled'. Not 4: referencing zero of six bundle files is a major navigation gap, not a minor one; not 2: the body is not a monolith and does not inline content that belongs in separate files.

3 / 5

Total

14

/

20

Passed

Description

78%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, well-structured description: third-person voice, concise, with an explicit 'Use when...' clause carrying several natural trigger phrases. Its main gaps are that the 'what' names only one action rather than the skill's fuller capability set, and the broad 'image/picture' triggers create some overlap risk with image-model skills.

Suggestions

Enumerate one or two more concrete capabilities in the 'what' portion (e.g., 'multiple built-in visual styles, emits SVG plus JSON metadata with seed and palette') to lift specificity.

Drop or qualify the generic 'image/picture' triggers (e.g., 'scientific diagram or poster image') to reduce conflict with diffusion/image-model skills, and add the '.svg' extension as a trigger term.

DimensionReasoningScore

Specificity

The description names the domain ('scientific-style SVG graphics') and one concrete action ('Generate ... directly from natural-language requirements'), but stops there. It matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive' — the script's other capabilities (multiple built-in styles, JSON metadata, tunable density parameters) are absent. Not 4: only a single action is listed, not 'several specific actions'; not 2: the action given is concrete and the transformation (NL requirements → SVG, no image models) is specific, not generic.

3 / 5

Completeness

Both questions are answered explicitly: what — 'Generate renderable, scientific-style SVG graphics directly from natural-language requirements (no image models)'; when — 'Use when users ask for an image/picture/scientific diagram/visualization poster or explicitly request SVG output'. This mirrors the anchor 'clearly and explicitly answers both what AND when with concrete trigger phrases'. Not 4: the 'when' is not merely adequate — it enumerates multiple concrete trigger conditions in a proper 'Use when...' clause.

5 / 5

Trigger Term Quality

The 'Use when' clause includes natural phrases users would say: 'image', 'picture', 'scientific diagram', 'visualization poster', 'SVG output', 'web-embeddable vector graphics'. Good coverage, but a few natural terms are missing — no '.svg' file extension, and no synonyms like 'drawing' or 'illustration', so it falls short of the 'comprehensive coverage including synonyms and file extensions' anchor. Not 3: coverage goes well beyond 'some relevant keywords' with multiple natural phrasings; not 5: the missing extensions/synonyms keep it one notch down.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — code-generated scientific SVGs explicitly contrasted with image models ('no image models') — and SVG/vector triggers are distinct. However, the broad triggers 'image/picture' overlap with genuine image-generation skills, so a request like 'generate an image of a cell diagram' could fire the wrong skill. This matches 'mostly distinct; minor overlap risk with closely related skills'. Not 5 because of that broad image/picture overlap; not 3 because the SVG/scientific-diagram focus is far more specific than the 'works with document files' level.

4 / 5

Total

16

/

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/Other/imagegenskill/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.