CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rct-bias-assessment-rob

Automates Risk of Bias 2 (ROB2) assessment for RCT papers by analyzing text against specific domains and synthesizing a report. Use when you need to assess the quality of a clinical trial paper or evaluate risk of bias.

Quality

65%

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 ./scientific-skills/Data Analysis/rct-bias-assessment-rob2/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 contains a workable ROB2 workflow with a proper one-level reference file and real scripts, but it is padded with auto-generated boilerplate sections, presents four overlapping run descriptions, and includes command examples that do not execute as written. It reads as an unedited generated skill rather than a curated one.

Suggestions

Remove the boilerplate sections (Key Features, Dependencies, Implementation Details) and the near-verbatim restatement of the description in 'When to Use'; they consume tokens without adding actionable guidance.

Fix the executable examples: `scripts/assess_rob2.py` has no CLI so `--help` fails, and `python extract_pdf.py` needs the PDF path argument and the `scripts/` prefix — show the actual invocations from the script's own docstring.

Consolidate the four overlapping run descriptions (## Usage, ### Workflow Steps, Example run plan, Usage flow) into one sequenced workflow, and correct the 'See `## Usage` above' cross-reference, which points to a section that appears later.

DimensionReasoningScore

Conciseness

Several padded boilerplate sections ("Scope-focused workflow aligned to:", "Structured execution path designed to keep outputs consistent and reviewable", "Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable") plus a When to Use section restating the description nearly verbatim with garbled grammar ("use when you need automates risk of bias 2 (rob2) assessment..."). This matches anchor 2's several unnecessary/padded sections rather than anchor 3's occasional tightening needs.

2 / 5

Actionability

There is concrete guidance (the JSON output schema, the `from scripts.assess_rob2 import clean_text` example), but commands are broken as written: `python scripts/assess_rob2.py --help` fails because the script defines functions with no CLI, `python extract_pdf.py` omits the required PDF-path argument and its `scripts/` location, and "See `## Usage` above" points to a section that appears later in the document. The gaps exceed anchor 4's 'minor gaps'.

3 / 5

Workflow Clarity

A clear sequence exists (Extract Study Info → Assess Domains → Synthesize, and the PDF extract → read → assess flow), but validation checkpoints are absent or implicit and four overlapping run descriptions (## Usage, ### Workflow Steps, Example run plan, Usage flow) blur which is canonical — matching anchor 3's 'steps listed but checkpoints missing'.

3 / 5

Progressive Disclosure

The one-level reference is clearly signaled ("Refer to [rob2_guidelines.md](references/rob2_guidelines.md) for the detailed questions and logic for each domain" — verified to exist) and the two scripts are real and referenced. Minor gaps: domain synthesis rules are duplicated inline from the reference, and `extract_pdf.py` is referenced without its `scripts/` path, so it falls just short of anchor 5.

4 / 5

Total

12

/

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.

The description clearly states what the skill does and when to use it, with relevant domain keywords and third-person voice. Its main weaknesses are the un-enumerated 'specific domains' and a somewhat generic when-clause that could overlap with general trial-quality requests.

DimensionReasoningScore

Specificity

Names the domain (ROB2 assessment for RCT papers) and two concrete actions ("analyzing text against specific domains", "synthesizing a report"), but the domains are not enumerated and coverage is not comprehensive, matching anchor 3 rather than 4.

3 / 5

Completeness

Has a clear 'what' (automates ROB2 assessment by analyzing domains and synthesizing a report) plus an explicit 'Use when...' clause; the when-clause ('assess the quality of a clinical trial paper') is somewhat generic, keeping it below anchor 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage ("risk of bias", "clinical trial paper", "quality", ROB2, RCT), but misses common variations like "critical appraisal" or "study quality", so it falls short of the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (ROB2 for RCT papers) with distinct triggers, but the broad phrase 'assess the quality of a clinical trial paper' could overlap with general paper-review skills, giving minor conflict risk typical of anchor 4.

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

scientific-skills/Data Analysis/rct-bias-assessment-rob2/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.