CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

emerging-topic-scout

A real-time monitoring system for identifying "incubation period" research hotspots in biological and medical sciences before they are defined by mainstream journals.

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/emerging-topic-scout/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 body delivers genuinely executable guidance — copy-paste commands, a complete parameter table, config and output examples, and validation commands — but wraps it in heavy boilerplate and repetition, breaks rendering with unclosed code fences, inlines API documentation already present in references/README.md, and scatters the workflow across redundant sections. It lands mid-scale: actionable core, poorly disciplined presentation.

Suggestions

Cut the padding: remove the boilerplate 'When to Use' / 'Key Features' / 'Implementation Details' sections, deduplicate the dependency list, and state the Cloudflare workaround once in 'Known Issues' — this is the single biggest conciseness win since the caveat currently appears 5+ times.

Fix the broken markdown: close the ```text fences in 'Legacy Configuration' and 'Example 2: Daily Scan with bioRxiv' (they currently swallow the Parameters table and following headings), fix the duplicate 'Example 2' headings, and replace the personal absolute path in Installation with a relative one.

Move the inlined API endpoint documentation (duplicated in references/README.md) and the full config.yaml/output-format examples into a reference file with a one-line pointer, and merge Workflow / Example run plan / Quick Check / Audit-Ready Commands into a single sequenced procedure with the py_compile and smoke_test checkpoints.

DimensionReasoningScore

Conciseness

The body is heavily padded: boilerplate sections ('When to Use' restating the description verbatim, 'Key Features', 'Implementation Details') that add no task-specific content, duplicate dependency entries (requests, feedparser, textblob listed twice), the Cloudflare caveat repeated in 5+ places (Overview, Network Access Notice, Usage, Parameters, Known Issues), and two competing 'Example 2' sections. This matches 'noticeably verbose; several unnecessary explanations or padded sections'. It is not a 1 because the padding is redundancy and boilerplate rather than extensive explanation of concepts Claude already knows.

2 / 5

Actionability

Concrete, executable commands are abundant — 'python scripts/main.py --sources arxiv --days 7 --output json', 'python -m py_compile scripts/main.py', 'python scripts/smoke_test.py' — plus a full parameter table with defaults, a complete config.yaml example, and concrete output-format examples. It is not a 5 because of broken unclosed ```text fences (in 'Legacy Configuration' and 'Example 2: Daily Scan with bioRxiv') that swallow the Parameters table and subsequent headings into code blocks, a non-portable personal install path ('/Users/z04030865/.openclaw/...'), and a dangling 'See ## Usage above' reference pointing to a section that appears later.

4 / 5

Workflow Clarity

Validation checkpoints do exist (py_compile, smoke_test.py as deterministic fallback, 'Quick Check', 'Audit-Ready Commands'), so it sits above 'validation absent'. However, the actual sequence is fragmented across at least six redundant sections (Workflow, Example run plan, Quick Check, Audit-Ready Commands, Installation, Usage), and the 'Workflow' section itself is generic process boilerplate ('Confirm the user objective... Validate that the request matches the documented scope') rather than a skill-specific operational sequence — matching 'steps listed but... sequence present but checkpoints missing or implicit' in coherence terms.

3 / 5

Progressive Disclosure

The bundle structure is real and referenced (references/README.md exists and is explicitly pointed to in a References section; scripts/main.py, smoke_test.py, requirements.txt all exist and are referenced), giving it structure above 'minimal'. But large content that clearly belongs in separate files is inlined in SKILL.md — the API Endpoints section duplicates documentation already in references/README.md, plus full config.yaml, JSON/Markdown output examples, and the trending-score algorithm — matching 'some structure but could be better organized; content that should be separate is inline'.

3 / 5

Total

12

/

20

Passed

Description

53%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 communicates a clear, distinctive 'what' in a niche domain but stops there: it names a single capability, omits the concrete supporting actions the skill actually performs, and — critically for triggerability — contains no 'Use when...' clause or natural synonym coverage. It sits at the middle of the scale: informative but not yet a reliable router.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to spot emerging research trends, trending preprint topics, or new hot areas in biology or medicine literature before they become mainstream' — this lifts completeness past the current cap of 3.

Include natural trigger synonyms users would actually say: 'emerging trends', 'trending research topics', 'preprint monitoring', 'literature hot topics', alongside the current 'research hotspots'.

Replace the single noun-phrase system description with concrete action verbs, e.g. 'Monitors arXiv/bioRxiv/medRxiv feeds, detects spikes in topic frequency and keyword clusters, and outputs ranked emerging-topic reports', to sharpen specificity.

DimensionReasoningScore

Specificity

The description names its domain ("biological and medical sciences") and one concrete capability ("identifying 'incubation period' research hotspots... before they are defined by mainstream journals"), which matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because it lists no further specific actions (no monitoring of specific sources, trend analysis, alerts, or report generation), and not a 2 because the stated action is concrete rather than generic like 'Processes PDF files'.

3 / 5

Completeness

The 'what' is clear (a real-time monitoring system that identifies early research hotspots), but there is no 'when' — no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. This is not a 4 because the 'when' is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

It contains some natural phrases a user might say ("research hotspots", "real-time monitoring", "biological and medical sciences"), but misses common variations and synonyms such as 'emerging trends', 'trending research topics', 'preprint monitoring', or 'literature scanning' — matching the anchor 'some relevant keywords but missing common variations or synonyms'. The quoted phrase "incubation period" is also potentially confusing since it primarily evokes disease incubation rather than early-stage topics.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct — early detection of emerging biomedicine research topics before mainstream coverage — with minor overlap risk against generic literature-review or search skills, matching 'mostly distinct; minor overlap risk with closely related skills'. It is not a 5 because the description does not include distinct trigger phrases that would fully separate it from adjacent literature-surveillance skills.

4 / 5

Total

13

/

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/emerging-topic-scout/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.