CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-baujat-plot

Generate Baujat plots for heterogeneity analysis. Identify studies that contribute most to the overall meta-analysis results and heterogeneity, helping discover potential outlier studies. Input meta-analysis data CSV, output Baujat plot PNG and contribution data CSV.

Quality

62%

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/Data Analysis/meta-baujat-plot/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 domain core is strong — data-format tables, an exact Rscript invocation with parameters, and a concrete output template — but it is buried in generic template filler and undermined by documentation that does not match the actual scripts (no real --help, fabricated expected output, unexplained fallback role and its Binary-only limit). The single-file structure with real bundle scripts is acceptable, though the redundant sections and broken internal references hurt navigation.

Suggestions

Delete the generic boilerplate sections (When to Use, Key Features, Dependencies, Implementation Details, Required Inputs, Output Contract, Validation and Safety Rules, Failure Handling) — they contain no task-specific information and roughly halve the token cost.

Fix the fallback-script documentation: state that it is used when R is unavailable, that it supports Binary data only, and replace the fabricated '--help expected output' with the actual usage string from the script.

Resolve the internal inconsistency: 'See ## Workflow above' points to a section that appears later, and 'Example run plan'/'Quick Validation' duplicate or contradict the Workflow — collapse them into one execution path.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template boilerplate that adds no domain information: "Use this skill when the request matches its documented task boundary", "Dependencies: not explicitly version-pinned in this skill package", "Output discipline: keep results reproducible", plus near-duplicate run plans ("Example run plan" vs "## Workflow") and a time-stamped cd path ("cd 20260316/scientific-skills/..."). That is several padded sections of content Claude already knows — squarely the 2 anchor (noticeably verbose), and not 3 because the padding is extensive rather than occasional.

2 / 5

Actionability

The core path is genuinely executable: "Rscript scripts/baujat_plot.R \"<csv_path>\" \"<type>\" \"<outcome_name>\" \"<output_dir>\"" with parameter descriptions, backed by real bundle scripts and concrete data-format tables. But the documented fallback usage is inaccurate — the script has no argparse/--help, so "python scripts/baujat_plot_fallback.py --help" just prints a one-line usage string and exits 1, while the body's "Expected output format" ("Result file: meta_baujat_plot_result.md...") is fabricated and matches nothing the script produces; the fallback's Binary-only limitation is also undocumented. That mix of concrete commands with fabricated/incomplete details fits 3 (some concrete guidance but incomplete), not 4.

3 / 5

Workflow Clarity

The Workflow section has a real sequence with a validation checkpoint ("Validate data integrity (at least 3 studies are required...)" → exact Rscript command → output template), which exceeds the 2 anchor. But clarity is undercut by two execution paths (R script vs. Python fallback) whose relationship is never explained, an incoherent self-reference ("See `## Workflow` above" in Implementation Details points to a section that appears later), and a "Quick Validation" step that doesn't connect to the workflow. Those gaps — present sequence but missing/incoherent checkpoints — fit 3 rather than 4.

3 / 5

Progressive Disclosure

The bundle structure is legitimate: both referenced script paths ("scripts/baujat_plot_fallback.py", "scripts/baujat_plot.R") exist and are clearly signaled, with no nested references. However, everything lives inline in one ~220-line SKILL.md with no reference files, and the generic boilerplate sections (Dependencies, Output Contract, Validation and Safety Rules, Failure Handling) are content that belongs either trimmed or split out; the broken "See Workflow above" pointer also hinders navigation. That places it at 3 — some structure but could be better organized — rather than 4.

3 / 5

Total

11

/

20

Passed

Description

66%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 solid, concrete description with clear input/output contracts and strong domain-specific triggers, undermined by the complete absence of an explicit "Use when..." clause, which both caps completeness and weakens trigger guidance. Adding trigger phrasing and the supported data types would lift it to the top anchor range.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a Baujat plot, wants to identify outlier or influential studies in a meta-analysis, or mentions heterogeneity sources (I², Q)."

Mention the supported outcome data types (binary, continuous, survival) so users can self-identify whether their CSV qualifies.

Include common synonyms such as "I²", "between-study heterogeneity", and ".csv" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Generate Baujat plots for heterogeneity analysis", "Identify studies that contribute most to the overall meta-analysis results and heterogeneity", "discover potential outlier studies", plus explicit input/output contracts ("Input meta-analysis data CSV, output Baujat plot PNG and contribution data CSV"). It stops short of 5 because it omits supported outcome types (Binary/Continuity/Survival) and the heterogeneity statistics (I², Tau², Q) the skill actually produces.

4 / 5

Completeness

The "what" is clearly and concretely answered, but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description. Per the rubric guideline, a missing 'when' clause caps completeness at 3; it is not 4 because the 'when' is entirely absent rather than merely imprecise, and not 2 because the 'what' is fully explicit.

3 / 5

Trigger Term Quality

Natural keywords are present: "Baujat plots", "heterogeneity", "meta-analysis", "outlier studies", "CSV", "PNG" — terms a researcher would genuinely say. Not 5 because common synonyms and variations are missing, e.g. "I²", "between-study variability", "systematic review", or file extensions like ".csv".

4 / 5

Distinctiveness Conflict Risk

"Baujat plot" is a highly niche, distinct trigger with minimal conflict risk against unrelated skills. It is not 5 because the broader phrasing "Identify studies that contribute most to the overall meta-analysis results and heterogeneity" could also match closely related meta-analysis diagnostics (leave-one-out, forest plot, subgroup analysis skills), creating minor overlap risk.

4 / 5

Total

15

/

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/Data Analysis/meta-baujat-plot/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.