CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

multi-database-literature-collector

Collects candidate biomedical literature across multiple databases, adapts search logic by database, preserves source metadata, and organizes results into a structured, screening-ready candidate pool. Always use this skill when a user wants cross-database literature collection, search strategy construction, candidate paper aggregation, or first-pass evidence organization before deduplication, screening, layered reading, or review planning. Requires real and verifiable literature records only. Every formal literature item must include a real link and DOI when available; never fabricate citations, titles, authors, years, journals, abstracts, PMIDs, or DOIs. If a DOI is unavailable or cannot be verified, state that explicitly rather than inventing one.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured skill body with an explicit seven-step workflow, strong input/output validation gates, and exemplary reference-module organization. Its main weakness is redundancy: the no-fabrication and scope-boundary rules are restated across five or six sections, inflating token cost without adding guidance, and the body lacks a worked search-string or filled-record example.

Suggestions

Consolidate the repeated anti-fabrication and "not final inclusion / not screening" rules into the single Hard Rules section, and drop the duplicated lists in "This skill must never", "What This Skill Should Not Do", and "Quality Standard".

Add one worked example — an adapted PubMed search string and a filled-out sample candidate record showing the required field format — either inline or in the adaptation/normalization reference modules.

Trim the inline A–J output-section descriptions to names plus a pointer, since references/output-section-guidance.md already expands each section.

DimensionReasoningScore

Conciseness

The workflow steps themselves are lean and directive, but the same constraints are restated many times: anti-fabrication rules appear in "This skill must never", the Step 5 "Hard verification rule", "Hard Rules 2–4", "What This Skill Should Not Do", and "Quality Standard", and the "not final inclusion / not screening" boundary is repeated roughly five times. Not 2 because nothing explains concepts Claude already knows and every section is instruction rather than padded prose; not 4 because the cross-section repetition is extensive — the body could be cut nearly in half without losing guidance.

3 / 5

Actionability

Concrete, executable instruction throughout: named databases (PubMed, Google Scholar, Web of Science, Embase...), an exact record field list (title, authors, PMID and/or DOI, evidence status), explicit tier labels (Tier 1/2/3/P), ten mandatory output sections A–J, an exact fallback phrase "DOI not available / not verified", and sample user inputs. Not 5 because the body never shows a worked example of an actual adapted search string or a filled-out example record; not 3 because the guidance is specific and directly executable, not high-level hints or pseudocode.

4 / 5

Workflow Clarity

Seven steps are explicitly ordered ("always run in order"), each mapped to a reference module, with an input-validation gate and a verbatim redirect script for out-of-scope requests, plus a hard verification checkpoint in Step 5 ("If verification is incomplete, say so explicitly instead of filling placeholders") and vague-input handling ("If the user's question is too vague... recommend or trigger prior question clarification"). Not 5 because failure handling is "state it" only — no recovery/retry loop or verification mechanism (e.g., how to actually verify a DOI or link) is specified; not 3 because checkpoints are explicit and present at both the input and output boundaries.

4 / 5

Progressive Disclosure

The body is an overview-plus-workflow-contract that points to nine real one-level-deep reference modules, each introduced with a descriptive purpose line ("Database choice and coverage logic → ...", "Search-term construction and logic expansion → ...") and tied to a specific workflow step; all nine referenced files exist in references/. Not 4 because navigation is genuinely clear, references are well signaled rather than buried, and the detailed per-topic rules are appropriately split out of the overview.

5 / 5

Total

16

/

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.

The description is exemplary: third-person, concrete, comprehensive in capability coverage, with an explicit "use when" clause and clear upstream positioning against adjacent review-planning skills. The only minor gap is the absence of a few plainer trigger synonyms such as "literature search" or "find papers".

DimensionReasoningScore

Specificity

The description lists multiple concrete third-person actions: "Collects candidate biomedical literature across multiple databases, adapts search logic by database, preserves source metadata, and organizes results into a structured, screening-ready candidate pool" — collection, per-database adaptation, metadata preservation, and structured organization are all specific and comprehensive. Not 4 because coverage is comprehensive rather than having minor gaps; not below 5 because no action is vague or generic.

5 / 5

Completeness

Explicitly answers both questions: the "what" is the opening sentence of concrete capabilities, and the "when" is "Always use this skill when a user wants cross-database literature collection, search strategy construction, candidate paper aggregation, or first-pass evidence organization...". Matches the anchor for clearly and explicitly answering both with concrete trigger phrases; not 4 because the "when" clause is already explicit and enumerates specific triggering intents.

5 / 5

Trigger Term Quality

Strong natural trigger phrases: "cross-database literature collection, search strategy construction, candidate paper aggregation, or first-pass evidence organization before deduplication, screening, layered reading, or review planning" — phrases a biomedical researcher would actually say. Not 5 because plainer high-frequency variants like "literature search", "find papers", or "systematic review preparation" are absent, leaving a few common natural terms missing; not 3 because the included terms cover the main use cases with several meaningful synonyms.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (cross-database candidate collection with real-record verification: "Requires real and verifiable literature records only... never fabricate citations") and explicitly positions itself upstream of adjacent skills ("before deduplication, screening, layered reading, or review planning"), minimizing conflict risk with screening/synthesis skills. Not 4 because the boundary against neighboring workflow stages is explicitly drawn rather than merely implied.

5 / 5

Total

19

/

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

awesome-med-research-skills/Evidence Insight/multi-database-literature-collector/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.