CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

preprint-surveillance-finder

Tracks the latest preprints and emerging research topics related to your topic across bioRxiv, medRxiv, and arXiv. Use when a user wants to discover what is being published right now before it reaches journals, monitor competitor directions, spot new methodology trends, or get an early-warning scan of a research area. Triggers on phrases like "what's new in X", "latest preprints on Y", "emerging topics in Z", "monitor bioRxiv for", or "what are people working on in this field".

Quality

85%

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

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, honest, and reasonably lean instruction skill with a strong two-mode workflow and an explicit anti-fabrication checklist. Its main weaknesses are that the executable scanner and smoke test in scripts/ are completely undocumented in SKILL.md, and the workflow lacks result-validation checkpoints (time-window verification, empty-result handling).

Suggestions

Document the bundled scanner in SKILL.md with a Quick start command (e.g., `python scripts/main.py --sources biorxiv medrxiv --days 14 --output markdown`) and note scripts/requirements.txt and scripts/smoke_test.py, so the executable path is discoverable.

Add a validation checkpoint in Step 2/3: verify each fetched paper's posting date falls within the requested time window, and define behavior for empty or partial API results (e.g., report the gap explicitly rather than proceeding silently).

Trim redundancy: the blockquote redirect under Input Validation duplicates the out-of-scope list above it, and the persona opener sentence can be dropped without losing guidance.

DimensionReasoningScore

Conciseness

The body is lean for its scope: no explanations of concepts Claude already knows, operational rather than tutorial in tone, and genuinely useful environment-specific notes ('May be blocked by Cloudflare in automated environments', RSS accessible at export.arxiv.org). Minor trimmable padding: the persona opener ('You are an expert research horizon-scanner...') and the blockquote redirect ('Emerging Topic Scout focuses on...') that duplicates the out-of-scope list immediately above it. Not a 5 due to these small redundancies; well above a 3 since there is no real over-explanation.

4 / 5

Actionability

Concrete, copy-paste-ready elements: manual search URL templates for bioRxiv/medRxiv/arXiv, a default time window (14 days), a structured report format, and a deterministic two-mode decision path. Not a 5 because the core instruction 'Query the relevant preprint server API or RSS feed' defers the actual API mechanics to references/README.md, and the fully executable scanner in scripts/ (main.py, with a documented CLI: 'python main.py --sources biorxiv medrxiv --days 7 --output markdown') is never mentioned in the body. Not a 3 because what is present is executable, not pseudocode.

4 / 5

Workflow Clarity

Clear four-step sequence (clarify parameters → execute scan → organize/report → hard rules) with input validation in Step 1 ('ask the user to narrow to a sub-field'), an explicit fallback feedback loop (live access fails → knowledge-synthesis mode, clearly labeled), and a hard-rules checklist ('Never fabricate paper titles, DOIs...'). Not a 5 because there are no checkpoints for verifying fetched papers fall inside the requested time window or handling empty/partial API results before reporting.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview and its one reference (references/README.md) is real, one level deep, and clearly signaled in a References section. However, scoring against the actual bundle structure reveals a significant organization gap: the entire scripts/ directory (main.py scanner, smoke_test.py, requirements.txt) is never referenced from the body, leaving the most executable asset undiscoverable. This goes beyond the 'minor organization gaps' of anchor 4, though it is not the buried/inline pattern of anchor 3's typical failure.

3 / 5

Total

15

/

20

Passed

Description

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

An exemplary description: concrete actions, named data sources, an explicit 'Use when' clause, and a list of natural trigger phrases with synonyms. The only nit is the slightly redundant 'Triggers on phrases' sentence following the 'Use when' clause, and a stray second-person possessive ('your topic') in an otherwise third-person description.

DimensionReasoningScore

Specificity

The description names the domain (preprint monitoring) and enumerates several concrete actions — 'Tracks the latest preprints and emerging research topics', 'discover what is being published right now', 'monitor competitor directions', 'spot new methodology trends', 'get an early-warning scan' — across named sources (bioRxiv, medRxiv, arXiv). Not a 5 because the capability list is use-case phrased rather than a comprehensive inventory of distinct operations. Not a 3 because it goes well beyond 1-2 concrete actions. The sentence voice is third person ('Tracks'), so the second-person penalty does not apply despite the stray possessive 'your topic'.

4 / 5

Completeness

Explicitly answers both questions: 'what' — tracks latest preprints and emerging research topics across bioRxiv/medRxiv/arXiv — and 'when' — an explicit 'Use when a user wants to...' clause plus a 'Triggers on phrases like...' list. This mirrors the anchor-5 example structure exactly. Not a 4 because the 'when' is already fully explicit with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say: "what's new in X", "latest preprints on Y", "emerging topics in Z", "monitor bioRxiv for", "what are people working on in this field", plus natural synonyms (preprints, bioRxiv/medRxiv/arXiv, emerging topics, early-warning). Matches the anchor for full coverage including synonyms; no common variations are missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (preprint surveillance across named servers) with distinct trigger phrases like 'monitor bioRxiv for'. Overlap with adjacent skills (paper download, citation analysis) is minimized because the description scopes to preprint discovery before journal publication. Anchor 5 fits; anchor 4 would require noticeable overlap risk with closely related skills, which is not present.

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/preprint-surveillance-finder/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.