CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-criteria-generator

Generates scientifically sound inclusion and exclusion criteria for Meta-Analysis based on a given title or keywords. Use when user wants to design eligibility criteria for a systematic review or meta-analysis.

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-criteria-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 three-step workflow is well-sequenced and actionable, but it is buried in a large amount of generic boilerplate that adds no skill-specific value and creates duplicated, self-referential sections. Trimming the template sections and adding the actual LLM prompt templates would substantially improve it.

Suggestions

Cut the generic boilerplate sections (When to Use, Key Features, Dependencies, Implementation Details, Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Deterministic Output Rules, Completion Checklist) — they restate process knowledge Claude already has and duplicate each other.

Merge the duplicate "Validation Shortcut" / "Quick Validation" sections and remove the "Example Usage" section that only says "See `## Usage` above"; keep one Usage section with one validation command.

Include the actual LLM prompt templates for Step 1 and Step 2 (or place them in a reference file) instead of the high-level instruction "Prompt the LLM to act as a Meta-Analysis expert", so the criteria generation is fully reproducible.

DimensionReasoningScore

Conciseness

The body is padded with generic template boilerplate ("Validate the request against the skill boundary", "Keep the output safe, reproducible", "Required Inputs", "Completion Checklist") that restates process knowledge Claude already has. Two duplicate sections ("Validation Shortcut" and "Quick Validation") both just say run `--help`, and "Example Usage" contains only "See `## Usage` above" — several unnecessary padded sections, matching anchor 2.

2 / 5

Actionability

The core workflow is concrete (the extraction command `python scripts/extract_criteria.py --inclusion ... --exclusion ...` is executable, and the `{}`-enclosure and PICO-S format requirements are specific), but the actual LLM prompt templates are absent ("Prompt the LLM to act as a Meta-Analysis expert" is direction, not instruction) and most sections by line count are abstract filler — incomplete concrete guidance, anchor 3.

3 / 5

Workflow Clarity

Steps 1-3 are clearly sequenced with per-step inputs and requirements, including a consistency checkpoint (exclusions "Must NOT contradict Inclusion Criteria") and a pre-run validation shortcut. Minor validation gaps (no check that the `{}` markers were actually produced) keep it below anchor 5.

4 / 5

Progressive Disclosure

Sections are labeled, script references (`scripts/extract_criteria.py`, `scripts/validate_skill.py`) are real one-level-deep paths, and no content clearly belongs in a separate file. Minor organization gaps — duplicated Usage/validation sections and the non-portable hardcoded path `cd "20260316/scientific-skills/..."` — keep it at anchor 4.

4 / 5

Total

13

/

20

Passed

Description

78%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 clearly states what the skill does and when to use it, with mostly natural trigger terms and a well-defined niche. Its main weakness is limited specificity of capabilities beyond the core generate-inclusion/exclusion action.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ("Generates scientifically sound inclusion and exclusion criteria for Meta-Analysis based on a given title or keywords") but coverage is not comprehensive — PICO framework, output format, and other capabilities are absent. Not 4 because it lists fewer than several specific actions; not 2 because the actions are concrete rather than generic.

3 / 5

Completeness

Explicitly answers both: what ("Generates scientifically sound inclusion and exclusion criteria for Meta-Analysis") and when ("Use when user wants to design eligibility criteria for a systematic review or meta-analysis") with a concrete trigger clause, matching the anchor-5 good example pattern.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "inclusion and exclusion criteria", "eligibility criteria", "systematic review", "meta-analysis", "title or keywords" are phrases users would actually say. A few natural variants (e.g. "study selection", "screening criteria") are missing, so it falls short of the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (meta-analysis eligibility criteria) with distinct triggers, but the "systematic review" mention creates minor overlap risk with closely related review-design skills, keeping it below anchor 5.

4 / 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-criteria-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.