CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-article-weekly

Generates a weekly academic literature report based on keywords using PubMed. Use when the user wants to track recent research progress on a specific topic, automatically retrieving, classifying, and summarizing relevant papers from the last 7 days.

Quality

81%

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

67%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 operative core is strong — a verified, executable script command with matching CLI flags, complete classification/summarization prompts, a specified output format, and quality rules guarding against hallucination and empty results. However, roughly a third of the body is auto-generated template padding that repeats the description verbatim three times, includes a non-portable dated example path, and contains a broken cross-reference ('See ## Workflow above'). Cutting the When to Use/Key Features/Dependencies/Implementation Details boilerplate would make this a substantially leaner, higher-scoring skill.

Suggestions

Conciseness: delete the template filler — collapse 'When to Use', 'Key Features', 'Dependencies', and 'Implementation Details' into a short 'When to Use' and a brief dependency note, removing the three verbatim repeats of the frontmatter description.

Conciseness/actionability: replace the non-portable Example Usage path ('20260316/scientific-skills/...') with a repo-relative example and a realistic keyword (e.g., 'python scripts/pubmed_search.py --keywords "lung cancer" --days 7 --limit 20 --format markdown').

Workflow clarity: add a validation checkpoint for script failures — check the exit status and handle API/network errors or malformed JSON output, not just the empty-results case; also fix the broken 'See ## Workflow above' cross-reference.

DimensionReasoningScore

Conciseness

The core Workflow, prompts, and Quality Rules sections are lean, but roughly a third of the body is template padding: the description is repeated verbatim three times ('Scope-focused workflow aligned to: Generates a weekly academic literature report...'), 'Key Features' and 'Dependencies' ('not explicitly version-pinned in this skill package. Add pinned versions if...') are filler, and 'Implementation Details' restates generic best practices Claude already knows ('validate the request, choose the packaged workflow'). Not 2 because the operative ~70% (workflow commands, prompts, output format, error handling) has no over-explanation and every token there earns its place.

3 / 5

Actionability

The workflow provides a copy-paste-ready command ('python scripts/pubmed_search.py --keywords "{keywords}" --days 7 --limit 20 --format markdown') whose flags match the actual bundled script, plus complete classification and summarization prompts with a JSON output contract and a concrete empty-results message. Not 5 because the Example Usage section cd's into a non-portable dated path ('20260316/scientific-skills/Evidence Insight/research-article-weekly') and the run plan includes hedged, non-executable steps ('Edit the in-file CONFIG block or documented parameters if...').

4 / 5

Workflow Clarity

The four-step sequence (draft report via script → optional AI refinement with classification prompt → grouped final report → combined output with Executive Summary) is clearly ordered, and Quality Rules supply checkpoints: 'Must use real data returned from the pubmed_search.py script. Do not hallucinate papers', 'Ensure all retrieved and relevant papers are included', and explicit no-results handling. Not 5 (capped below) because there is no validation for script-level failures — network/API errors, malformed output, or non-zero exit — only the empty-results case is handled.

4 / 5

Progressive Disclosure

Structure is good: the single bundle file 'scripts/pubmed_search.py' is referenced by exact path and exists, headers organize the body, and the inline AI-refinement prompts are appropriately placed in SKILL.md as core operating instructions rather than pushed to nested references. Not 5 because of minor organization gaps: 'See `## Workflow` above for related details' points the wrong way (Workflow appears below that section), and the template filler sections (Key Features, Dependencies, Implementation Details) dilute the overview's navigability.

4 / 5

Total

15

/

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: it states what the skill does with four concrete actions and an explicit 'Use when the user wants to track recent research progress on a specific topic' trigger clause, in proper third-person voice. Main improvement opportunities are adding synonyms such as 'literature search', 'journal articles', or 'research update' to broaden natural trigger coverage, and tightening the niche boundary beyond PubMed-specific requests.

Suggestions

Add natural synonyms users would say — e.g., 'literature search', 'journal articles', 'new publications', 'research update' — to widen trigger coverage.

Make the trigger boundary more explicit (e.g., 'Use when the user wants a PubMed-based weekly literature update') to reduce overlap with general web-search or literature-review skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Generates a weekly academic literature report', 'automatically retrieving, classifying, and summarizing relevant papers from the last 7 days' — anchored to a named source (PubMed) and timeframe, which comprehensively covers the skill's retrieve→classify→summarize→report pipeline. It is not 4 because there is no meaningful gap in the action coverage for this niche.

5 / 5

Completeness

It explicitly answers both parts: 'what' via 'Generates a weekly academic literature report based on keywords using PubMed... retrieving, classifying, and summarizing' and 'when' via the concrete trigger clause 'Use when the user wants to track recent research progress on a specific topic'. This matches the anchor 5 example structure (what + explicit 'Use when' trigger phrases); it is above 4 because the 'when' clause is specific, not generic.

5 / 5

Trigger Term Quality

Natural trigger terms are present: 'PubMed', 'weekly academic literature report', 'track recent research progress', 'papers', 'last 7 days'. It falls short of 5 because common user phrasings like 'literature search', 'journal articles', 'new publications', or 'research update' are missing.

4 / 5

Distinctiveness Conflict Risk

The PubMed + weekly-report + 7-day window framing ('using PubMed', 'relevant papers from the last 7 days') gives a clear niche with mostly distinct triggers. Not 5 because 'track recent research progress on a specific topic' could also fire for general literature-monitoring or web-search requests that are not PubMed-specific, leaving minor overlap risk with closely related search skills.

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/research-article-weekly/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.