CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

drug-target-evidence-landscape

Organizes the evidence and competitive landscape around a drug, target, or pathway by separating disease relevance, tractability, preclinical evidence, clinical evidence, modality fit, and crowding. Always map what is biologically supported, what is druggable, what has actually advanced, and what remains strategically open. Never confuse target relevance with druggability, preclinical activity with clinical promise, or narrative excitement with validated development maturity. Never fabricate references, trial status, approval status, company activity, or asset metadata.

Quality

69%

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 ./awesome-med-research-skills/Evidence Insight/drug-target-evidence-landscape/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.

A well-structured instructional body with a clear ordered workflow, explicit verification and self-review checkpoints, and genuinely strong reference-module integration. Its two real weaknesses are heavy internal repetition of the same prohibitions across four sections, and a half-orphaned bundle where 8 of 16 reference files are never surfaced.

Suggestions

Consolidate 'Core Function should not', 'Hard Rules', 'What This Skill Should Not Do', and 'Quality Standard' into a single hard-rules section — each currently restates the same separate-relevance-from-druggability and never-fabricate prohibitions 3–4 times.

Delete or integrate the 8 orphaned reference files (e.g. target-assessment-framework.md, literature-integrity-rules.md, translation-readiness-rules.md, preclinical-clinical-evidence-ladder.md) so every file in references/ is reachable from SKILL.md.

Close the Step 8 feedback loop by specifying corrective action when a check fails (e.g. 'if the weakest layer was presented as established, downgrade its wording in Sections B–D and re-verify against Section I before finalizing').

DimensionReasoningScore

Conciseness

Core prohibitions are repeated roughly four times across sections — 'separate target relevance from druggability' appears in the task framing, the Core Function 'should not' list, Hard Rule 1, and the Quality Standard, while 'never fabricate references/trial/approval status' appears in Hard Rule 9, again in 'What This Skill Should Not Do', and a third time in references/literature-and-asset-verification-rules.md. This systematic duplication of 'Core Function should not', 'Hard Rules', 'What This Skill Should Not Do', and 'Quality Standard' matches 'noticeably verbose; several padded sections' rather than incidental over-explanation.

2 / 5

Actionability

For an instruction-only skill the guidance is concrete and executable: an ordered 8-step execution with named deliverables (Step 6 'Must include: same-target competition... whether the space is open, moderately crowded, or heavily crowded'), a mandatory A–I output structure with required sub-bullets, and a scripted out-of-scope redirect. It falls short of fully executable because judgment directives like 'summarize disease linkage strength' and 'recommend... the most defensible next-step interpretation' carry no criteria or worked example in the body itself.

4 / 5

Workflow Clarity

The sequence is explicit ('Execution — 8 Steps (always run in order)') with a verification gate at Step 2 ('Retrieve and Verify Evidence Before Landscape Claims... Do not present trial status, approval status, developer identity, or competitive activity as established fact without direct verification') and a pre-finalize self-check at Step 8 including a fallback interpretation. It misses a 5 because Step 8 identifies weaknesses but never says what to revise or re-verify when a check fails — no explicit feedback loop back to earlier steps.

4 / 5

Progressive Disclosure

The 'Reference Module Integration' section maps all 8 referenced modules to specific output sections and steps, and all 8 paths exist exactly as named with no nesting deeper than one level. However, references/ contains 16 files — 8 (e.g. target-assessment-framework.md, literature-integrity-rules.md, translation-readiness-rules.md, scope-framing-rules.md) are never referenced from SKILL.md, leaving half the bundle as undiscoverable clutter that goes beyond a purely minor organization gap.

4 / 5

Total

14

/

20

Passed

Description

66%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, domain-specific description that enumerates concrete capabilities and is clearly third-person and guardrail-rich, but it never tells the user (or the model) when to invoke it, and it leans long — two sentences restate prohibitions that belong in the body. Adding an explicit trigger clause would fix its weakest dimension (completeness) at little cost.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks about the evidence, competition, or whitespace around a drug, target, or pathway, or wants to compare biological rationale against development maturity.'

Trim the two 'Never...' guardrail sentences to one short clause so the description stays within the ~1024-character sweet spot and reads as capabilities plus triggers rather than constraints.

Add one or two natural synonyms users would actually say ('target landscape', 'competitive scan', 'pipeline crowding') to strengthen trigger matching against sibling biomedical skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions with named dimensions ('separating disease relevance, tractability, preclinical evidence, clinical evidence, modality fit, and crowding'), but two of its four sentences ('Never confuse...', 'Never fabricate...') restate guardrails rather than add capabilities, and 'Organizes the evidence and competitive landscape' is mildly abstract — slightly below the terse, comprehensive action list of a 5.

4 / 5

Completeness

The 'what' is clear and multi-dimensional (organizes evidence and competitive landscape across six separated dimensions), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'Always map what is biologically supported...' is an instruction to the model, not a usage trigger, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage for the domain — 'drug', 'target', 'pathway', 'evidence', 'preclinical', 'clinical', 'competitive landscape', 'crowding' — but common user phrasings like 'target landscape', 'pipeline', 'drug discovery', or 'due diligence' are missing, keeping it below comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche is carved by the evidence-layer separation language ('tractability', 'crowding', 'development maturity', 'modality fit'), but the bundle's orphaned sibling-style reference files (e.g. target-assessment-framework.md, competition-landscape-rules.md) indicate overlap risk with closely related biomedical-research skills, so conflict risk is minor rather than minimal.

4 / 5

Total

15

/

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/drug-target-evidence-landscape/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.