CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-forest-model-plot

Generate forest plots for meta-analysis of survival data. Input is a CSV file containing study names, HR and 95% confidence intervals, output forest plot PNG and data table CSV. Supports both R and Python scripts.

Quality

71%

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-forest-model-plot/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 core workflow is genuinely executable — real commands, a precise data-format table, and verified bundle scripts — but it is buried in generic boilerplate with duplicated sections, contradictory dependency claims, and documented validation commands ("--help") that the target script does not support. Trimming the template sections and correcting the verification path would move this to a strong skill.

Suggestions

Remove or collapse the generic boilerplate sections (When to Use, Key Features, Output Contract, Deterministic Output Rules, Completion Checklist) and the duplicate Validation Shortcut/Quick Validation pair into one accurate verification step — the body could shrink by half without losing actionable content.

Fix the documented verification commands: forest_survival.py has no --help handling (raw sys.argv parsing), so either document the actual usage error/message or point verification at scripts/validate_skill.py, and replace the fabricated Quick Validation expected output with the script's real output (Survival_forest_{outcome}.png and .csv).

Reconcile factual inconsistencies: Python "3.10+" vs "3.7+ recommended", "plus 1 additional script(s)" (there are 2), and the "See `## Workflow` above" cross-reference that points to a section defined below.

DimensionReasoningScore

Conciseness

Roughly 220 lines of which a large fraction is generic template boilerplate ("When to Use", "Key Features", "Output Contract", "Deterministic Output Rules", "Completion Checklist") that adds no skill-specific information, plus two near-duplicate validation sections and contradictory Python requirements ("3.10+" in Dependencies vs "3.7+ recommended" later). This matches anchor 2 (noticeably verbose, several padded sections) rather than 1, because genuinely useful skill-specific content (data-format table, commands, output spec) is also present.

2 / 5

Actionability

The workflow section gives copy-paste-ready commands with full argument syntax for both R and Python ("Rscript scripts/forest_survival.R \"<csv_path>\" \"<outcome_name>\" \"<output_dir>\""), a concrete data-format table with example values, and dependency install commands — all verified to exist in the bundle. It falls short of 5 because "python scripts/forest_survival.py --help" is documented twice but the script parses raw sys.argv and has no --help handling (it would error treating --help as the CSV path), and the Quick Validation "expected output" ("Result file: meta_forest_model_plot_result.md...") is fabricated — the script produces a usage line and Survival_forest_*.{png,csv} files.

4 / 5

Workflow Clarity

The three-step workflow is clearly sequenced with a real input-validation checkpoint ("Check if necessary columns exist... at least 2 studies, HR and CI are positive numbers") and an explicit feedback loop ("If there are data issues, prompt the user to correct and resubmit"), plus a failure-handling section. Not a 5 because the documented post-implementation verification command (forest_survival.py --help) does not actually run as written, and the duplicated Validation Shortcut / Quick Validation sections create contradictory verification paths.

4 / 5

Progressive Disclosure

The structure is flat and one level deep: SKILL.md points directly to scripts/forest_survival.py, scripts/forest_survival.R, and scripts/validate_skill.py, all of which exist in the bundle; no content that belongs in separate reference files is inlined. Minor gaps: "plus 1 additional script(s)" is inaccurate (there are 2 additional scripts), the cross-reference "See `## Workflow` above" points to a section that appears below it, and redundant sections (two validation sections, two dependency sections) hurt organization, keeping it below anchor 5.

4 / 5

Total

14

/

20

Passed

Description

70%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 precise, distinctive description with concrete input/output artifacts, but it lacks any "Use when..." trigger clause and omits the statistical outputs (pooled HR, heterogeneity) the skill actually delivers. Adding explicit trigger phrases would raise completeness and trigger-term coverage.

Suggestions

Append a trigger clause, e.g. "Use when the user asks for a forest plot, meta-analysis of survival/hazard-ratio data, or pooled effect estimates from study-level HR and confidence intervals".

Spell out "hazard ratio (HR)" and include file-extension terms like ".csv" to broaden natural trigger coverage.

Mention the computed outputs (pooled HR with CI, p-value, I-squared heterogeneity) so the stated capability matches what the scripts deliver.

DimensionReasoningScore

Specificity

"Generate forest plots for meta-analysis of survival data... output forest plot PNG and data table CSV. Supports both R and Python scripts" names the domain, both concrete actions, and the exact input/output artifacts. It falls just short of anchor 5 because it omits capabilities the skill actually performs (pooled effect estimates, heterogeneity statistics), while clearly exceeding anchor 3's 1-2 action coverage.

4 / 5

Completeness

The "what" is clearly and explicitly stated (generate forest plots from survival-data CSV, outputting a PNG and data-table CSV), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the "what" is concrete rather than vague.

3 / 5

Trigger Term Quality

Terms like "forest plots", "meta-analysis", "survival data", "HR", "95% confidence intervals", "CSV", and "PNG" are natural phrases a user would say. A few natural variations are missing — "hazard ratio" spelled out, ".csv", and "systematic review" — which places it at anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

"Forest plots for meta-analysis of survival data" with HR/CI CSV input is a clear niche with distinct triggers (forest plot, meta-analysis, hazard ratio) and minimal overlap with generic plotting or data skills. It is not a 4 because no closely related skill in a typical bundle would plausibly claim this exact combination of triggers.

5 / 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/Data Analysis/meta-forest-model-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.