CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-to-claim-verifier

Verifies whether a scientific or biomedical claim is actually supported by the cited original papers rather than by citation drift, overstatement, selective citation, or correlation-to-causation inflation. Use this skill whenever a user wants to check whether a repeated statement, slide claim, manuscript sentence, review assertion, or “people often say” scientific conclusion is truly supported by the underlying primary literature. Always separate the claim itself, the cited paper(s), what the paper actually showed, what it did not show, and whether later retellings drifted beyond the original evidence. Never fabricate references, findings, study features, or citation chains.

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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-architected verification workflow: the ordered steps, mandatory output structure, and cleanly signaled one-level-deep references make it highly actionable and easy to navigate. The dominant weakness is redundancy — trigger examples triplicated, Core Function duplicating the execution steps, and three overlapping rule sections — which inflates token cost without adding guidance.

Suggestions

Collapse the three example lists (intro statements, Input Validation examples, Sample Triggers) into a single trigger section — they repeat the same user phrasings.

Remove the 'Core Function' section (it restates the 8-step execution almost one-to-one) and merge 'Hard Rules', 'What This Skill Should Not Do', and 'Quality Standard' into one non-overlapping rules section, cutting roughly a third of the body.

Add one worked example of a filled A–J output for a sample claim to make the mandatory output structure fully concrete.

DimensionReasoningScore

Conciseness

Noticeably verbose through structural duplication: the same user-phrasing examples appear three times ("This skill is for users who want to check statements such as", Input Validation "Examples", and "Sample Triggers"); "Core Function" (10 items) restates the "Execution — 8 Steps" almost one-to-one; and "Hard Rules", "What This Skill Should Not Do", and "Quality Standard" overlap heavily (e.g., "Never fabricate references..." appears in rules and quality standard). This is beyond anchor 3's "could be tightened" — several padded/duplicated sections — but not anchor 1, since it never explains concepts Claude already knows.

2 / 5

Actionability

For an instruction-only skill the guidance is mostly executable: an exact ordered 8-step procedure with explicit decision categories, a mandatory A–J output structure specifying each section's contents, a copy-paste out-of-scope redirect template ("Your request ([restatement]) is outside that scope because it requires [...]"), and concrete support-level/mismatch taxonomies. It falls short of anchor 5 because there is no worked example of a filled A–J output and source tracing stays high-level ("trace further backward when possible").

4 / 5

Workflow Clarity

"Execution — 8 Steps (always run in order)" gives a clear sequence, each step with explicit decision categories, and the workflow includes validation checkpoints and error-recovery paths: an input-validation gate with a stop condition, a "Cannot be verified with the available source material" failure state, and a final audit requiring "explicitly mark any unresolved reference uncertainty". This matches anchor 5's explicit validation steps, feedback paths, and checklists; anchor 4 would require missing checkpoints, which are present.

5 / 5

Progressive Disclosure

Each of the nine reference modules is explicitly signaled with a use condition and destination ("references/claim-decomposition-rules.md → use when rewriting the target claim ... in Section A"). All nine files exist, contain real (non-stub) content, and contain no nested .md references — a clean one-level-deep structure matching anchor 5, exceeding anchor 4 whose references are only "mostly clear".

5 / 5

Total

16

/

20

Passed

Description

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

An excellent description: third-person voice, explicit what and when, rich trigger synonyms across statement/slide/manuscript/review contexts, and a clearly carved niche. Its only weakness is modest specificity — the verification and separation actions are named, but downstream workflow actions (mismatch classification, corrected claim output) are not surfaced.

DimensionReasoningScore

Specificity

Names several concrete actions: "Verifies whether a scientific or biomedical claim is actually supported by the cited original papers rather than by citation drift, overstatement, selective citation, or correlation-to-causation inflation" and "Always separate the claim itself, the cited paper(s), what the paper actually showed, what it did not show". It stops short of anchor 5 because workflow actions present in the body (source-chain tracing, mismatch classification, producing citation-safe corrected wording) are omitted, leaving minor coverage gaps; well above anchor 3's 1–2 actions.

4 / 5

Completeness

Clearly answers both questions: the "what" is explicit ("Verifies whether a scientific or biomedical claim is actually supported by the cited original papers...") and the "when" is explicit with concrete trigger phrases ("Use this skill whenever a user wants to check whether a repeated statement, slide claim, manuscript sentence, review assertion..."). This matches anchor 5 exactly; it is above anchor 4 because the trigger guidance is specific, not generic.

5 / 5

Trigger Term Quality

Comprehensive natural-language coverage with synonyms: "repeated statement, slide claim, manuscript sentence, review assertion, or ‘people often say’ scientific conclusion", plus failure-mode vocabulary users would name ("citation drift", "overstatement", "selective citation"). This matches anchor 5 rather than anchor 4 because both claim-side synonyms and mismatch-type phrasings a user would naturally say are present.

5 / 5

Distinctiveness Conflict Risk

Clear niche — claim-to-primary-source verification — with distinct triggers, explicitly framed against generic alternatives ("rather than by citation drift, overstatement, selective citation"). Unlike anchor 4's minor overlap with closely related skills, the verification-vs-summarization framing makes accidental triggering of a general literature-review or paper-summary skill unlikely.

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

awesome-med-research-skills/Evidence Insight/paper-to-claim-verifier/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.