CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reference-search

Multi-database literature search and search-strategy design that outputs structured, reproducible result lists; use when you need reference retrieval, systematic searching, review topic selection, or to construct a traceable search strategy.

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

Quality

Content

60%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 substantive content is solid — executable commands, real configuration, concrete endpoints, and a clear recommended workflow — but it is undermined by a fully duplicated boilerplate section set that roughly doubles the token cost, and by a dangling reference to a nonexistent test file. The bundle structure itself is genuine and well organized.

Suggestions

Delete the duplicated boilerplate block at the top (the unnumbered 'When to Use / Key Features / Dependencies / Example Usage / Implementation Details' sections, lines 11–54): it restates the frontmatter description verbatim and duplicates the numbered sections 1–5, nearly halving the body's token cost.

Remove or fix the dangling reference to 'tests/test_pubmed_search.py' — the file does not exist in the skill bundle — and align the two inconsistent example paths ('20260316/scientific-skills/...' vs 'skills/reference-search') to one correct location.

Add an explicit validation checkpoint to the search workflow (conciseness's duplication is the top fix, but workflow clarity is close behind): e.g., after export, verify the number of records written matches the API-reported count and retry with backoff on timeout, since the 20-second timeout and rate limit are already documented.

DimensionReasoningScore

Conciseness

The body carries an entire duplicated boilerplate block — an unnumbered 'When to Use / Key Features / Dependencies / Example Usage / Implementation Details' set (lines 11–54) followed by numbered sections 1–5 covering the same ground — including filler like 'Scope-focused workflow aligned to: <full description restated verbatim>' and 'Use this skill when a evidence insight task needs a packaged method instead of ad-hoc freeform output.' This is noticeably verbose with several padded sections (anchor 2), though it never pedagogically explains concepts Claude already knows (which would be anchor 1).

2 / 5

Actionability

Concrete, mostly executable guidance throughout: run commands (`python scripts/pubmed_search.py`), a real `CONFIG` dict with per-key comments, an example JSON output, and exact E-utilities endpoints. Minor gaps keep it at anchor 4 rather than 5: no documented CLI arguments, and the two usage examples use inconsistent `cd` paths ('20260316/scientific-skills/...' vs 'skills/reference-search').

4 / 5

Workflow Clarity

The 'Search workflow (recommended)' is a clearly sequenced 4-step process with pre-flight checkpoints (confirm research question, set inclusion/exclusion criteria) and a post-run review step. Not anchor 5 because there is no explicit validate/fix/retry checkpoint (e.g., reconciling returned record counts against the reported total, or retry guidance on API timeout); not anchor 3 since the sequence and most checkpoints are present and the operation is non-destructive.

4 / 5

Progressive Disclosure

The bundle is real and well listed: 'references/guide.md', 'references/evaluation-checklist.md', 'assets/search_log_template.csv', 'assets/search_results_template.csv', and 'scripts/pubmed_search.py' all exist and are enumerated in a dedicated 'Included assets and references (in-repo)' section. Minor gaps fit anchor 4 rather than 5: the reference to 'tests/test_pubmed_search.py' is dangling (no tests/ directory exists in the bundle), and references are flat-listed rather than contextually signaled from the workflow steps.

4 / 5

Total

14

/

20

Passed

Description

88%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 capabilities, an explicit trigger clause, and a well-defined niche. Its only notable gap is missing the most natural user-facing trigger terms — 'PubMed' and everyday synonyms like 'find papers' or 'articles'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'literature search', 'search-strategy design', 'outputs structured, reproducible result lists', 'reference retrieval', 'systematic searching', 'review topic selection', 'construct a traceable search strategy' — with comprehensive coverage, matching the top anchor. It is not a 4 because the gaps are not minor; the action list covers the skill's full scope.

5 / 5

Completeness

It explicitly answers both questions: the 'what' ('Multi-database literature search and search-strategy design that outputs structured, reproducible result lists') and an explicit 'use when you need reference retrieval, systematic searching, review topic selection, or to construct a traceable search strategy' with concrete trigger phrases. This matches the anchor-5 example structure; the 'when' clause is explicit, not weaker as anchor 4 requires.

5 / 5

Trigger Term Quality

Natural phrases like 'reference retrieval', 'systematic searching', and 'literature search' are present, but the most natural trigger users would say — 'PubMed' — is absent, along with common synonyms such as 'find papers' or 'evidence search'. Good coverage with a few natural terms missing fits anchor 4 rather than 5's synonym-and-extension-level coverage.

4 / 5

Distinctiveness Conflict Risk

The systematic-review/reproducible-search niche is clear with distinct triggers, but 'multi-database literature search' is broad enough to overlap with generic web-search or evidence-summarization skills. Mostly distinct with minor overlap risk fits anchor 4 rather than 5's minimal-conflict niche.

4 / 5

Total

18

/

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/reference-search/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.