CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

result-reliability-checker

Assesses whether study results are trustworthy by auditing design integrity, sample structure, statistical handling, bias control, validation chain, and claim discipline. It identifies where results are robust, fragile, overfit, under-validated, or overclaimed. Always separate reported findings from reliability judgment. Never fabricate references, PMIDs, DOIs, trial identifiers, study features, or validation claims.

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 ./awesome-med-research-skills/Evidence Insight/result-reliability-checker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A well-structured, highly actionable audit workflow with excellent progressive disclosure into a genuine one-level-deep bundle. Its main weakness is redundancy — the same do's and don'ts are repeated across four sections — which inflates token cost without adding guidance, and the workflow lacks an explicit feedback loop after the final self-check.

Suggestions

Consolidate the overlapping directive sections ('Core Function' should-not list, 'Hard Rules', 'What This Skill Should Not Do', 'Quality Standard') into a single rules section to remove triple- and quadruple-stated anti-patterns.

Add a feedback loop after Step 8: if the self-critical check exposes a missed fragility or unsupported judgment, revisit the relevant earlier step before finalizing.

Include one brief worked example (claim → evidence chain → judgment) in the body or a reference to anchor the interpretive steps that currently rely on judgment alone.

DimensionReasoningScore

Conciseness

The body is composed of dense, directive instructions with no explanation of concepts Claude already knows, but the same anti-patterns are stated three to four times across 'Core Function', 'Hard Rules', 'What This Skill Should Not Do', and 'Quality Standard' (e.g. 'do not treat high performance metrics as reliability by default' / 'Do not equate high AUROC / C-index / accuracy with robustness'), and the skill's purpose is restated in four sections. This is 'mostly efficient but could be tightened' rather than 2, since the padding is structural duplication of directives, not padded explanation; it is not 4 because the redundant sections are a real, multi-section trimming opportunity.

3 / 5

Actionability

The body gives concrete, executable audit guidance: 8 ordered steps with specific per-step checklists ('events-per-variable', 'calibration vs discrimination', 'multiple testing handling'), a mandatory A–I output structure, a verified table format in the reference module, a ready-to-use out-of-scope redirect template with a [restatement] placeholder, and concrete example inputs and sample triggers. It falls just short of 5 because several directives remain interpretive ('what the paper is asking the reader to believe', 'most likely hidden fragility') without worked examples, and the judgment-level definitions are delegated to a reference file.

4 / 5

Workflow Clarity

The 'Execution — 8 Steps (always run in order)' provides an explicit sequence with real checkpoints: gating ('Do not evaluate reliability before the claim-to-evidence chain is explicit'), per-step reference dispatch ('Apply references/design-and-bias-rules.md'), and a step-8 self-critical final check. It is not 5 because there is no feedback loop — nothing instructs revisiting an earlier step if the final check exposes a missed fragility — and the step-8 check is a one-pass review rather than an explicit validate-and-recover cycle.

4 / 5

Progressive Disclosure

The body acts as a clear orchestration overview: all seven referenced files exist in references/, each is listed in 'Reference Module Integration' with a one-line purpose ('Use for the core audit dimensions...', 'Use when checking design fit...'), each is dispatched at a defined execution step, and the references are exactly one level deep (none of them point onward). Content is appropriately split — frameworks, rule detail, and output guidance live in the bundle while the body holds sequencing and orchestration.

5 / 5

Total

16

/

20

Passed

Description

71%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 specific, well-scoped description with concrete audit actions and natural domain keywords, held back mainly by the complete absence of a 'Use when...' trigger clause. Adding explicit trigger guidance with common synonyms would lift both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks whether a paper's or study's results are reliable, trustworthy, robust, overclaimed, or safe to cite — or mentions overfitting, weak validation, small-sample risk, or conclusion overreach.'

Include natural user-side synonyms such as 'reliable', 'paper', 'audit', 'evidence', and 'cite' alongside the current technical vocabulary ('robust', 'fragile', 'overfit') to broaden trigger-term coverage.

Consider naming the input the skill expects (a paper/abstract with methods and results) so the 'what' also implies when the skill applies.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'auditing design integrity, sample structure, statistical handling, bias control, validation chain, and claim discipline' and 'identifies where results are robust, fragile, overfit, under-validated, or overclaimed' — giving comprehensive coverage of the audit domain in third-person voice. It matches the top anchor rather than 4 because coverage spans six distinct audit dimensions plus failure modes and integrity constraints, not just several actions with gaps.

5 / 5

Completeness

The 'what' is explicit and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not 4 because 'when' is not merely implicit-specific — it is entirely absent; it is not 2 because the 'what' half is concrete and multi-part.

3 / 5

Trigger Term Quality

Strong natural keywords are present ('trustworthy', 'robust', 'fragile', 'overfit', 'under-validated', 'overclaimed', 'references, PMIDs, DOIs, trial identifiers'), but common variations users would actually say — 'reliable', 'paper', 'audit', 'evidence', 'cite' — are missing. This fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive-synonym anchor at 5, and exceeds anchor 3 because the present terms are natural and domain-specific rather than generic.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche ('Assesses whether study results are trustworthy') distinct from summarization or clinical-decision skills, with minimal overlap risk. It is not 5 because sibling critical-appraisal / risk-of-bias / paper-review skills could plausibly compete for the same natural queries; it is not 3 because the scope is sharply framed around result trustworthiness rather than broadly 'works with documents'.

4 / 5

Total

16

/

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

awesome-med-research-skills/Evidence Insight/result-reliability-checker/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.