CtrlK
BlogDocsLog inGet started
Tessl Logo

scientific-schematics

Automates publication-quality scientific diagrams (e.g., flowcharts, architectures, pathways) when you need journal/poster-ready visuals from a natural-language description.

60

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/scientific-schematics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-organized, mostly lean overview with executable example commands, a clearly sequenced pipeline including a genuine validation/refinement loop, and real one-level-deep reference files. Remaining gaps are modest: duplicated content between Key Features and Implementation Details, a missing dependency-install step, and vaguely specified stopping conditions.

Suggestions

Deduplicate 'Key Features' and 'Implementation Details' — describe the loop, model overrides, and quality threshold once each, stating the actual threshold value instead of 'e.g. 8.5/10'.

Add a dependency-install step to Example Usage (e.g., 'pip install pillow matplotlib requests') so the quick-start is fully copy-paste runnable.

Convert the reference pointers to markdown links with a note on when to consult each file (e.g., 'See [best_practices.md](references/best_practices.md) before finalizing journal figures').

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — no padding explaining matplotlib, LLMs, or what a flowchart is — but 'Key Features' and 'Implementation Details' duplicate content (the generate→review→refine loop and model overrides each described twice, and the 8.5/10 threshold appears twice with 'e.g.' hedges), keeping it below lean-and-trim 5.

4 / 5

Actionability

Four copy-paste-ready commands cover setup and the common cases (doc-type selection, generator/reviewer overrides), but the Dependencies section lists packages without an install command and expected output is never shown, leaving minor gaps versus fully executable coverage.

4 / 5

Workflow Clarity

Pipeline stages are clearly sequenced (Generation → Review → Refinement Loop → Finalization) with an explicit validation feedback loop (reviewer score vs the 8.5 threshold driving re-generation), but the loop's 'internal stopping conditions' are left vague and the threshold is hedged as 'e.g. 8.5/10', preventing a 5.

4 / 5

Progressive Disclosure

Verified against the actual bundle: both referenced files (references/best_practices.md, references/diagram_types.md) exist, are one level deep, and are clearly listed while the body remains a compact overview; it falls short of 5 only because the references are bare code paths rather than linked pointers with when-to-read guidance.

4 / 5

Total

16

/

20

Passed

Description

65%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 clearly communicates a distinct niche (publication-ready scientific diagrams from natural-language prompts) with a reasonable when-clause and decent trigger keywords. Its main weaknesses are the single generic action verb and the second-person 'when you need' phrasing, which costs it a specificity point under the rubric's voice rule.

Suggestions

Rewrite in third person (e.g., '...when journal- or poster-ready visuals are needed from a natural-language description') to remove the second-person voice penalty.

Enumerate the concrete actions the skill performs — e.g., 'Generates, critiques, and iteratively refines diagrams' — to lift specificity beyond a single 'Automates' verb.

Add natural trigger synonyms such as 'schematic', 'figure', or 'publication figures' that users would actually say when requesting this skill.

DimensionReasoningScore

Specificity

The description names the domain ('scientific diagrams') and output types ('flowcharts, architectures, pathways') but offers only one generic action verb ('Automates'), matching the anchor of domain named with minimal actions (base 3); the second-person phrase 'when you need journal/poster-ready visuals' triggers the rubric's 1-point voice penalty, reducing it to 2.

2 / 5

Completeness

Both 'what' ('Automates publication-quality scientific diagrams') and 'when' ('when you need journal/poster-ready visuals from a natural-language description') are present, but the when-clause is need-framed rather than concrete user-trigger phrases like 'Use when the user mentions X', so it falls short of the explicit 5 anchor.

4 / 5

Trigger Term Quality

Good coverage of natural terms users would say — 'flowcharts', 'architectures', 'pathways', 'journal/poster-ready visuals' — but common synonyms like 'schematic', 'figure', or 'publication figures' are missing, placing it just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The publication-quality scientific diagram niche with journal/poster framing is mostly distinct, but generic terms like 'flowcharts' and 'diagrams' carry minor overlap risk with general charting or dataviz skills.

4 / 5

Total

14

/

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