CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mechanism-flowchart

Generates Mermaid flowchart code and visual diagrams for pathophysiological.

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/Data Analysis/mechanism-flowchart/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 contains a solid executable core — a verified Python example, concrete commands, a parameter table, and output specification — but it is wrapped in generic template boilerplate (risk tables, security checklists, lifecycle metadata with a stale 2026-03-06 next-review date) and circular self-references that dilute the useful content. Workflow guidance is present but abstract, and reference navigation is vague with one missing cited file.

Suggestions

Delete the circular filler lines ("See `## Features` above for related details.", etc.) and the generic template sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template) or move them to a reference file.

Rewrite the Workflow section as concrete task steps tied to the script (e.g., run scripts/main.py with the mechanism text, validate the generated Mermaid in mermaid.live, refine node labels) instead of abstract scope-management language.

Fix broken references: either add the missing requirements.txt or remove "Declared in requirements.txt" from Dependencies, and point to references/guidelines.md by name instead of the generic "Reference material available in `references/`".

DimensionReasoningScore

Conciseness

The body is noticeably verbose with several padded sections: circular self-referential filler ("See `## Features` above for related details.", "See `## Prerequisites` above", "See `## Workflow` above"), generic template boilerplate unrelated to the skill's actual task (Risk Assessment table, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template), a duplicated py_compile command in both "Quick Check" and "Audit-Ready Commands", and an auto-generated broken sentence ("Use this skill when the task needs Generates Mermaid flowchart code..."). It is above 1 because genuinely useful concrete sections (parameters table, output format, example, sample output) do exist; it is below 3 because well over half the body is boilerplate that adds no skill-specific value.

2 / 5

Actionability

The Example Usage is real, executable Python that matches the actual packaged code (scripts/main.py defines `MechanismDiagram` and `generate(mechanism_description, ...)`), and the commands (`python -m py_compile scripts/main.py`, `python scripts/main.py`), the Input Parameters table, and the Output Format JSON are concrete. Minor gaps keep it below 5: no CLI invocation example (python scripts/main.py with arguments is undocumented), the `rendered_svg` output is unspecified, and Dependencies cites a requirements.txt that does not exist. It is above 3 because the code shown is copy-paste ready and verified against the actual script, not pseudocode.

4 / 5

Workflow Clarity

The Workflow section lists five sequenced steps, and Quick Check plus Error Handling provide some validation checkpoints (py_compile before execution, fallback path on failure), but the workflow steps themselves are abstract template language ("Confirm the user objective...", "Validate that the request matches the documented scope...") rather than a concrete task sequence (parse input → run generate → validate mermaid syntax → render). It is above 2 because a sequence with an explicit pre-execution validation and an error-recovery path is present; it is below 4 because the checkpoints are generic and not tied to the actual diagram-generation steps.

3 / 5

Progressive Disclosure

The bundle structure is real and shallow (scripts/main.py and references/guidelines.md both exist and are referenced generically as "Reference material available in `references/`"), but the body inlines substantial content that belongs in reference files (Risk Assessment, Security Checklist, Evaluation Criteria, Sample Output details) and points to references only vaguely rather than by filename. One cited dependency target (requirements.txt) does not exist. It is above 2 because sections are present and the bundle files are one level deep and genuinely usable; it is below 4 because references are not clearly signaled per-file and boilerplate that should be split out is inlined.

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 names a concrete, distinctive capability (Mermaid flowchart generation for medical mechanisms) but is truncated mid-sentence, missing any "Use when..." trigger guidance, and lacking natural synonyms like "drug mechanism" or "disease pathway". It reads like a cut-off fragment rather than a polished trigger description.

Suggestions

Fix the truncated sentence — extend "for pathophysiological" to name the full scope, e.g., "pathophysiology, disease pathways, and drug mechanisms of action".

Add an explicit trigger clause, e.g., "Use when the user asks for a flowchart, mechanism diagram, or visual representation of a disease pathway or drug action."

Include natural trigger terms users would say: "mechanism of action", "disease pathway", "medical diagram", "pathophysiology diagram".

DimensionReasoningScore

Specificity

"Generates Mermaid flowchart code and visual diagrams for pathophysiological." names the domain (Mermaid flowcharts, pathophysiology) and 1-2 concrete actions (generate flowchart code, generate diagrams), but coverage is not comprehensive — the body's drug action pathways, sequence/state diagram types, and export formats are unstated, and the sentence is truncated ("for pathophysiological." lacks a noun), leaving the action scope unclear. It is below 4 because only two actions are named and the truncation muddies what else is covered; it is above 2 because the actions named are genuinely concrete, not generic.

3 / 5

Completeness

The "what" is stated clearly ("Generates Mermaid flowchart code and visual diagrams"), but there is no "Use when..." clause or any explicit trigger guidance for when to invoke the skill; per the judging guidelines a missing 'Use when' clause caps completeness at 3. Not 4 because the "when" is entirely absent rather than merely under-specified; not 2 because the "what" is concrete and specific.

3 / 5

Trigger Term Quality

Relevant keywords are present ("Mermaid flowchart", "diagrams", "pathophysiological"), but natural user phrases and synonyms are missing — e.g., "drug mechanism", "disease pathway", "medical diagram", "pathophysiology", "mechanism of action" — and "pathophysiological" is an adjective, not a phrase a user would naturally say. It is above 2 ("Works with files") because multiple relevant terms appear, but below 4 because common variations a user would actually utter are absent.

3 / 5

Distinctiveness Conflict Risk

"Mermaid flowchart" plus "pathophysiological" carves out a clear niche (medical mechanism diagramming) with mostly distinct triggers and only minor overlap risk with generic diagramming or chart skills. Not 5 because the truncated description omits "drug action pathways" and other distinct medical triggers, weakening the niche boundary; not 3 because Mermaid + pathophysiology is far more specific than "Works with document files".

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/Data Analysis/mechanism-flowchart/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.