mechanism-flowchart

Generates Mermaid flowchart code and visual diagrams for pathophysiological.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Data Analysis/mechanism-flowchart/SKILL.md

Quality

Content

56%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 content is well-structured and largely actionable with real executable artifacts, but it is padded with generic template boilerplate and broken cross-references, and it under-uses the available references directory by inlining content that could be split out.

Suggestions

Remove the generic template boilerplate and broken 'See `## X` above' cross-references that point nowhere; keep only mechanism-specific guidance.

Offload detailed material (risk/security checklists, prerequisites, lifecycle/evaluation criteria) into references/ files and point to them explicitly, e.g. 'See references/guidelines.md for visualization best practices'.

Reconcile the Python example's import path with the actual package layout and either ship the referenced requirements.txt or remove the reference.

Dimension	Reasoning	Score
Conciseness	The body is noticeably padded with generic templated boilerplate (e.g. 'See `## Features` above', 'See `## Prerequisites` above', 'See `## Workflow` above'), repetitive scope echoes of the description, and over-explanation of basics like pip install, leaving real signal buried among several unnecessary sections.	2 / 5
Actionability	It provides a concrete Python example, an Input Parameters table, an Output Format spec, a sample Mermaid block, and concrete commands backed by a real scripts/main.py, with only minor gaps such as the top-level import name and a referenced requirements.txt that is absent.	4 / 5
Workflow Clarity	The 5-step workflow includes a Quick Check validation checkpoint and an explicit fallback-on-failure path for a local-script-execution skill, but broken 'See `## X` above' cross-references introduce minor gaps in the actual sequence.	4 / 5
Progressive Disclosure	Sections are organized and references are one level deep, but almost all detail is inlined into a ~220-line SKILL.md while references/guidelines.md is only weakly signaled via a generic 'reference material available' line rather than explicit pointers.	3 / 5
	Total	13 / 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 states concrete actions in a recognizable niche but is marred by a grammatically truncated tail and the absence of an explicit 'Use when' trigger clause, which caps completeness and trigger quality at mid-range.

Suggestions

Complete the truncated 'for pathophysiological' clause, e.g. 'for pathophysiological mechanisms, disease pathways, and drug action pathways'.

Add an explicit 'Use when...' trigger clause naming natural user phrasings like 'flowchart', 'mechanism of action', 'disease pathway', and 'Mermaid diagram'.

Broaden coverage of concrete actions (sequence/state diagrams, multi-format export) to lift specificity toward a 4-5.

Dimension	Reasoning	Score
Specificity	The phrase 'Generates Mermaid flowchart code and visual diagrams' names the domain and a couple of concrete actions, but coverage is not comprehensive (no mention of sequence/state diagrams, drug-action pathways, or export formats) and the trailing 'for pathophysiological' is truncated, pulling it down from a 4.	3 / 5
Completeness	It has a clear 'what' but no explicit 'Use when...' trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3, and 'for pathophysiological' is only a weak implicit 'when'.	3 / 5
Trigger Term Quality	It includes relevant keywords ('Mermaid flowchart', 'pathophysiological') but misses common natural synonyms and phrasings users would say ('mechanism of action', 'disease pathway', 'drug pathway', 'diagram', 'figure'), and the truncated 'for pathophysiological' weakens the naturalness.	3 / 5
Distinctiveness Conflict Risk	The Mermaid + pathophysiology niche is fairly specific and distinguishable from generic skills, with only minor overlap risk against general diagramming skills, fitting between anchors 3 and 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/Data Analysis/mechanism-flowchart/SKILL.md
Commit: f5ef65b

Reviewed: ~3 hours ago

Table of Contents

Discovery Implementation Validation

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.