CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

experiment-detail-comparator

Compare experimental method details between two Zotero PDF papers, identify protocol differences (ratios, dosages, timing, conditions), search supporting literature to explain why they differ, and generate an HTML report. Use when you need a parameter-level comparison of two methods and evidence-backed reasons for discrepancies.

Quality

76%

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/Other/experiment-detail-comparator/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 manual, script-by-script workflow is genuinely strong — correctly sequenced, concrete, and verifiable against the bundle — but the skill is undermined by a missing recommended entry point, a broken and misleading validation shortcut, and a tail of generic boilerplate that dilutes the document. Detail that belongs in reference files is fully inlined.

Suggestions

Add `run_comparison.py` to the bundle or replace the 'End-to-end run (recommended)' section with the working 7-step manual workflow as the primary path, so the headline example no longer references a nonexistent script.

Fix the validation shortcut: `compare_methods.py` has no `--help` handling (positional sys.argv only), so document a real smoke test (e.g., run it against two small fixture method JSON files) and delete the fabricated 'Expected output format' block that does not match the script's output.

Trim the generic boilerplate sections ('Required Inputs', 'Recommended Workflow', 'Output Contract', 'Deterministic Output Rules', 'Completion Checklist') and move the extraction schema, evidence-grading rubric, and query templates into files under `references/` to reduce SKILL.md to an actionable overview.

DimensionReasoningScore

Conciseness

The core sections (Dependencies, Example Usage, Implementation Details) are dense and earn their tokens, but roughly a quarter of the body is generic policy boilerplate — "Required Inputs" ("A clearly specified task goal aligned with the documented scope"), "Output Contract", "Deterministic Output Rules", "Completion Checklist" — that teaches nothing specific to this skill, and validation guidance is duplicated at the top ("Validation Shortcut") and bottom ("Quick Validation"). Mostly efficient with a removable padding layer, which fits the 3 anchor better than the 2 anchor since the padding is a minority of the document.

3 / 5

Actionability

The 7-step manual workflow gives exact, verifiable commands for real bundle scripts, but the two most prominent commands are broken: the recommended end-to-end entry point `python run_comparison.py ...` references a script that does not exist anywhere in the bundle, and `python scripts/compare_methods.py --help` fails because the script parses positional sys.argv with no argparse. This is more than the 'minor gaps' of the 4 anchor — a user following the documented recommended path hits immediate failure — though the majority of guidance remains executable, keeping it above the 2 anchor.

3 / 5

Workflow Clarity

The manual workflow is clearly sequenced (steps 1–7, each with a concrete command), but the validation checkpoints are fabricated rather than functional: the documented 'Expected output format' for the validation shortcut ("Result file: experiment_detail_comparator_result.md / Validation summary: PASS/FAIL") matches nothing the script actually prints, and the shortcut command itself errors out. Checkpoints exist on paper but not in effect, matching the 3 anchor (checkpoints missing or non-functional) rather than the 4 anchor (most checkpoints present).

3 / 5

Progressive Disclosure

All referenced script paths (compare_methods.py, extract_method_section.py, etc.) resolve to real files in scripts/, and sections are well organized. However, there are no reference files at all — the full extraction schema, the evidence-grading rubric, query templates, and HTML report structure are all inlined in a ~385-line SKILL.md. That fits the 3 anchor ('content that should be separate is inline') with good structure; not the 4–5 anchors, which expect detail appropriately split into well-signaled separate files.

3 / 5

Total

12

/

20

Passed

Description

92%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 description: concrete, third-person, action-oriented, with an explicit 'Use when' trigger clause and a well-delineated niche. The only weakness is modest synonym coverage of natural trigger phrases, which keeps trigger term quality at 4 rather than 5.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with named parameters: "Compare experimental method details between two Zotero PDF papers, identify protocol differences (ratios, dosages, timing, conditions), search supporting literature to explain why they differ, and generate an HTML report" — concrete action verbs plus enumerated parameter types give comprehensive coverage of the skill's scope. It does not fit the anchor 4 ('minor gaps in coverage') because every capability the skill body implements (compare, diff, literature search, HTML report) is named.

5 / 5

Completeness

Both questions are answered explicitly: the 'what' is the four concrete actions, and the 'when' is the trigger clause "Use when you need a parameter-level comparison of two methods and evidence-backed reasons for discrepancies." This matches the 5 anchor (clear what AND when with concrete trigger phrases), not the 4 anchor where the 'when' is only implicit or less specific.

5 / 5

Trigger Term Quality

Good keyword coverage: "parameter-level comparison", "protocol differences", "Zotero PDF papers", "evidence-backed reasons for discrepancies" are phrases a user with this need would plausibly say. It falls short of the 5 anchor (comprehensive synonyms/extensions — e.g., 'methods section', 'experimental procedure', 'side-by-side comparison') but is well above the 3 anchor ('some relevant keywords but missing common variations').

4 / 5

Distinctiveness Conflict Risk

A clear niche — pairwise comparison of two Zotero-indexed papers' experimental methods with literature-backed rationale generation — with distinct triggers ("two Zotero PDF papers", "parameter-level comparison of two methods") that would not fire for generic PDF or literature-search skills. Minimal conflict risk, matching the 5 anchor.

5 / 5

Total

19

/

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/Other/experiment-detail-comparator/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.