CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ib-summarizer

Summarize core safety information from Investigator's Brochures for clinical.

Quality

60%

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/Evidence Insight/ib-summarizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 actionable material — real commands, a parameter table, example runs, and concrete output templates — but it is buried in a large amount of generated boilerplate with duplicated sections, generic risk/security/lifecycle filler, and a stale date. Organization and reference usage are mediocre: much of the inline detail belongs in reference files.

Suggestions

Cut the template filler — duplicated 'Description'/'Usage'/'Workflow' sections, Risk Assessment, Security Checklist, Lifecycle Status (with its stale 2026-03-06 date), Evaluation Criteria, and the 'See ## Usage/## Workflow above' cross-reference sections — to roughly halve the body.

Move the full markdown/JSON output templates and the parameter table into a reference file (e.g., references/output-formats.md) and link to it from a short 'Usage' section, keeping SKILL.md as an overview.

Fix the concrete gaps: either ship the referenced requirements.txt or remove the 'pip install -r requirements.txt' instructions, and replace the hardcoded 'cd "20260318/scientific-skills/..."' path with a portable relative path.

DimensionReasoningScore

Conciseness

The ~300-line body is noticeably verbose with several padded, template-generated sections: duplicated content ('Description', 'Usage', 'Workflow' appear twice; 'Example Usage' and 'Implementation Details' say 'See ## Usage/## Workflow above'), boilerplate risk-assessment and security-checklist tables, generic 'Lifecycle Status' with a stale date ('Next Review Date: 2026-03-06'), and empty 'Evaluation Criteria' checklists. This matches 'Noticeably verbose; several unnecessary explanations or padded sections' rather than level 3, where padding would be occasional.

2 / 5

Actionability

Concrete, executable guidance dominates: 'python -m py_compile scripts/main.py', 'python scripts/main.py --help', a full parameter table, real example invocations, and concrete output templates. Minor gaps keep it below 5: the 'Installation' section references a requirements.txt that does not exist in the bundle, and 'Example Usage' hardcodes a non-portable path ('cd "20260318/scientific-skills/Evidence Insight/ib-summarizer"').

4 / 5

Workflow Clarity

The 'Workflow' section lists a five-step sequence (confirm inputs, validate scope, run script, return structured result, fallback), but the checkpoints are generic template language rather than concrete validations tied to the script, and validation of the actual output is only implied via the 'Quick Check' compile step. This fits 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit' rather than level 4's 'clear sequence with most checkpoints present'.

3 / 5

Progressive Disclosure

The bundle is real and one level deep (references/audit-reference.md exists and is clearly linked from a References section; scripts/main.py exists), but the SKILL.md inlines substantial content that belongs in separate files — full markdown/JSON output templates, the parameter table, risk and security tables — and only one reference file is offered. This matches 'Some structure but could be better organized... content that should be separate is inline' rather than level 4, where most content would be appropriately placed.

3 / 5

Total

12

/

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 communicates a clear what for a distinct niche but is underdeveloped: it lacks any when-to-use trigger clause, omits natural synonyms like 'IB' or 'CSI', and the truncated ending ('for clinical.') suggests careless generation. It sits at the midpoint of the scale.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user mentions Investigator's Brochures, IBs, core safety information (CSI), or clinical trial safety documents.'

Include natural synonyms and extensions users would say: 'IB', 'CSI', 'clinical trial', '.pdf', '.docx'.

Either complete the truncated phrase 'for clinical.' (e.g., 'for clinical researchers') or remove it, and list the concrete extraction targets (ADRs, contraindications, warnings, interactions) to raise specificity.

DimensionReasoningScore

Specificity

The description names the domain ('Investigator's Brochures') and one concrete action ('Summarize core safety information'), but coverage is not comprehensive and the sentence is truncated ('for clinical.'). It fits the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than level 4, which requires several specific actions (e.g., extracting ADRs, contraindications, interactions).

3 / 5

Completeness

The 'what' is clear ('Summarize core safety information from Investigator's Brochures') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not level 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant keywords like 'Investigator's Brochures', 'core safety information', and 'clinical' are present, but common variations users would naturally say are missing: the abbreviation 'IB', 'CSI', 'clinical trial', 'drug safety', and file extensions like .pdf/.docx. This matches 'Some relevant keywords but missing common variations or synonyms' rather than level 4's 'a few natural terms missing'.

3 / 5

Distinctiveness Conflict Risk

Investigator's Brochures are a specific clinical-trial document type, giving the skill a clear niche with minimal conflict risk against generic document skills. It is not level 5 only because 'for clinical.' is vague and other medical-document summarizer skills could overlap slightly.

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

scientific-skills/Evidence Insight/ib-summarizer/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.