CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

literature-filtering

Filter literature by publication year, journal, and predefined screening rules to produce inclusion/exclusion lists; use when conducting preliminary screening or systematic review screening to narrow the literature scope.

Quality

78%

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/Evidence Insight/literature-filtering/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

Highly actionable content with a complete executable example, but it is weighed down by an oversized inline script, duplicated prose explanations, and missing validation checkpoints for a batch screening workflow. Bundle files exist but are weakly integrated.

Suggestions

Move the full Python script to scripts/ (e.g., scripts/screen.py) and keep only a short invocation snippet plus input/output format summary in SKILL.md, removing the Implementation Details prose that duplicates the code.

Add explicit validation checkpoints for the batch operation, e.g., verify included + excluded == total after screening and check screening_log.csv for records with empty reasons before reporting stats.

Tightly integrate the bundle files: reference references/guide.md directly in the workflow (not "if available") and align assets/screening_log_template.csv headers with the screening_log.csv columns the script writes.

DimensionReasoningScore

Conciseness

The body inlines a ~175-line complete script and then an "Implementation Details" section that partially re-explains what the code already shows (e.g., normalization steps duplicate the normalize_journal docstring). Mostly efficient but could be tightened by trimming the duplicated prose; not a 2 because the prose still adds auditable-decision guidance beyond the code.

3 / 5

Actionability

The skill provides a complete, runnable Python script, a minimal input CSV example, and explicitly named outputs (included.csv, excluded.csv, screening_log.csv). It is copy-paste ready and covers the common case end to end.

5 / 5

Workflow Clarity

The sequence (rule setting, normalization, ordered filtering, review, outputs) is clearly listed, but this batch operation has no explicit validation checkpoint (e.g., verify included + excluded equals total, or check the log for missing reasons). The batch-operation cap without validation limits this to 3 despite the clear sequence.

3 / 5

Progressive Disclosure

Section structure exists and both bundle files are real (references/guide.md, assets/screening_log_template.csv), but the full script arguably belongs in scripts/ rather than inlined, the guide.md reference is hedged ("if available"), and the template's headers do not match the log format the code emits. Some structure, but organization and signaling could improve.

3 / 5

Total

14

/

20

Passed

Description

83%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: third-person voice, concrete actions, and an explicit "use when" clause with domain-appropriate trigger phrases. Its only weakness is slightly incomplete action/trigger coverage relative to what the skill actually does.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Filter literature by publication year, journal, and predefined screening rules to produce inclusion/exclusion lists" — with only minor gaps (journal normalization and the screening log are not mentioned). It is not a 5 because coverage of the skill's actions is not comprehensive, and not a 3 because multiple specific actions are named rather than just 1-2.

4 / 5

Completeness

It explicitly answers both: what ("Filter literature by publication year, journal, and predefined screening rules to produce inclusion/exclusion lists") and when ("use when conducting preliminary screening or systematic review screening to narrow the literature scope"). Both halves are concrete and explicit, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "preliminary screening", "systematic review screening", "publication year", "journal", "inclusion/exclusion lists". A few natural terms are missing (e.g., "bibliography", "abstract screening", "screening criteria"), which keeps it below 5 but above 3, where common variations would be absent.

4 / 5

Distinctiveness Conflict Risk

The literature-screening niche is fairly distinct with domain-specific triggers, but it could overlap with a broader systematic-review or search-query skill. Minor overlap risk with closely related skills fits anchor 4 rather than the clear-niche bar of 5.

4 / 5

Total

17

/

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/Evidence Insight/literature-filtering/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.