CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blockbuster-therapy-predictor

Comprehensive analytics tool for forecasting breakthrough therapeutic technologies by integrating multi-dimensional data sources including clinical development pipelines, intellectual property landscapes, and capital mar.

Quality

60%

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/blockbuster-therapy-predictor/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 skill has genuinely useful core content — working commands, parameters, scoring methodology, and expected output — but it is buried in template filler, duplicated sections, and confusing self-references. The execution path is not one clear sequence but three overlapping variants, and nearly all detail lives inline in SKILL.md instead of in the references/ directory.

Suggestions

Cut template boilerplate: the empty '## Dependencies', the 'See `## Features`/`## Usage` above' filler sections, the duplicate '## References' heading, and redundant Prerequisites/Security/Lifecycle sections that don't guide execution.

Merge 'Example run plan', 'Workflow', and 'Usage' into a single linear workflow with one validation checkpoint (py_compile) and one fallback path.

Move the output samples, scoring methodology, thresholds table, and supported-technologies table into references/ files and link them from a compact overview.

DimensionReasoningScore

Conciseness

The ~343-line body is heavily padded with template boilerplate: an empty '## Dependencies', a '## Prerequisites' that duplicates the Requirements File section, two separate '## References' headings, a self-referential 'Key Features' that says 'See `## Features` above', plus Risk Assessment / Security Checklist / Lifecycle Status / Evaluation Criteria sections that add little actionable value. This matches 'Noticeably verbose; several unnecessary explanations or padded sections'; it avoids a 1 only because it never explains basic concepts Claude already knows.

2 / 5

Actionability

Concrete, executable commands are present ('python scripts/main.py --tech PROTAC,mRNA,CRISPR', '--output json', '--threshold 70', a full parameter table, sample console/JSON output, and py_compile verification). Minor gaps keep it below 5: the 'Example Usage' hardcodes an unrelated cd path ('20260318/scientific-skills/...'), and 'Edit the in-file CONFIG block... if the script uses fixed settings' is conditional and vague.

4 / 5

Workflow Clarity

A numbered 5-step Workflow with an explicit fallback exists and a Quick Check (py_compile) provides a validation checkpoint, but the sequence is duplicated and muddled across three competing paths ('Example run plan', 'Workflow', and 'Usage') that overlap and cross-reference each other with 'See `## Usage` above' / 'See `## Workflow` above'. This fits 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit' — the duplication makes the real execution order harder to follow than anchor 4's 'clear sequence' allows.

3 / 5

Progressive Disclosure

The bundle reference (references/audit-reference.md) exists and is linked, but the body inlines large amounts of material that belongs in separate files — full console/JSON output samples, scoring methodology tables, and the 10-technology supported table — while navigation is weakened by duplicated section names and 'see above' pointers. This matches 'Some structure but could be better organized... content that should be separate is inline' rather than 4's 'most content is appropriately placed'.

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 specific niche (biotech/therapeutics investment forecasting) but is undermined by a mid-word truncation ('capital mar'), buzzword framing, and a complete absence of any 'Use when...' trigger guidance. It reads as a one-line capability summary rather than a full skill description.

Suggestions

Restore the truncated ending and complete the sentence (e.g., '...and capital market indicators').

Add an explicit trigger clause, e.g., 'Use when the user asks to predict blockbuster drugs, compare therapeutic platforms, or prioritize biotech R&D/investment targets.'

Include natural user synonyms such as 'drug pipeline', 'pharma/biotech investment', and 'blockbuster therapy prediction'.

DimensionReasoningScore

Specificity

The description names the domain ('forecasting breakthrough therapeutic technologies') and 1-2 concrete actions ('forecasting', 'integrating multi-dimensional data sources') with the source types listed, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It scores below 4 because 'Comprehensive analytics tool' is buzzword filler and the sentence is truncated mid-word ('capital mar'), leaving coverage incomplete; it is above 2 because the data-source enumeration (clinical pipelines, IP, capital markets) is genuinely concrete.

3 / 5

Completeness

The 'what' is clearly stated (forecasts breakthrough therapies by integrating clinical, IP, and market data) but there is no 'Use when...' or equivalent trigger clause, capping completeness at 3 per the judging guidelines. Not 4/5 because 'when' is entirely absent rather than merely implicit; not 2 because the 'what' half is concrete, not vague.

3 / 5

Trigger Term Quality

Terms like 'therapeutic technologies', 'clinical development pipelines', and 'capital mar[kets]' are relevant, but common user phrasings are missing — 'blockbuster drugs', 'drug pipeline', 'biotech/pharma investment', 'which therapies will succeed'. This fits 'Some relevant keywords but missing common variations or synonyms' rather than 4, whose keyword coverage would include the natural synonyms users actually say.

3 / 5

Distinctiveness Conflict Risk

The niche is mostly distinct — 'forecasting breakthrough therapeutic technologies' via clinical/patent/funding data has clear triggers with only minor overlap risk against closely related biotech-analytics skills. Not 5 because the generic 'Comprehensive analytics tool... multi-dimensional data sources' framing is a template pattern likely shared by sibling skills in the same collection, and the truncated ending blurs the final differentiator.

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/blockbuster-therapy-predictor/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.