CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-funnel-plot

Generate Meta-analysis funnel plots and perform publication bias testing. Takes CSV file with Meta-analysis data as input, outputs funnel plot PNG, Egger test and Begg test results.

Quality

66%

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

Quality

Content

48%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 contains a solid executable core — precise data-format tables, an exact Rscript invocation, and a well-defined output template — but wraps it in substantial generic template boilerplate and contradictory guidance about the Python and R entry points, including a fabricated validation section. Tightening the document to the workflow, data requirements, invocation, and failure modes would substantially improve it.

Suggestions

Delete or drastically trim the generic boilerplate sections ("When to Use", "Key Features", "Implementation Details", "Required Inputs", "Output Contract", "Validation and Safety Rules", "Failure Handling", "Quick Validation") and keep only funnel-plot-specific guidance.

Resolve the entry-point contradiction: commit to either the R or the Python implementation in the Workflow, and remove the fabricated "Quick Validation" expected output that `funnel_plot.py --help` does not actually produce.

Move invocation details and package installation into (or adjacent to) the Workflow section so a reader follows one coherent path from input validation to output, and fix the "See `## Workflow` above" reference and the dated `cd "20260316/..."` example path.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: roughly half of it ("When to Use", "Key Features", "Implementation Details", "Required Inputs", "Output Contract", "Validation and Safety Rules", "Failure Handling", "Quick Validation") is generic template boilerplate unrelated to funnel plots, and "Implementation Details" opens with a broken self-reference ("See `## Workflow` above" when Workflow appears later). The genuinely useful content (data format tables, Rscript invocation, output template, package dependencies) is buried among padded sections.

2 / 5

Actionability

The core path is concrete and executable — the exact Rscript command with per-parameter descriptions, column-name tables per data type, and an R package install command — but it is undermined by incoherent guidance: "Example Usage" and "Quick Validation" direct to `python scripts/funnel_plot.py --help` with a fabricated expected output (the script takes positional args and prints a usage line, not the documented result-file summary), while the actual workflow requires `Rscript scripts/funnel_plot.R`; the "Output Contract" also invents a `meta_funnel_plot_result.md` deliverable that contradicts the documented PNG/CSV outputs. These are more than minor gaps, so it cannot reach the 'mostly executable' anchor of 4.

3 / 5

Workflow Clarity

The Workflow section gives a clear 3-step sequence (validate input → execute script → report output) with an explicit validation checkpoint (required columns per data type, minimum 3 studies) and a fully specified output template. It falls short of 5 because there is no in-workflow error-recovery loop (failure handling is only covered generically in a separate section) and the surrounding sections introduce Python-vs-R entry-point confusion.

4 / 5

Progressive Disclosure

The body is sectioned with headers and the referenced bundle files (`scripts/funnel_plot.py`, `scripts/funnel_plot.R`) are real, but everything lives inline in a ~200-line SKILL.md with no reference files. The generic boilerplate sections inflate the main file without adding navigational value, and the confusing placement of content (workflow-relevant details in "Implementation Details" and "Example Usage" rather than the Workflow section) means organization could be better.

3 / 5

Total

12

/

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 strong, concrete, third-person description that clearly communicates what the skill does with good domain-specific trigger terms and minimal conflict risk. Its main weakness is the absence of any 'Use when...' trigger clause, which caps completeness and slightly limits discoverability.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks for a funnel plot, publication bias testing, or Egger/Begg tests on meta-analysis data."

Mention trim-and-fill analysis (documented in the body) and any other supported outputs to make capability coverage comprehensive.

Include a common synonym such as "funnel plot asymmetry" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Generate Meta-analysis funnel plots", "perform publication bias testing", "Egger test and Begg test results" — plus explicit input (CSV) and output (PNG) formats, matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because capabilities documented in the body (e.g., trim-and-fill analysis) are omitted, and exceeds 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

The 'what' is clearly and concretely stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance — the rubric guidelines cap completeness at 3 in that case. The input sentence ("Takes CSV file with Meta-analysis data as input") only weakly implies when to use the skill.

3 / 5

Trigger Term Quality

Terms users would naturally say are present: "Meta-analysis", "funnel plot", "publication bias", "Egger test", "Begg test", "CSV". A few natural variations are missing (e.g., "funnel plot asymmetry", "publication bias assessment"), matching the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (funnel plots with Egger and Begg publication bias tests on meta-analysis CSV data) with distinct trigger phrases; a user needing this would use these exact terms, so conflict with other skills is minimal.

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