CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pubmed-search-specialist

Build complex Boolean query strings for precise PubMed/MEDLINE literature retrieval. Trigger when user needs MeSH term mapping, Boolean query construction, advanced PubMed filters, citation searching, systematic review search strategy, or clinical query optimization.

Quality

76%

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/pubmed-search-specialist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 domain-specific core (field tags, clinical query filters, the worked aspirin/stroke example, quality checklist) is genuinely strong and executable, but it is buried in generic template boilerplate: a triple-repeated description, circular self-references, two competing workflow sections, and security/lifecycle/response-template padding. Trimming the boilerplate and moving reference-grade tables into the existing references files would substantially improve the skill.

Suggestions

Remove the template filler: the description restated in 'When to Use' and 'Key Features', circular 'See ## X above' sections, and the generic Risk Assessment / Security Checklist / Lifecycle Status / Response Template sections that add no PubMed-specific guidance.

Merge the two workflow sections into one, keeping the PICO-to-final-query workflow and converting the MeSH verification warning into a concrete checkpoint (e.g., verify each term at the MeSH Browser URL before finalizing).

Move the field tags reference table, Boolean operator explanations, and clinical query filter strings into references/ (extending boolean-examples.md) so SKILL.md stays a lean overview with clearly signaled one-level-deep references.

DimensionReasoningScore

Conciseness

The frontmatter description is repeated verbatim in "When to Use" and twice more in "Key Features"; sections like "Dependencies" and "Implementation Details" are circular filler ("See `## Prerequisites` above", "See `## Workflow` above"); and roughly a hundred lines of generic template governance (Risk Assessment, Security Checklist, Lifecycle Status, Response Template) add no PubMed-specific value. This is structural padding, not the incidental over-explanation of anchor 3.

2 / 5

Actionability

The body provides copy-paste-ready clinical query filter strings, field tag and MeSH feature tables, a complete worked example query, verified commands (`python -m py_compile scripts/main.py`, `python scripts/main.py --help`), and a parameters table. Not a 5 because the example usage `cd "20260318/scientific-skills/Evidence Insight/pubmed-search-specialist"` is a non-portable artifact path and "Estimated result count guidance" lacks any concrete method for producing counts.

4 / 5

Workflow Clarity

The domain workflow (PICO extraction → MeSH mapping → Boolean construction → filter application → output) is sequenced and backed by a pre-finalize checklist, but a second, competing generic "Workflow" section duplicates it with abstract steps, and validation checkpoints ("MeSH terms verified against current MeSH database") are stated as warnings without concrete verification steps. Sequence is present but checkpoints are implicit, fitting anchor 3 rather than 4.

3 / 5

Progressive Disclosure

The two references (`references/mesh-structure.md`, `references/boolean-examples.md`) are real files, one level deep, and clearly signaled. However, a 357-line body inlines full clinical query filter strings, a complete field tag reference table, and Boolean operator explanations — reference-grade content that partially duplicates `references/boolean-examples.md` and should live in the reference files.

3 / 5

Total

12

/

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: third-person, concrete, with an explicit trigger clause enumerating specific capabilities. The only gap is a few natural synonym phrases (e.g., "literature search") that would broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the core action ("Build complex Boolean query strings for precise PubMed/MEDLINE literature retrieval") and the trigger list enumerates six concrete capabilities ("MeSH term mapping, Boolean query construction, advanced PubMed filters, citation searching, systematic review search strategy, or clinical query optimization"), giving comprehensive coverage of the skill's actions rather than 1-2 generic ones.

5 / 5

Completeness

It explicitly answers both what ("Build complex Boolean query strings for precise PubMed/MEDLINE literature retrieval") and when ("Trigger when user needs MeSH term mapping, Boolean query construction...") with concrete trigger phrases, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Natural domain keywords users would actually say are present — "PubMed", "MEDLINE", "MeSH term", "Boolean query", "systematic review search strategy", "clinical query". Not a 5 because common variations such as a standalone "literature search", "search strategy", or "database search" phrase are missing.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (PubMed/MEDLINE Boolean query construction) with domain-specific triggers like MeSH mapping and clinical query optimization, making it unlikely to fire for unrelated skills.

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

scientific-skills/Evidence Insight/pubmed-search-specialist/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.