CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-abstract-screener

Screens research papers based on title/abstract and inclusion criteria, providing a structured Yes/No/Maybe decision. Use when you need to filter literature for meta-analysis or systematic reviews.

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-abstract-screener/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 task-specific core (the two-phase screening workflow with a JSON output contract and script validation) is clear and well sequenced, but it is embedded in ~80 lines of generic template filler. More seriously, the screening logic and schema are delegated to references/screening_prompts.md and scripts/screen_paper.py, neither of which exists in the bundle, leaving the skill's central details unresolvable.

Suggestions

Ship or fix the missing bundle files: references/screening_prompts.md (screening logic + JSON schema) and scripts/screen_paper.py are cited as the primary implementation surface but do not exist in references/ or scripts/, so the skill's core logic is inaccessible.

Delete the generic template sections (When to Use, Key Features, Implementation Details, Required Inputs, Output Contract, Validation and Safety Rules, Failure Handling, Input Validation, Quick Validation) — they restate the description or repeat boilerplate that Claude already knows; keep the Workflow and Resources sections.

Remove the leaked generation path in Example Usage ("cd 20260316/scientific-skills/Data Analytics/meta-abstract-screener") and replace it with a path relative to the skill directory; also include an example screening input/output pair inline so the skill is actionable even before opening the references.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded sections: "Key Features" restates the frontmatter description verbatim, "When to Use" offers only circular filler ("Use this skill when the request matches its documented task boundary"), and "Implementation Details", "Required Inputs", "Output Contract", "Validation and Safety Rules", "Failure Handling", and "Input Validation" are generic template boilerplate that adds nothing specific to abstract screening. It avoids level 1 because it does not explain concepts Claude already knows (no PDF-style tutorials), but roughly half the body is unnecessary template text that could be cut.

2 / 5

Actionability

There are concrete commands ("python scripts/screen_paper.py '<json_output>'", "python scripts/screen_paper.py --help", py_compile check) and a concrete output contract ("The output must contain strictly `Result` and `Reason`"), but the actual decision logic and JSON schema are delegated to "references/screening_prompts.md" (Steps 1 and 2), which does not exist in the bundle — the referenced files are missing, so the key executable details are inaccessible. This is "some concrete guidance but incomplete; missing key details" rather than mostly executable guidance.

3 / 5

Workflow Clarity

The core Workflow is a clearly sequenced three-phase process (Analysis → Formatting → Optional Validation via the script), with an additional Quick Validation path and a Failure Handling section covering error recovery in generic terms. It falls short of level 5 because validation is only optional and the failure-recovery guidance is boilerplate rather than concrete feedback loops tied to the screening steps; it is above level 3 because checkpoints are explicitly present, not merely implied.

4 / 5

Progressive Disclosure

Structure is decent — a Resources section clearly signals one-level-deep references ("references/screening_prompts.md", "scripts/screen_paper.py") — but the bundle contains no references/ or scripts/ directories, so every detailed reference points to a nonexistent file and the promised deeper content is unavailable. Combined with substantial inline generic boilerplate that should be trimmed, this sits between "references present but not clearly signaled" (they are signaled, but broken) and the well-placed level-4 anchor.

3 / 5

Total

12

/

20

Passed

Description

82%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 (screen papers by title/abstract against inclusion criteria into a Yes/No/Maybe decision) and when to use it, in third person, with natural trigger terms and low conflict risk. The only weakness is modest action coverage — one composite screening action rather than several enumerated capabilities.

DimensionReasoningScore

Specificity

The description names the domain ("research papers", "title/abstract", "inclusion criteria") and one concrete composite action ("Screens research papers... providing a structured Yes/No/Maybe decision"), i.e. 1-2 concrete actions rather than the several specific actions of the level-4 anchor (cf. "Extracts text from PDF files, fills forms, converts pages to images"). It is above level 2 because the actions are specific, not generic, but coverage is not comprehensive (exclusion criteria and the systematic-review exclusion behavior are absent).

3 / 5

Completeness

Both halves are explicit: the "what" ("Screens research papers based on title/abstract and inclusion criteria, providing a structured Yes/No/Maybe decision") and the "when" with concrete trigger phrases ("Use when you need to filter literature for meta-analysis or systematic reviews"), matching the level-5 anchor pattern. Level 4 would require the when-clause to be less explicit or specific, which is not the case here.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "research papers", "title/abstract", "inclusion criteria", "filter literature", "meta-analysis", "systematic reviews" — phrases a user doing literature screening would plausibly say. It falls short of level 5 ("comprehensive coverage... including synonyms") because common variations like "screen abstracts/papers", "literature search", or "citation screening" are missing.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — title/abstract-level literature screening for meta-analysis and systematic reviews — with distinct triggers unlikely to fire for unrelated skills. Minor theoretical overlap with sibling research skills (e.g. full-text screening or data extraction) is not indicated by the text, fitting the "clear niche with distinct triggers; minimal conflict risk" anchor.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 11 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/meta-abstract-screener/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.