CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-analysis-methods-generator

Generates the Methods section for a meta-analysis paper, including search strategy, screening, quality assessment, data extraction, and statistical analysis.

Quality

65%

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-analysis-methods-generator/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 core workflow and prompt templates are genuinely useful and clearly sequenced, but they are buried in a large amount of generic boilerplate meta-sections that add no task-specific value. Several delivery defects (a truncated prompt, mismatched IO contract field, nonexistent CONFIG reference, contradictory validation guidance, broken heading structure) reduce actionability and navigation. Trimming the filler and fixing the prompt/IO inconsistencies would substantially raise the score.

Suggestions

Cut the generic meta-sections (When to Use, Key Features, Dependencies, Implementation Details, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Deterministic Output Rules, Completion Checklist) that restate obvious defaults, keeping only the IO Contract, Workflow, Quality Rules, and Prompts that carry task-specific content.

Fix delivery defects: complete the truncated Inclusion/Exclusion prompt, rename the `title` input to `risk_of_bias_tool` (or fix its description), remove the nonexistent `CONFIG` block reference, and reconcile the contradictory validation guidance ("Validation Shortcut" vs. "Quick Validation").

Fix the heading structure in "Prompts and Templates" so each prompt's Role/Content/Requirements are sub-headings (###) of the prompt rather than sibling top-level sections, and repair the dangling "See `## Workflow` above" reference.

DimensionReasoningScore

Conciseness

Roughly half the body is generic filler that assumes no intelligence, e.g. "Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable", "Keep the output safe, reproducible, and within the documented scope at all times", and a "Completion Checklist" of self-evident confirmations. This matches anchor 2 (several unnecessary explanations or padded sections); it is not 3 because the padding is the bulk of the file rather than incidental, and not 1 because the prompts section does carry real task-specific content.

2 / 5

Actionability

The six prompt templates (Search Strategy, Quality Assessment, Statistical Analysis, etc.) give concrete generation instructions, but delivery is incomplete: the Inclusion/Exclusion prompt trails off ("The user will input a section of inclusion and exclusion criteria. Please:" with nothing actionable after it), the IO contract describes input `title` as "The risk of bias assessment tool to use (e.g., ROB2, NOS, ROBINS-I...)" (a name/description mismatch), and the run plan references an in-file `CONFIG` block that does not exist. This fits anchor 3 (some concrete guidance but incomplete) rather than 4.

3 / 5

Workflow Clarity

The Workflow section gives a clear 6-step sequence with per-step inputs ("Step 1: Search Strategy ... Inputs: `PICOS`, `current_time`, `language`") plus step-1 input validation and Quality Rules, matching anchor 4. It is not 5 because checkpoints are thin (no validation of `language` values, no post-compilation verification) and the body contradicts itself on validation ("Run this minimal command first ... python scripts/validate_skill.py --help" vs. "No local script validation step is required for this skill").

4 / 5

Progressive Disclosure

Everything is inlined in one 255-line SKILL.md with no references directory; inlining the six prompt templates is defensible, but organization is weak — the "Prompts and Templates" subsections use top-level `##` headings that fragment the document, "See `## Workflow` above" is a dangling cross-reference, and three overlapping validation sections (Validation Shortcut, Quick Validation, Validation and Safety Rules) obscure navigation. This matches anchor 3 (some structure but could be better organized).

3 / 5

Total

12

/

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, specific description that clearly states what the skill produces and enumerates the Methods-section components. Its main weakness is the complete absence of a "Use when..." trigger clause, which both caps completeness and slightly weakens trigger-term quality. Adding an explicit usage clause with natural trigger phrases would lift it to the top band.

Suggestions

Append an explicit trigger clause such as: "Use when the user asks to write, draft, or generate the Methods section of a meta-analysis or systematic review paper."

Include common user phrasings and synonyms such as "systematic review", "PRISMA", "methods section", "materials and methods" to improve trigger-term coverage.

Consider mentioning the supported output languages (Chinese/English) or supported risk-of-bias tools (ROB2, NOS, ROBINS-I) to further sharpen distinctiveness.

DimensionReasoningScore

Specificity

"Generates the Methods section for a meta-analysis paper, including search strategy, screening, quality assessment, data extraction, and statistical analysis" names the domain and enumerates five concrete content areas. It fits anchor 4 (several specific items, minor gaps) rather than 5, since the enumeration is content coverage under one verb rather than multiple distinct actions like the anchor-5 example.

4 / 5

Completeness

The description has a clear "what" but contains no "Use when..." clause or equivalent trigger guidance, and the judging guidelines explicitly cap completeness at 3 in that case. It is not a 4 because the "when" is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

Terms like "Methods section", "meta-analysis", "screening", "quality assessment", "data extraction", and "statistical analysis" are natural phrases users would say. A few natural variants are missing ("systematic review", "PRISMA", "write the methods"), matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Methods section for a meta-analysis paper" carves out a fairly distinct niche with specific sub-tasks (search strategy, quality assessment), giving minimal conflict risk with unrelated skills. It is not a 5 because it could overlap with general academic-writing or systematic-review skills, whose requests might also match these triggers.

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/Academic Writing/meta-analysis-methods-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.