CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

graph-interpretation

Use when interpreting scientific graphs and charts, explaining data visualizations for research presentations, writing figure captions for publications, or analyzing trends in clinical research data. Converts complex visual data into clear, accurate explanations for academic papers, clinical reports, and public presentations.

Quality

68%

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/Academic Writing/graph-interpretation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%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 domain content (graph-type table, caption structure, audience templates, pitfall tables) is genuinely useful, but it is buried in template boilerplate and, critically, documents an API that does not exist: every Python and CLI example targets `scripts/graph_interpreter` while the actual bundle ships only a single-method `scripts/main.py`. The reference file is an empty stub, so the promised detailed guidance is not actually available.

Suggestions

Align all code and CLI examples with the actual bundle: either implement the documented `GraphInterpreter` API in `scripts/main.py` (or `scripts/graph_interpreter.py`) or rewrite the Quick Start, Core Capabilities, and CLI Usage sections around the real `GraphInterpretation.describe()` interface — remove every reference to the fabricated module, class, and methods.

Cut the template boilerplate: delete the three verbatim repetitions of the description (When to Use, Key Features, scope line), the generic Implementation Details section with its broken "See ## Workflow above" reference, and the best-practice explanations of things Claude already knows (correlation ≠ causation, report CIs) — this alone would roughly halve the body.

Move the graph-type table, audience explanation templates, Common Patterns, and Quality Checklist into `references/` (populating the currently empty `guidelines.md` or adding focused files), keeping SKILL.md to an overview plus a working quick start with clearly signaled one-level-deep links.

DimensionReasoningScore

Conciseness

The ~400-line body repeats the frontmatter description verbatim three times ("Use this skill when the task needs Use when interpreting...", the "Key Features" restatement, and the scope line), pads with generic template text ("requires explicit assumptions, bounded scope, and a reproducible output format"), and explains concepts Claude already knows (correlation vs. causation, report CIs with point estimates, distinguish statistical from clinical significance). This is noticeably verbose with several padded sections, matching anchor 2 rather than 3 — the padding is not incidental but structural.

2 / 5

Actionability

The core examples are not executable: the Quick Start imports `from scripts.graph_interpreter import GraphInterpreter` and demonstrates ~15 methods (`interpret`, `analyze`, `extract_statistics`, `generate_multi_audience`, `generate_caption`, `critical_appraisal`, `interpret_forest_plot`, `generate_grade_rating`, ...), and the CLI section invokes `python scripts/graph_interpreter.py`, but the only real script is `scripts/main.py` containing a `GraphInterpretation` class with a single `describe()` method — the documented API is fabricated. Only the Quick Check commands (`python -m py_compile scripts/main.py`, `python scripts/main.py`) actually run, leaving minimal genuinely concrete guidance (anchor 2). Not 1 because runnable verification commands and concrete output structures (caption template, statistical reporting example) do exist.

2 / 5

Workflow Clarity

A sequenced 5-step Workflow exists with a fallback path ("If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion"), an Error Handling section, and pre-flight checkpoints ("stop early if the task would require unsupported assumptions"). However, the checkpoints are generic template language disconnected from the actual script's single-method capability, and "Implementation Details" opens with a broken forward reference ("See `## Workflow` above for related details") placed before the Workflow section. Steps are listed but validation is implicit and partly incoherent — anchor 3, not 4.

3 / 5

Progressive Disclosure

The body does point to real bundle paths (`scripts/main.py` exists, `references/` exists), but it simultaneously references a nonexistent `scripts/graph_interpreter.py`, and `references/guidelines.md` is a 5-line heading-only stub while the body claims "Reference material available in `references/` for task-specific guidance" — references exist but do not clearly signal real content. Meanwhile ~300 lines of graph-type tables, audience templates, patterns, and checklists that belong in reference files are inlined in SKILL.md. Some structure, but organization and signaling are incomplete — anchor 3.

3 / 5

Total

10

/

20

Passed

Description

88%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 description: concrete, third-person, with an explicit "Use when..." trigger clause covering multiple natural use cases and a clear statement of what it produces. The only improvements are broader synonym coverage (specific graph-type names) and slightly sharper separation from general visualization/presentation skills.

DimensionReasoningScore

Specificity

The description lists four concrete actions — "interpreting scientific graphs and charts", "explaining data visualizations", "writing figure captions for publications", "analyzing trends in clinical research data" — plus a named conversion ("Converts complex visual data into clear, accurate explanations"), matching the comprehensive-coverage anchor. It is not 4 because coverage spans interpretation, explanation, caption generation, and trend analysis with named deliverable contexts (academic papers, clinical reports, public presentations), leaving no meaningful gaps.

5 / 5

Completeness

It explicitly answers both questions: an explicit trigger clause ("Use when interpreting scientific graphs and charts, ... or analyzing trends in clinical research data") and a clear what-statement in third person ("Converts complex visual data into clear, accurate explanations for academic papers, clinical reports, and public presentations"). This matches the anchor for both what and when with concrete trigger phrases; no gaps justify a 4.

5 / 5

Trigger Term Quality

Natural terms users would say are present — "scientific graphs", "charts", "data visualizations", "figure captions", "clinical research data", "trends" — giving good keyword coverage. It is not 5 because common synonyms users actually utter are missing, e.g. specific graph-type names (Kaplan-Meier, forest plot, survival curve) and phrases like "explain this figure for my paper" or "results section".

4 / 5

Distinctiveness Conflict Risk

The niche — interpreting and explaining existing scientific/clinical figures for academic outputs — is mostly distinct from chart-creation or general dataviz skills, with distinct triggers like "writing figure captions" and "clinical research data". It is not 5 because "explaining data visualizations for research presentations" carries minor overlap risk with presentation-building and data-visualization skills.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/graph-interpretation/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.