CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-forest-binary-plot

Generate meta-analysis forest plots for binary classification data. Input is a CSV file containing study names, event counts and sample sizes for experimental and control groups. Output includes forest plot PNG and data table CSV.

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

Quality

Content

56%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 skill's core workflow is genuinely strong: a precise data contract, executable R-first/Python-fallback commands, input validation with a resubmit loop, and a deterministic output template. However, the body is heavily padded with generic scaffold boilerplate, contains a broken cross-reference and contradictory duplicate dependency lists, and buries the real workflow under redundant policy sections, hurting token efficiency and organization.

Suggestions

Delete or collapse the generic template sections ('When to Use', 'Key Features', 'Implementation Details', 'Output Contract', 'Deterministic Output Rules', 'Completion Checklist') that restate nothing specific to forest plots; keep only the Data Format, Workflow, Dependencies, and When Not to Use sections.

Resolve the two contradictory R dependency lists ('ggplot2, meta, gridExtra' vs 'meta, metafor, grid, stringr') into one accurate list, and fix the broken reference 'See ## Workflow above'.

Remove the environment-specific dated path ('cd "20260316/scientific-skills/..."') and point the 'Quick Validation' section at the actual task scripts (forest_binary.R / forest_binary.py) instead of the extract_criteria.py scaffold.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template filler ('Use this skill when the request matches its documented task boundary', 'Prefer this skill for repeatable, checklist-driven execution'), with a broken self-reference ('See ## Workflow above' when Workflow is below), a hardcoded dated path ('cd "20260316/scientific-skills/..."'), and two contradictory R dependency lists ('ggplot2, meta, gridExtra' vs 'meta, metafor, grid, stringr') — noticeably verbose with several padded sections (anchor 2), though the core Data Format/Workflow sections are efficient, keeping it above anchor 1.

2 / 5

Actionability

Provides copy-paste-ready commands with per-parameter documentation ('Rscript scripts/forest_binary.R "<csv_path>" "<outcome_name>" "<output_dir>"' plus a flagged Python fallback), an exact column table with examples, and a precise output template — mostly executable with minor gaps: no end-to-end example with real values, and the 'validation shortcut' points at the scaffolding script extract_criteria.py rather than the actual task scripts.

4 / 5

Workflow Clarity

A clear 3-step sequence with explicit validation in Step 1 (required columns, 'at least 2 studies, non-negative integer values', with a correct-and-resubmit loop) and an error-recovery fallback in Step 2 ('If R script execution fails, automatically fall back to Python script'). Not anchor 5 because there is no guidance for when both scripts fail, and the scattered duplicate validation sections muddy the primary flow.

4 / 5

Progressive Disclosure

All referenced scripts exist one level deep in scripts/ with no nested references, but everything is inlined in a single ~155-line file whose generic policy sections ('Output Contract', 'Deterministic Output Rules', 'Completion Checklist', duplicated validation sections) are redundant and could be consolidated or dropped; structure exists but organization is inconsistent (anchor 3).

3 / 5

Total

13

/

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.

The description communicates a specific, well-bounded task with concrete input and output contracts, and its niche topic keeps conflict risk low. Its main weakness is the total absence of a 'Use when...' trigger clause, which caps completeness and weakens discoverability against natural user phrasing.

Suggestions

Append an explicit trigger clause, e.g., 'Use when the user mentions forest plots, meta-analysis of binary/dichotomous outcomes, or pooled odds ratios from event-count data.'

Add natural synonyms and variations users actually say, such as 'dichotomous outcomes', 'odds ratio', 'risk ratio', and the '.csv' file extension.

Replace 'binary classification data' with the domain-standard term 'binary (dichotomous) outcome data' so the phrase matches how meta-analysis users describe their data.

DimensionReasoningScore

Specificity

Concrete action ('Generate meta-analysis forest plots') with a precisely specified input schema ('study names, event counts and sample sizes for experimental and control groups') and concrete outputs ('forest plot PNG and data table CSV'), but only a single action verb, matching anchor 4 rather than the multi-action comprehensiveness of anchor 5.

4 / 5

Completeness

The 'what' is clear (task, inputs, outputs), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; anchor 3 ('clear what, when missing') fits exactly.

3 / 5

Trigger Term Quality

Natural terms users would say are present ('meta-analysis', 'forest plots', 'CSV', 'event counts', 'experimental and control groups'), but common synonyms and variations ('dichotomous outcomes', 'odds ratio', '.csv' extension) are missing, fitting anchor 4 rather than the comprehensive coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Meta-analysis forest plots for binary classification data' is a clear niche with minimal conflict risk beyond a hypothetical sibling skill (e.g., continuous-outcome forest plots) or generic charting skills, matching anchor 4; it lacks the explicit trigger phrasing that would justify anchor 5.

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