CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reporting-guideline-compliance-checker

Checks biomedical manuscripts against reporting guidelines such as CONSORT, STROBE, PRISMA, and TRIPOD to identify missing or weak reporting elements before submission or revision.

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 ./awesome-med-research-skills/Academic Writing/reporting-guideline-compliance-checker/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 instructional skill with a clear sequenced workflow, concrete output template, and a properly wired reference bundle, but it is noticeably padded: the Task/Core Function lists are duplicates and the Hard Rules section reprints a reference file verbatim. Cutting the duplication would materially reduce token cost without losing any guidance.

Suggestions

Delete the 'Core Function' section (a near-duplicate of 'Task') and the 'What This Skill Should Not Do' section, whose points are already covered by 'Scope Boundary' and 'Hard Rules'.

Remove the inline 10-rule 'Hard Rules' section and keep only the pointer to references/hard-rules.md, which already contains the same rules.

Consolidate the repeated input-sufficiency guidance (Task item 6, 'Input Validation', Step 1, Output Section I, Hard Rule 10) into one canonical section.

DimensionReasoningScore

Conciseness

The body has substantial duplication: the 'Task' 7-point list and the 'Core Function' 7-point list are near-identical restatements; the 'Hard Rules' section (10 rules) is a near-verbatim duplicate of references/hard-rules.md; and the input-sufficiency point is repeated in 'Task', 'Input Validation', 'Step 1', 'Output Section I', and 'Hard Rule 10'. This matches 'noticeably verbose; several unnecessary explanations or padded sections' rather than 3, since the redundancy goes beyond occasional tightening.

2 / 5

Actionability

For an instruction-only skill the guidance is mostly concrete: an 8-step execution flow, explicit severity categories (major gap / moderate / minor / not applicable / unclear), named high-risk items (participant flow, eligibility, endpoint definition, bias handling), and a mandatory 9-section output template (A-I). Minor gaps keep it below 5: no worked example of a filled-out review, and steps like 'explain the compliance logic clearly' remain abstract. It clearly exceeds the pseudocode/incomplete level of 3.

4 / 5

Workflow Clarity

Steps 1-8 are clearly sequenced, with an explicit upfront validation checkpoint ('If these are not clear enough, do not jump into a full compliance assessment') and a recovery path (request missing materials), echoed by Output Section A. This is not a destructive/batch skill, so the workflow-cap rule does not apply. It falls short of 5 because mid-process verification (e.g., confirming the framework choice against hybrid rules before proceeding) is only delegated to reference files rather than being an explicit checkpoint in the sequence.

4 / 5

Progressive Disclosure

All seven referenced files exist, are clearly signaled with per-file usage instructions, and are one level deep — no nested references. However, the body inlines sizable content that duplicates the bundle (the full 10-rule Hard Rules section duplicates references/hard-rules.md; Steps 2 and 4 restate guideline-selection-rules.md and compliance-severity-rules.md), matching 'good structure; most content appropriately placed; minor organization gaps' rather than the clean split of a 5.

4 / 5

Total

14

/

20

Passed

Description

70%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, distinctive description with strong domain keywords, but it omits explicit trigger guidance (a 'Use when...' clause with concrete user phrases). Adding one would lift completeness from 3 to 4-5 without lengthening the description much.

Suggestions

Append an explicit trigger clause, e.g., 'Use when the user mentions CONSORT, STROBE, PRISMA, TRIPOD, reporting guidelines, or asks whether a manuscript is missing reporting items before submission.'

Include natural user phrasings like 'checklist compliance', 'reporting checklist', or 'will this get desk-rejected' to broaden trigger coverage.

Consider naming the deliverable (a structured compliance review with severity-ranked gaps) so the 'what' fully covers the skill's output.

DimensionReasoningScore

Specificity

The description names the domain ("biomedical manuscripts", "reporting guidelines such as CONSORT, STROBE, PRISMA, and TRIPOD") and concrete actions ("Checks... to identify missing or weak reporting elements before submission or revision"). It lists several specific capabilities with only minor coverage gaps (e.g., no mention of severity classification or revision-stage review), matching the 'several specific actions; minor gaps' anchor rather than the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

The 'what' is clear (checks manuscripts against named guidelines to identify missing/weak reporting elements), but there is no 'Use when...' clause or equivalent explicit trigger guidance — "before submission or revision" describes the manuscript lifecycle stage, not when to invoke the skill. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3, which matches 'clear what but when is missing or only weakly implied'.

3 / 5

Trigger Term Quality

Natural terms users would say are well covered: "CONSORT", "STROBE", "PRISMA", "TRIPOD", "reporting guidelines", "missing or weak reporting elements", "before submission or revision". A few common variations are absent ("checklist", "compliance", "reporting checklist", "desk rejection"), so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

This is a clear niche — reporting-guideline compliance checking for biomedical manuscripts — with distinct triggers in the four named frameworks (CONSORT, STROBE, PRISMA, TRIPOD). Minimal overlap risk with other writing/editing skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 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/Academic Writing/reporting-guideline-compliance-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.