CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

consistency-checker-across-manuscript

Checks consistency across title, abstract, methods, results, figures, tables, and supplements to identify internal contradictions and version drift in biomedical manuscripts.

Quality

69%

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/Academic Writing/consistency-checker-across-manuscript/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 instruction skill with a clear sequenced workflow, a mandatory output template, and genuinely useful one-level-deep reference files. Its main liability is heavy redundancy — at least four body sections restate content that already exists elsewhere in the body or in the references — which roughly doubles the token cost without adding guidance.

Suggestions

Delete or merge the redundant sections: "Hard Rules" vs references/hard-rules.md, "Core Function" vs "Task", and "What This Skill Should Not Do" vs "Scope Boundary" — keep one authoritative copy of each rule set.

Trim "Sample Triggers" and "Important Distinctions" or move them into the relevant reference files to cut the body's token footprint substantially.

Add one short worked example of a consistency finding rendered in the mandatory A–H output structure to make the template fully concrete.

DimensionReasoningScore

Conciseness

The body is noticeably padded through structural duplication: "Hard Rules" (10 rules) repeats almost verbatim in references/hard-rules.md and again in "What This Skill Should Not Do"; "Core Function" restates the earlier "Task" list; "Input Validation" and "Sample Triggers" duplicate Step 1 of Execution; and "Important Distinctions" overlaps the severity/drift reference rules. It avoids score 1 because it never explains domain concepts Claude already knows — the padding is redundancy, not basic-concept tutorials — but several sections could be deleted outright.

2 / 5

Actionability

For an instruction-only skill, the guidance is mostly concrete: an 8-step execution sequence, a mandatory output template with exact section headers (A–H), a named detection taxonomy ("sample-size inconsistencies, shifting endpoint wording, population-definition drift, figure/table numbering mismatch"), and explicit severity classes. It misses score 5 because no worked example of a finding in the required output format is provided, and the actual comparison criteria are deferred to the reference files.

4 / 5

Workflow Clarity

Steps 1–8 are clearly sequenced with an explicit input-sufficiency checkpoint ("If the user provides only a vague request... do not immediately produce a full review") reinforced by output section A ("Input Match Check") and section H (missing-input list). It falls short of score 5 because there is no verification/feedback loop on its own findings — no step instructing re-confirming each flagged numerical contradiction against both source sections before reporting it.

4 / 5

Progressive Disclosure

The "Reference Module Integration" section signals all eight one-level-deep reference files with paths and per-file use cases, and all cited paths exist in references/ with no nested references inside them. It misses score 5 because content is not cleanly split — the body's 10-line "Hard Rules" section fully duplicates references/hard-rules.md, creating ambiguity about which is authoritative, and paths are code-formatted rather than linked.

4 / 5

Total

14

/

20

Passed

Description

66%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, third-person description that clearly conveys the niche (cross-component consistency and version drift in biomedical manuscripts) with good natural keywords. Its main weakness is the complete absence of a 'Use when...' trigger clause, which caps completeness and leaves triggering to inference.

Suggestions

Append an explicit trigger clause, e.g. "Use when reviewing a biomedical manuscript before submission, cross-checking abstract vs. results, or checking for version drift after revision."

Add natural synonyms users would say, such as "cross-check", "discrepancies", or "alignment", to broaden trigger coverage.

Mention the key deliverable (severity-classified inconsistency findings and a correction-priority plan) to make the 'what' more comprehensive.

DimensionReasoningScore

Specificity

The description enumerates concrete comparison targets ("title, abstract, methods, results, figures, tables, and supplements") and two distinct detection actions ("identify internal contradictions and version drift"), which is noticeably more concrete than the score-3 anchor ('extracts content'). It falls short of score 5 because it omits actions the skill actually performs, such as severity classification and correction prioritization — minor gaps in coverage rather than comprehensive.

4 / 5

Completeness

The 'what' is clear ("Checks consistency across title, abstract, methods, results, figures, tables, and supplements to identify internal contradictions and version drift"), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description. Per the judging guideline, a missing 'Use when' clause caps completeness at 3; 'version drift' weakly implies a revision-stage trigger but that is inference, not explicit statement.

3 / 5

Trigger Term Quality

Good natural-keyword coverage: "consistency", "contradictions", "version drift", "biomedical manuscripts", plus all seven component names users would mention. Not score 5 because common synonyms users naturally say — "cross-check", "discrepancies", "alignment", "pre-submission check" — are absent; not score 3 because the terms present are natural and well-targeted rather than jargon-only.

4 / 5

Distinctiveness Conflict Risk

The biomedical-manuscript cross-component consistency niche is clear and the terms "internal contradictions and version drift" are distinctive. It sits at score 4 rather than 5 because "consistency" and "manuscripts" leave minor overlap risk with closely related skills (generic proofreading, peer-review, or manuscript-editing skills in the same collection), whereas score 5 requires minimal conflict risk with distinct triggers.

4 / 5

Total

15

/

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/Academic Writing/consistency-checker-across-manuscript/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.