CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

claim-strength-calibrator

Calibrates manuscript claim strength so wording matches the actual evidence level, study design, and validation status.

Quality

67%

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/claim-strength-calibrator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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 body delivers genuinely strong workflow design: a sequenced 9-step process, explicit input validation with a feedback loop, and a mandatory structured output template that functions as a checklist. Its main weakness is severe redundancy — the clarify-first rule, evidence-level taxonomy, overclaim patterns, and hard rules each appear three to four times, including near-verbatim duplication of references/hard-rules.md — which inflates token cost without adding guidance value.

Suggestions

Remove the inline "Hard Rules" section (10 items) — it restates references/hard-rules.md almost verbatim; keep a one-line pointer plus the 2-3 rules that must be enforced before any output is produced.

Merge the overlapping framing sections — "Task", "Core Function", "Scope Boundary", "What This Skill Should Not Do", and "Quality Standard" each restate the same scope and failure modes — into a single compact purpose-and-boundaries section.

State the evidence-level taxonomy and overclaim-pattern taxonomy once (in the existing reference files or once in the body) and drop the duplicated lists in "Important Distinctions", Step 3, and Step 4.

Add one worked before/after example — an inflated claim paired with its evidence-anchored rewrite — to make the calibration guidance concrete for the most common case.

DimensionReasoningScore

Conciseness

The same instructions repeat many times across sections: the clarify-first rule appears in Reference Module Integration, Input Validation, Step 1, Hard Rule 10, and output section H; the evidence-level taxonomy appears in Task, Important Distinctions, Step 3, and again in references/evidence-level-mapping-rules.md; "Core Function" restates "Task"; and the 10-item "Hard Rules" section restates references/hard-rules.md nearly verbatim. This matches anchor 2 (noticeably verbose, several padded sections) rather than 3, since the redundancy is pervasive rather than a few spots that could be tightened.

2 / 5

Actionability

For an instruction-only skill, the guidance is concrete and executable: a 9-step procedure, a defined evidence-level taxonomy, named overclaim patterns, severity classes, 10 hard rules, and a mandatory A-H output structure. It falls short of anchor 5 only because there is no worked example (an inflated claim rewritten into calibrated wording) covering the common cases.

4 / 5

Workflow Clarity

The Execution section gives a clear numbered 9-step sequence with an explicit input-sufficiency validation checkpoint (Step 1 plus output section A "Input Match Check"), a genuine feedback loop (ask for missing manuscript/study context before producing a full review, echoed in section H), and a checklist via the mandatory A-H output structure. This matches anchor 5 (explicit validation steps, feedback loops, checklists); the workflow is not a destructive or batch operation, so no validation cap applies.

5 / 5

Progressive Disclosure

All 7 referenced files exist, are one level deep, and each is annotated in the body with when and how to use it — references are clearly signaled, not buried. However, the body inlines substantial content that duplicates the reference files (hard rules, evidence levels, overclaim patterns, severity classes), which is a real organization gap; this fits anchor 4 (good structure, most content appropriately placed, minor gaps) rather than 5.

4 / 5

Total

15

/

20

Passed

Description

53%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 is clear and appropriately concise, with a well-scoped single action tied to concrete calibration criteria (evidence level, study design, validation status). Its main weakness is the complete absence of trigger guidance — no "Use when..." clause and none of the natural user phrasings like "overstated" or "overclaiming" — which caps completeness and trigger quality at 3.

Suggestions

Add a use-when clause naming concrete triggers, e.g. "Use when the user asks whether claims are overstated, wants to tone down an abstract or discussion, or is responding to reviewer criticism about overclaiming."

Include the natural trigger words users would say — "overstated", "overclaiming", "tone down claims", "hedging" — alongside "claim strength" and "wording".

List the concrete actions the skill performs (identify overclaim patterns, map each claim to its evidence level, propose rewritten bounded wording, classify severity) instead of the single verb "calibrates".

DimensionReasoningScore

Specificity

"Calibrates manuscript claim strength so wording matches the actual evidence level, study design, and validation status" names the domain and a single concrete action with its calibration criteria, but does not list several actions (e.g., identify overclaims, map to evidence levels, propose rewrites). This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, which requires several specific listed actions.

3 / 5

Completeness

The description has a clear "what" (calibrates claim-strength wording against evidence level, study design, validation status) but no "Use when..." clause or equivalent explicit trigger guidance. Per the judging guidelines, a missing use-when clause caps completeness at 3; it cannot be 4 because the "when" is not present even weakly.

3 / 5

Trigger Term Quality

Relevant domain keywords are present ("manuscript", "claim strength", "wording", "evidence level", "study design"), but the natural phrases a user would actually say for this task — "overstated", "overclaiming", "tone down", "hedging", "abstract", "discussion" — are absent. This is anchor 3 (some relevant keywords, missing common variations or synonyms), not 4, since the most likely trigger words are missing entirely rather than just a few.

3 / 5

Distinctiveness Conflict Risk

"Calibrates manuscript claim strength" carves a fairly distinct biomedical-manuscript-editing niche, but without explicit triggers it retains minor overlap risk with generic scientific tone-editing or peer-review skills. This matches anchor 4 (mostly distinct, minor overlap with closely related skills) rather than 5 (clear niche with distinct triggers), which requires trigger phrases the description lacks.

4 / 5

Total

13

/

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/claim-strength-calibrator/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.