CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-literature-deep-research

Deep literature review — PubMed, EuropePMC, bioRxiv preprints, citation networks, evidence synthesis. Disambiguates queries, runs collision-aware searches, grades evidence T1-T4, and produces structured reports. Use for systematic literature review, meta-analysis evidence collection, and detailed answer-with-citations workflows.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced research workflow with real tool signatures, explicit error-recovery loops, and a lean telegraphic style. The main defect is bundle integrity: all five referenced detail files are missing from the bundle, so the progressive-disclosure chain dangles, and section 2.6 inlines verbose per-tool narrative (including live-outage status) that belongs in a reference or maintenance-notes file.

Suggestions

Ship the five referenced files (TOOL_NAMES_REFERENCE.md, REPORT_TEMPLATE.md, FULLTEXT_STRATEGY.md, WORKFLOW.md, EXAMPLES.md) in a references/ directory, or inline their essential content (the 15-section template and the three-tier full-text strategy) — currently the skill defers to files that do not exist.

Move section 2.6's per-tool narratives (EuroPMCAnnot, BGPT, LitVar, the EPMC/EuropePMC naming-collision discussion) into a dedicated reference file, keeping only one-line pointers in SKILL.md.

Relocate time-sensitive operational status (the Europe PMC /references 503 outage, live-verification anecdotes) to a maintenance-notes or tool-status reference so the main workflow stays lean and doesn't go stale in place.

DimensionReasoningScore

Conciseness

The body is overwhelmingly lean and telegraphic (tables, terse tool chains, "Methodology stays internal. Report shows findings, not process.") with no explanation of concepts Claude already knows. However, section 2.6 embeds ~40 lines of narrative prose including time-sensitive operational status ("Live-verified as of this writing: the /references endpoint is down on BOTH implementations ... 33s response, HTTP 500") and live-verification anecdotes, which could be trimmed or relocated — matching the anchor for efficient content with minor instances of over-explanation.

4 / 5

Actionability

The guidance is copy-paste ready: `EuropePMC_search_articles(query="term1 term2 term3", limit=5)`, `PubMed_convert_article_ids {"ids": ["23193287", "10.1093/nar/gks1195"]}`, `PubMed_lookup_article_by_citation {"journal": "Nature", "year": 2015, ...}`, concrete query patterns ("\"[TERM]\" AND ([context]) NOT [collision]"), explicit fallback chains, and a concrete report skeleton. Per the rubric's instruction-skill note, concrete specific guidance with real parameter values earns the top anchor.

5 / 5

Workflow Clarity

The pipeline is explicit (Phase 0 → 1 → 2 → 3) with mode selection, and each phase has validation checkpoints and feedback loops: collision detection ("If >20% off-topic, build negative filter"), the zero-result loop ("PubMed returns 0 for ~30% of valid queries. Always retry with EuropePMC"), broaden/narrow search iteration ("Failed query -> try DIFFERENT TERMS"), and tool-failure retry→fallback chains. This is a research workflow (not destructive/batch), so the cap at 3 does not apply, and the anchor for clear sequence with explicit validation steps and error-recovery loops is met.

5 / 5

Progressive Disclosure

The body is well-sectioned and signals five one-level-deep references in a References section, but none of the referenced files (TOOL_NAMES_REFERENCE.md, REPORT_TEMPLATE.md, FULLTEXT_STRATEGY.md, WORKFLOW.md, EXAMPLES.md) exist in the bundle — no references/, scripts/, or assets/ directories are present. Core deferred content (the 15-section report template, the three-tier full-text strategy) therefore lives nowhere, breaking the disclosure chain, and section 2.6 inlines ~40 lines of per-tool detail that belongs in a reference file. This lands at the 'some structure but could be better organized' anchor rather than 4 (references must resolve to real files) or 2 (structure and signaling are present).

3 / 5

Total

17

/

20

Passed

Description

92%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: concrete, third-person, domain-anchored actions paired with an explicit 'Use for' clause covering systematic review, meta-analysis evidence collection, and citation-backed answers. The only gap is that a few natural user phrasings (e.g. 'find papers', 'search the literature') are absent from the trigger vocabulary.

Suggestions

Add a few natural trigger phrases users would actually say, such as 'find papers on', 'search the literature', or 'survey of [topic]', to broaden trigger-term coverage.

Optionally signal scope boundaries against sibling entity-profiling skills (e.g. 'not for single-gene/drug/disease profiles') to further reduce overlap risk.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Disambiguates queries, runs collision-aware searches, grades evidence T1-T4, and produces structured reports" — plus named sources ("PubMed, EuropePMC, bioRxiv preprints, citation networks, evidence synthesis") covering input, process, and output. This matches the anchor for multiple specific concrete actions with comprehensive coverage; the only lower anchor (4) requires minor coverage gaps, which are not present.

5 / 5

Completeness

Both questions are answered explicitly: the "what" via three concrete verbs plus a structured output, and the "when" via "Use for systematic literature review, meta-analysis evidence collection, and detailed answer-with-citations workflows". This mirrors the anchor example that clearly and explicitly answers both what AND when with concrete trigger phrases; the weak-'when' anchors (3/4) do not apply.

5 / 5

Trigger Term Quality

Natural phrases users would say are present — "literature review", "systematic literature review", "meta-analysis", "answer-with-citations" — but common variations like "find papers", "search the literature", "survey of X", or "sources" are missing. Good keyword coverage with a few natural terms missing matches anchor 4; anchor 5 requires synonym-level coverage of the most common user phrasings.

4 / 5

Distinctiveness Conflict Risk

Biomedical-specific sources (PubMed, EuropePMC, bioRxiv) and the T1-T4 evidence-grading scheme carve a clear niche with distinct, literature-specific triggers — minimal conflict with generic research or entity-profiling skills. Anchor 5 (clear niche, distinct triggers, minimal conflict risk) is the best fit; the description stays in third person and does not over-claim.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-literature-deep-research/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.