CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

scientific-schematics

Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.

Quality

80%

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/scientific-schematics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A highly actionable, well-sequenced body with genuine validation checkpoints, honest failure-mode documentation, and a real (verified) two-file reference structure. Its weakness is redundancy: the same basic command and setup instructions appear multiple times, and a few marketing-style or speculative sections plus prompt guidance duplicated with the references should be consolidated.

Suggestions

Collapse the four repetitions of the basic invocation (Quick Start, How to Use, Command-Line Usage, Getting Started) into one, and merge the duplicated Configuration and Environment Setup sections — this alone would remove ~40 lines.

Move the prompt-engineering guidance (good/bad prompts, key elements) into references/iterative_refinement.md's existing "Prompt Engineering Tips" section and keep only a one-line pointer in SKILL.md.

Delete or shrink the low-information sections: "Smart Iteration Benefits" checkmarks, "Integration with Other Skills", and the generic "Final Integration Check" items Claude already knows.

DimensionReasoningScore

Conciseness

Unique content is dense and valuable (threshold table, failure semantics, API contract, limitations, troubleshooting), but the basic invocation command is repeated four times (Quick Start, How to Use, Command-Line Usage, Getting Started), setup appears twice (Configuration and Environment Setup), and padded sections like "Smart Iteration Benefits" checkmarks and "Integration with Other Skills" add length without information. It is not a 4 because several sections are wholly redundant rather than minor trimmings, and not a 2 because the majority of the body is efficient, skill-specific content rather than explanations of concepts Claude already knows.

3 / 5

Actionability

Commands are copy-paste ready and cover the common cases: `python scripts/generate_schematic.py "..." -o figures/consort.png --doc-type journal` with variants for presentation, poster, custom iterations, and verbose mode, plus concrete setup (`export OPENROUTER_API_KEY=...`, `uv pip install requests`) and diagnosis (`-v` for route, model slug, bounded errors). Specific examples span journal, presentation, and poster use cases, matching the anchor for fully executable guidance.

5 / 5

Workflow Clarity

The generate-review-decision-refine loop is explicitly sequenced ("What happens behind the scenes" steps 1-5) with the threshold check as an explicit validation step, error-recovery guidance ("Check `termination_reason` and each attempt's `error`", read the critique before re-running, avoid blind paid replay), and checklists for the complex verification process. The null-score/review-unavailable path is handled as a clear feedback branch, matching the anchor for clear sequence with explicit validation and feedback loops.

5 / 5

Progressive Disclosure

The two references exist, are one level deep (they cite scripts, not further markdown files), and are well signaled with per-file descriptions ("The generate-review-refine loop, the Python API, every command-line option... four worked examples"; "Publication standards and accessibility guidelines"), and the inline anchor link resolves to a real heading. It is not a 5 because SKILL.md at ~380 lines is more than a lean overview — prompt-engineering guidance (good/bad prompts, key elements) duplicates the "Prompt Engineering Tips" material in references/iterative_refinement.md and would be better consolidated there.

4 / 5

Total

17

/

20

Passed

Description

71%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 concrete, third-person description that clearly states what the skill does across the generate-review-refine pipeline and names its diagram specializations. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness, and missing common synonyms like "schematic" and "figure" in the trigger terms.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating scientific figures, schematics, or diagrams for papers, posters, or presentations" — this would raise completeness from 3 to 4-5.

Include the synonyms "schematic(s)" and "figure(s)" and the output format term "PNG" among the trigger keywords, since users asking for a "paper figure" or "schematic" would not currently match.

Tighten "complex scientific visualizations" to specific triggers (e.g. "publication figures") to reduce overlap with general data-visualization skills.

DimensionReasoningScore

Specificity

"Generates scientific diagram drafts using Nano Banana 2 AI", "Uses Gemini 3.7 Flash for quality review", and "Refines when the review requests improvement, with at most two generations" list multiple concrete actions covering the full pipeline (generate, review, refine with an explicit iteration cap). It is not a 4 because coverage of what the skill does is comprehensive rather than having minor gaps.

5 / 5

Completeness

The "what" is clear (generate, review, refine), but there is no "Use when..." clause or equivalent explicit trigger guidance — "Specialized in neural network architectures, system diagrams, flowcharts..." only weakly implies when to invoke the skill, which caps completeness at 3 per the judging guidelines. It is not a 4 because the specialization list names domains without stating any usage condition.

3 / 5

Trigger Term Quality

Natural terms a researcher would say are present ("flowcharts", "neural network architectures", "system diagrams", "biological pathways", "scientific visualizations"), but common synonyms like "schematic", "figure", or any file extensions (.png) are missing. It is not a 5 because comprehensive coverage including synonyms and extensions is absent, and not a 3 because the term set goes well beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

The scientific-diagram-for-publication niche with named diagram classes is mostly distinct with clear triggers. It is not a 5 because the phrase "complex scientific visualizations" is broad enough to overlap with general charting/plotting and companion visualization skills the body itself acknowledges.

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

K-Dense-AI/scientific-agent-skills

Path

skills/scientific-schematics/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.