CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

literature-review

Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/literature-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 skill's core strength is an exemplary seven-phase workflow with genuine validation loops, error recovery, and a quality checklist. It is undermined by token inefficiency — large sections duplicate the bundled reference files and the summary/integration sections pad the document — and by progressive-disclosure failures including a reference to a nonexistent generate_schematic.py script.

Suggestions

Replace the inline "Database-Specific Search Guidance" and "Citation Style Guide" sections with one-line pointers to references/database_strategies.md and references/citation_styles.md, keeping only a single quick-start example inline.

Remove the mandatory schematics section's reference to scripts/generate_schematic.py (which is not bundled) or bundle the script; also delete the redundant closing Summary and tangential Integration sections to cut token load.

Provide a concrete arXiv/Semantic Scholar API example (e.g., an actual curl or Python request) so the "export results in JSON" step is executable rather than aspirational.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with several padded/duplicated sections: "Database-Specific Search Guidance" (~70 lines) and "Citation Style Guide" restate content already in references/database_strategies.md and references/citation_styles.md; the closing "Summary" section restates the whole skill; "Integration with Other Skills" lists tangential skills (pydeseq2, scanpy, brand-guidelines); the schematics section repeats its own instructions ("How to generate figures" vs "How to generate schematics"); and the same script invocations (search_databases.py, verify_citations.py) are shown three times across Phase sections and the Example Workflow. This fits anchor 2 ("noticeably verbose; several unnecessary explanations or padded sections") better than 3, given the volume of duplication of bundled reference content.

2 / 5

Actionability

Mostly executable guidance: concrete gget commands, copy-paste invocations with flags for the three bundled scripts (e.g., `python scripts/verify_citations.py my_literature_review.md`, `--deduplicate --format markdown`), a template cp command, and dependency checks. Minor gaps keep it below anchor 5: `scripts/generate_schematic.py` is invoked but does not exist in the bundle, the arXiv section shows only commented pseudocode with no actual API call, and "Export results in JSON format from each database" gives no concrete mechanism.

4 / 5

Workflow Clarity

The seven-phase workflow is clearly sequenced with explicit validation checkpoints and feedback loops: "Re-run verification until all citations pass", a citation verification script, database-failure handling ("If fewer than 2 databases succeed, pause and inform user"), a dedup-failure fallback ("Manually deduplicate by sorting on title and DOI"), `--check-deps` for PDF tooling, and a final quality checklist. This matches anchor 5 (explicit validation steps, error-recovery loops, checklist).

5 / 5

Progressive Disclosure

Structure exists and the bundled references are real, one level deep, and listed in a Resources section, but substantial content that belongs in those files is inlined: the Database-Specific Search Guidance and Citation Style Guide sections duplicate references/database_strategies.md and references/citation_styles.md, and the body points to a nonexistent scripts/generate_schematic.py. This fits anchor 3 ("content that should be separate is inline") better than 4, given the scale of the inline duplication.

3 / 5

Total

14

/

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, concrete description that names the domain, specific databases, and output formats, with good natural trigger terms. Its main weakness is the missing explicit "Use when..." trigger clause, which caps completeness at 3 and leaves minor overlap risk with adjacent citation-management skills.

Suggestions

Append a trigger clause such as "Use when conducting a systematic or scoping review, writing a literature review section, or synthesizing research on a topic" to satisfy completeness.

Add common user phrasings like "meta-analysis", "scoping review", or "survey of research papers" to broaden natural trigger coverage.

Sharpen distinctiveness by scoping to full multi-database reviews (e.g., "not for single-paper summaries or citation formatting alone").

DimensionReasoningScore

Specificity

The description names several concrete actions with specific tools — "Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.)" and "Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles". It stops short of anchor 5 because core workflow actions (search strategy, screening, synthesis, quality assessment) are absent and "etc." leaves the database list open.

4 / 5

Completeness

The "what" is clear and multi-part (conduct reviews, generate markdown/PDFs, verified citations), but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description. Per the judging guidelines this caps completeness at 3; the description sits squarely on anchor 3, not 4, because the "when" is entirely absent rather than merely weakly implied.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present: "literature reviews", "systematic", "academic databases", and named databases ("PubMed", "arXiv", "bioRxiv", "Semantic Scholar") plus "citations", "citation styles", "markdown", "PDFs". A few common variations are missing (e.g., "meta-analysis", "scoping review", "research papers", "state of the art"), matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The literature-review niche is clear and database names make it mostly distinct, but "verified citations in multiple citation styles" overlaps with citation-management skills (e.g., the body's own reference-style-sync) and the phrase does not distinguish full reviews from single-paper summaries — anchor 4 ("minor overlap risk with closely related skills").

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (612 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/literature-review/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.