CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reproducibility-check

Comprehensive reproducibility tool — audit Methods completeness for replication AND promote open science best practices (pre-registration, FAIR data, code sharing, replication design, reporting transparency); trigger when preparing a manuscript, reviewing methodological comple...

Quality

71%

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/reproducibility-check/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 skill body delivers a genuinely actionable, well-sequenced workflow with strong mode-selection logic, explicit checklist validation, and a complete worked example. Its weaknesses are verbosity — the Mode A/B material is duplicated across three sections and known concepts are re-explained — and weak progressive disclosure, with detailed content inlined instead of split into the existing reference files.

Suggestions

Collapse the duplication: remove the "Key Features" section (its bullets are restated nearly verbatim in "When to Use" and in Processing Workflow steps 5–11), keeping one authoritative statement of the Mode A/B capabilities.

Move the detailed Mode B workflow steps, output templates, and the long example output report into references/guide.md, keeping a concise overview in SKILL.md with clear point-of-use pointers (e.g., "Output format: see [guide.md](references/guide.md)") instead of "when available"/"recommended" signaling.

Delete the explanations of concepts Claude already knows — the FAIR-letter expansion, direct vs. conceptual replication definitions, and the "Key Platforms and Tools" descriptions of GitHub/Zenodo/OSF — replacing them with just the names where operationally relevant.

DimensionReasoningScore

Conciseness

The body states the Mode A/B content three times — the "When to Use" list, the "Key Features" bullets, and Processing Workflow steps 5–11 which nearly verbatim duplicate the Key Features Mode B bullets — and explains concepts Claude already knows ("FAIR data management — Findable (persistent identifier, metadata), Accessible...", "direct replication (match original methods), conceptual replication (different methods, same hypothesis)", "GitHub / GitLab — Code version control and sharing"). This matches "noticeably verbose; several unnecessary explanations or padded sections" rather than 3 (only occasional tightening needed) or 1 (no elementary concept padding; most lines carry operational content).

2 / 5

Actionability

Concrete guidance throughout: a 4-step Mode A workflow with priority rules ("High Priority: required to reproduce results"), a complete worked Example Usage showing both input template and full output report, enumerated Output Requirements, named platforms, and explicit mode selection logic ("If both types of input are present → run both modes sequentially"). As an instruction-only skill, absent code is not penalized; it is not 5 because some Mode B steps stay advisory ("Adopt open science badges", "Choose open access publication route") without concrete procedures, and not 3 because the guidance is specific and complete with a full example, not pseudocode-level.

4 / 5

Workflow Clarity

Clear numbered sequences for both modes, an explicit validation step ("Checklist verification — Validate coverage of: sample size/replicates, randomization/blinding...") tied to assets/reproducibility_checklist.md, a trigger condition requesting the full Methods section, and error-handling feedback ("If required inputs are missing, state exactly which fields are missing and request only the minimum"). Not 5 because Mode B steps 5–11 have no verification checkpoints — they are advisory guidance with no way to confirm outputs — and not 3 because validation, sequencing, and error recovery are explicitly written out.

4 / 5

Progressive Disclosure

Bundle files exist (assets/reproducibility_checklist.md, references/guide.md) but are weakly signaled ("when available", "Dependencies: ... (recommended for ...)"), while the body inlines substantial content that belongs in those references — the ~30-line example output report, the full Mode B workflow detail, and Output Requirements that overlap with references/guide.md's output checklists and format. This matches "some structure but references present yet not clearly signaled; content that should be separate is inline" rather than 4 (clear point-of-use pointers, content appropriately split) or 2 (the body is well-sectioned and references are real and one level deep).

3 / 5

Total

13

/

20

Passed

Description

75%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 conveys what the skill does with several specific, natural trigger keywords and a well-differentiated niche. Its main defect is that the text is physically truncated mid-word ("reviewing methodological comple..."), which cuts the trigger clause short and prevents full completeness.

Suggestions

Fix the truncated description: restore the full text so the trigger clause reads completely (e.g., "...trigger when preparing a manuscript, reviewing methodological completeness, checking reproducibility, or asking about pre-registration, FAIR data, or replication.").

Add the natural user phrasing "methods section" as an explicit trigger term, since users auditing completeness will typically mention their Methods section.

DimensionReasoningScore

Specificity

The description names concrete actions — "audit Methods completeness for replication" and "promote open science best practices (pre-registration, FAIR data, code sharing, replication design, reporting transparency)" — listing several specific capabilities. It is not 5 because "Comprehensive ... tool" and "promote ... best practices" carry mild generic framing with minor coverage gaps, and not 3 because more than 1-2 concrete actions are explicitly enumerated.

4 / 5

Completeness

The "what" is explicit ("audit Methods completeness for replication AND promote open science best practices") and a "when" clause exists ("trigger when preparing a manuscript, reviewing methodological comple..."). It is not 5 because the when-clause is truncated mid-word in the file, leaving the trigger list incomplete; it is not 3 because trigger guidance is explicitly present rather than merely implied.

4 / 5

Trigger Term Quality

Natural keywords users would say are present: "reproducibility", "replication", "pre-registration", "FAIR data", "code sharing", "manuscript", "Methods". Not 5 because the truncated trigger clause ("trigger when preparing a manuscript, reviewing methodological comple...") cuts off mid-word, losing additional trigger conditions and common phrasings like "methods section" or "peer review"; not 3 because coverage goes well beyond domain jargon with several natural user terms.

4 / 5

Distinctiveness Conflict Risk

The research-reproducibility niche ("Methods completeness", "pre-registration", "FAIR data", "replication design") is distinct with clearly differentiated triggers. Not 5 because the "manuscript" trigger creates minor overlap risk with manuscript-writing/peer-review skills; not 3 because the domain is far more specific than a generic document- or code-handling skill.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/reproducibility-check/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.