CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-results-funnel-plot-generator

Generates a Meta-analysis results section description for funnel plots, including statistical tables (Egger's, Begg's, Trim & Fill) and figure legends. Supports English and Chinese outputs. Use when user provides a funnel plot image and statistics and wants a formatted report.

Quality

74%

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

Quality

Content

46%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 and quality rules are sound and the reference/script split is appropriate, but the body is undermined by generic boilerplate sections, circular cross-references, a malformed assembly step with a duplicated figure-reference option, and a complete failure to document the script's actual command-line interface. An informed reader can reconstruct the process but would be unable to run the assembly step correctly from the document alone.

Suggestions

Delete the templated boilerplate sections (Key Features, Implementation Details, and the generic bullets under When to Use and Example Usage) that restate the description or point circularly to other sections; keep only the Usage inputs, Workflow, Quality Rules, and Error Handling content.

Document main.py's real invocation: it takes --desc, --egger, --begg, --trim, and --lang flags (there is no in-file CONFIG block), so show one complete example command with placeholder values instead of the generic run plan.

Fix the malformed workflow bullet — the figure reference is written as "(Figure 3)" or "(Figure 3)" (identical options, likely meant to differ for English/Chinese) and the bullet's indentation is broken — and replace the hardcoded dated path "20260316/scientific-skills/Academic Writing/..." with a repo-relative path.

DimensionReasoningScore

Conciseness

Roughly a third of the body is templated boilerplate: "Key Features" restates the frontmatter description verbatim, "Implementation Details" offers generic filler ("Execution model: validate the request...", "Output discipline..."), "When to Use" contains padded generic bullets ("when a academic writing task needs a packaged method instead of ad-hoc freeform output"), and "Example Usage" opens with the circular pointer "See `## Usage` above for related details". This is noticeably verbose with several padded sections, matching the score-2 anchor; it exceeds the 'some unnecessary explanation' of score 3.

2 / 5

Actionability

Concrete elements exist (workflow steps naming the three tables, `python -m py_compile scripts/main.py`, `python scripts/main.py --help`, a link to references/prompts.md which is real), but key details are missing: the body never documents main.py's actual CLI flags (--desc, --egger, --begger, --trim, --lang) and instead says to "Edit the in-file CONFIG block or documented parameters if the script uses fixed settings" — inaccurate for an argparse-based script — plus the assembly step is garbled ("Insert figure reference \"(Figure 3)\" or \"(Figure 3)\" into the description" offers two identical options with broken bullet formatting) and the example path hardcodes a dated repo path ("20260316/scientific-skills/..."). Some concrete guidance but incomplete with missing key details — score 3, not 4, because the core operation (running the script with real inputs) is never demonstrated.

3 / 5

Workflow Clarity

The sequence is present (inputs → LLM description → LLM tables → assemble via scripts/main.py → quality rules on language/structure/formatting), and error handling plus input validation sections exist. However, checkpoints are implicit rather than explicit — there is no step verifying the assembled output against the Quality Rules (table format, section order, language match), and the workflow's step 3 is malformed, creating real ambiguity about figure-label insertion. Steps listed with validation gaps fits score 3; score 4's 'most checkpoints present' is not met since output verification is entirely absent.

3 / 5

Progressive Disclosure

Structure is good for a small bundle: references/prompts.md (verified to exist) is linked once with a clear purpose statement ("See prompts.md for the LLM prompts used in this workflow"), one level deep, and scripts/main.py is the single implementation surface. Score 4 rather than 5 because navigation is diluted by redundant circular sections ("Example Usage" → "See ## Usage above"; "Implementation Details" → "See ## Workflow above") that add lookup friction rather than clear signposted navigation.

4 / 5

Total

12

/

20

Passed

Description

92%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: it names concrete deliverables, an explicit use-when clause with the exact required inputs, and a distinct niche, all in third person. The only meaningful gap is the absence of the natural synonym "publication bias" (and related phrasing like heterogeneity assessment), which keeps trigger term coverage just short of comprehensive.

DimensionReasoningScore

Specificity

Multiple concrete actions are named: "Generates a Meta-analysis results section description", "statistical tables (Egger's, Begg's, Trim & Fill)", "figure legends", and "Supports English and Chinese outputs" — comprehensive coverage of the skill's capabilities with no vague filler. Third person voice is used correctly.

5 / 5

Completeness

Both questions answered explicitly: the "what" lists the concrete deliverables (results section description, statistical tables, figure legends, bilingual output) and the "when" is a concrete trigger clause — "Use when user provides a funnel plot image and statistics and wants a formatted report" — naming the exact inputs and intent. Fits the score-5 anchor; the score-4 anchor ('when' could be more explicit) undersells the specificity of the input list.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("funnel plot", "meta-analysis", "Egger's", "Begg's", "Trim & Fill", "statistical tables", "figure legends"), but misses common synonyms a user would naturally say, most notably "publication bias" — the primary term associated with funnel plot analysis. Not a 5 because the anchor requires synonym-level coverage; not a 3 because most natural terms for this domain are present.

4 / 5

Distinctiveness Conflict Risk

A clear niche (meta-analysis funnel plot reporting with named statistical tests) with distinct triggers; virtually no other skill would trigger on "funnel plot image" plus Egger's/Begg's statistics. Minimal conflict risk.

5 / 5

Total

19

/

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/Academic Writing/meta-results-funnel-plot-generator/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.