CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

comparison-table-gen

Auto-generates comparison tables for concepts, drugs, or study results.

Quality

63%

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/comparison-table-gen/SKILL.md
SKILL.md
Quality
Evals
Security

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 body delivers genuinely executable usage (parameters table, concrete CLI examples, output format, fallback paths) buried in heavy template boilerplate: self-referential sections, generic checklists, and vague pointer text to nonexistent detail. The core usable content is roughly a third of the file; the rest is padding that taxes the context window.

Suggestions

Cut the meta-sections that only point at other sections ("Key Features", "Dependencies", "Example Usage", "Implementation Details" openers like "See `## Features` above") and merge their one-line substance into the relevant sections.

Drop or drastically shrink the generic boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Response Template) — none of it is specific to comparison tables.

Replace the vague "`references/` contains supporting rules" pointers with a concrete link (e.g. "Table formatting standards: see [references/guidelines.md](references/guidelines.md)") and populate that file with the actual formatting standards it promises.

DimensionReasoningScore

Conciseness

The 214-line body is noticeably verbose with padded template sections: "Key Features" and "Dependencies" sections that only say "See `## Features` above for related details", a "When to Use" bullet that repeats the frontmatter description verbatim ("task needs Auto-generates comparison tables..."), and generic boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Response Template) that adds almost no skill-specific information. Not 1 because it doesn't explain concepts Claude already knows — it's redundant scaffolding, not educational padding.

2 / 5

Actionability

There is executable, copy-paste-ready guidance: a parameters table (`--items`, `--attributes`, `--output`), concrete invocations ("python scripts/main.py --items \"Drug A,Drug B\" --attributes \"Mechanism,Dose,Side Effects\""), a compile check, and a JSON output format. Not 5 because the "Example Usage" section's `cd "20260318/scientific-skills/..."` path is an odd hardcoded relative path, and no expected output of a real run is shown, leaving minor gaps.

4 / 5

Workflow Clarity

The Workflow section gives a clear 5-step sequence (confirm objective → validate scope → execute with available inputs → structured result → fallback on failure) with checkpoints such as "stop early if the task would require unsupported assumptions" and Error Handling defines explicit failure paths. Not 5 because the validate→fix→retry feedback loop is described only abstractly — the sole concrete validation is `python -m py_compile scripts/main.py`, and the steps reference no per-step commands — and not 3 because the sequence and error/fallback checkpoints are genuinely present.

4 / 5

Progressive Disclosure

Bundle structure is real (scripts/main.py and references/guidelines.md both exist), but references are only gestured at generically — "Reference material available in `references/`" and "`references/` contains supporting rules, prompts, or checklists" — with no named link to guidelines.md, and references/guidelines.md itself is just two bullet headings with no substance. Meanwhile large blocks of generic content (Security Checklist, Lifecycle Status, Evaluation Criteria) are inlined in SKILL.md where they add nothing, matching 'some structure but could be better organized; references present but not clearly signaled'.

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 a specific, domain-anchored capability but stops there: it has no trigger/usage clause and misses natural synonyms like 'compare', 'versus', or 'side-by-side'. It reads as a one-line capability summary rather than a full activation description.

Suggestions

Append an explicit trigger clause, e.g. "Use when comparing treatments, drugs, therapies, or study outcomes side by side, or when the user mentions comparing/versus/vs concepts."

Add natural user phrasings as trigger terms: 'compare', 'versus', 'vs', 'side-by-side', 'differences between', alongside the existing 'comparison table'.

Consider adding one more concrete output cue (e.g. 'outputs markdown and HTML tables') to lift specificity without adding fluff.

DimensionReasoningScore

Specificity

"Auto-generates comparison tables" is a concrete action and "concepts, drugs, or study results" names the domain objects, but only one action verb is offered. This matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor, not 4 (which requires several specific actions like extract/fill/merge) and not 2 (the action is concrete, not generic).

3 / 5

Completeness

The description answers 'what' clearly ("Auto-generates comparison tables for concepts, drugs, or study results") but contains no 'Use when...' clause or any trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because 'when' is entirely absent rather than merely weak, and not 2 because the 'what' is specific, not vague.

3 / 5

Trigger Term Quality

"Comparison tables", "drugs", and "study results" are relevant keywords a medical researcher might use, but common natural phrasings are missing — users would more likely say "compare", "versus", "vs", "side-by-side", or "differences between treatments" rather than "auto-generates comparison tables". Some relevant keywords but missing common variations, so 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

The medical framing ("drugs", "study results") carves out a fairly clear niche with low conflict risk against generic table-formatting skills, matching 'mostly distinct; minor overlap risk with closely related skills'. It is not 5 because the triggers do not fully pin the niche — a request to compare general concepts or products would also plausibly match generic table/markdown skills.

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/comparison-table-gen/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.