CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

disease-mechanism-evidence-map

Systematically maps mechanism evidence for a disease from molecules to pathways, cell types, tissues, biological consequences, and clinical phenotypes. Always use this skill when a user needs a layered mechanism evidence chain rather than a flat summary or immediate gap analysis. Formal literature citations must be real and verifiable.

Quality

65%

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/disease-mechanism-evidence-map/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 a clear sequenced workflow, well-organized one-level-deep references that all exist, and a defined output structure. Its main weaknesses are heavy cross-section redundancy that bloats token cost and abstract directives that lack execution-level detail such as table schemas or a worked example of a layered evidence chain.

Suggestions

Consolidate the repeated distinctions (direct vs indirect evidence, layer taxonomy, no-fabrication rules) into a single section — they currently appear in 4-5 places (Skill Summary, Core Function, Output Requirements, Hard Rules, What This Skill Should Not Do).

Specify the Key Evidence Chain Table's columns (e.g., axis, link, evidence type, evidence strength, completeness, citation status) and include one short worked example of a layered chain.

Replace abstract directives like 'Prioritize the dominant and best-supported mechanism axes' with concrete selection criteria or a rule of thumb (e.g., number of independent layers with direct human evidence).

DimensionReasoningScore

Conciseness

The body is pervasively redundant: the direct/indirect/inference distinction appears in five sections (Skill Summary, Core Function, Output Requirements, Decision Logic, Hard Rules), the no-fabrication rule in four, and the layer taxonomy is restated at least four times. This matches 'noticeably verbose; several unnecessary explanations or padded sections' rather than the occasional tightening of anchor 3.

2 / 5

Actionability

Concrete structure exists (9-step Decision Logic, output sections A-K, out-of-scope redirect script, sample inputs), but execution-level detail is missing: 'Provide a structured table summarizing the main mechanism chains' specifies no columns, no worked example of a chain is given, and directives like 'Prioritize the dominant and best-supported mechanism axes' remain abstract. Some concrete guidance but incomplete.

3 / 5

Workflow Clarity

A clear 9-step sequence, each step bound to a specific reference module, plus explicit input validation with a stop-and-redirect script and a citation-verification checkpoint (Step 8). Not a 5 because there are no feedback loops or explicit pass/fail validation gates between steps, and the workflow-step checklist fields are only named, not specified.

4 / 5

Progressive Disclosure

All 11 referenced files (references/mechanism-scope-rules.md, references/output-section-guidance.md, etc.) exist, are exactly one level deep, and each is signaled with its purpose. Not a 5 because the 260-line body duplicates rule content inline instead of remaining a lean overview, so content is not fully 'appropriately split' between SKILL.md and the bundle.

4 / 5

Total

13

/

20

Passed

Description

62%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 clearly states what the skill does and when to use it, with an explicit differentiation from flat summaries and gap analysis. Its weaknesses are jargon-heavy trigger phrasing ('layered mechanism evidence chain') and a single-action framing that underrepresents the skill's full capability set.

Suggestions

Add natural trigger phrases users would actually say, e.g. 'Use when the user asks for a mechanism map, pathophysiology overview, or how a disease's mechanism is supported across evidence layers'.

Enumerate the skill's other concrete capabilities (labeling evidence strength, identifying weak chain links, suggesting hypothesis entry points) so the 'what' is comprehensive rather than a single mapping action.

DimensionReasoningScore

Specificity

Names the domain and one core action ('Systematically maps mechanism evidence for a disease from molecules to pathways, cell types, tissues, biological consequences, and clinical phenotypes') with the layer chain enumerated, but other capabilities (evidence-strength labeling, hypothesis entry points, downstream routing) are absent, so coverage is not comprehensive as anchor 4 requires.

3 / 5

Completeness

Both are explicit: what = 'Systematically maps mechanism evidence for a disease from molecules to pathways, cell types, tissues, biological consequences, and clinical phenotypes', and when = 'Always use this skill when a user needs a layered mechanism evidence chain rather than a flat summary or immediate gap analysis'. Not a 5 because the when-clause uses abstract jargon instead of concrete user trigger phrases.

4 / 5

Trigger Term Quality

Relevant keywords are present ('mechanism evidence', 'flat summary', 'gap analysis'), but the primary trigger phrase 'layered mechanism evidence chain' is skill-internal jargon rather than natural user language, and common synonyms like 'pathophysiology', 'mechanism map', or 'evidence chain' variations are missing.

3 / 5

Distinctiveness Conflict Risk

The explicit contrast 'rather than a flat summary or immediate gap analysis' carves a distinct niche from adjacent literature-summary and gap-analysis skills; minor overlap risk remains with general pathway-review or literature-synthesis skills, so it falls just short of the minimal-conflict anchor 5.

4 / 5

Total

14

/

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/disease-mechanism-evidence-map/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.