CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inplasy-registration-helper

Assists researchers in generating INPLASY registration content for meta-analyses from a title and optional protocol. Use when the user wants to draft a INPLASY registration form.

Quality

62%

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/Protocol Design/INPLASY-registration-helper/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 core Workflow, Quality Rules, and bundle layout are sound, but roughly half the body is generated boilerplate padding, the heading says 'PROSPERO' while the skill is INPLASY, and there is no validation step. The real guidance that exists (script call, templates reference, placeholder rules) is actionable.

Suggestions

Delete the boilerplate sections ('When to Use' bullets 2–5, 'Key Features', 'Dependencies', 'Implementation Details') — they restate the description or point nowhere ('See `## Workflow` above'), and roughly halve the token cost.

Fix the naming mismatch: the title heading says 'PROSPERO Registration Helper' while the skill name, description, and templates are INPLASY — pick one registry and align all text.

Add an explicit validation step after content generation (e.g., 'Verify all `{}` placeholders are preserved, every `<>` field is filled, and output is in English before returning') and correct the mislabeled ```python block in Tools to a ```bash shell command.

DimensionReasoningScore

Conciseness

Several sections are boilerplate padding: 'When to Use' bullets 2–5 restate the description in broken grammar, 'Key Features' and 'Dependencies' restate the description or say nothing ('not explicitly version-pinned in this skill package'), and 'Implementation Details' contains filler like 'See `## Workflow` above for related details.' Roughly half the body adds no guidance, matching the 'several unnecessary explanations or padded sections' anchor; not a 3 because the padding is extensive rather than occasional.

2 / 5

Actionability

The workflow gives real, executable anchors ('Run `scripts/date_utils.py`', 'Use the prompts in `references/registration_templates.md`' — both files exist), but key details are missing: no guidance on assembling generated sections into the final form, the Tools section mislabels a shell command as a ```python block, and the example path '20260316/scientific-skills/Protocol Design/INPLASY-registration-helper' is arbitrary. Some concrete but incomplete guidance matches anchor 3; not 4 due to these gaps.

3 / 5

Workflow Clarity

The three-step sequence (Analyze Input → Calculate Timeline → Generate Content) is coherent and ordered, but there is no validation checkpoint — nothing tells the reader to verify that `{}` placeholders were preserved, `<>` fields filled, and output is English before delivering. Anchor 3 fits (steps listed, checkpoints missing); not 2 because the sequence is well-defined, not 4 because the Quality Rules are constraints with no verify step.

3 / 5

Progressive Disclosure

Bundle structure is appropriate: the templates are correctly split into references/registration_templates.md (one level deep, referenced from the workflow) and the script lives in scripts/date_utils.py, both real files. Minor gaps: the reference is only mentioned mid-workflow and generically ('references/ contains supporting rules, prompts, or checklists'), and boilerplate sections dilute navigation. Matches anchor 4; not 5 because references could be more clearly signaled with a dedicated section.

4 / 5

Total

12

/

20

Passed

Description

62%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 answers both what and when with a specific domain and third-person voice, but is thin on concrete capability coverage and natural trigger variations. The 'when' clause mirrors the 'what' instead of adding triggering situations.

Suggestions

Enumerate the concrete actions the skill performs, e.g., 'Generates the registration title, review question, eligibility criteria, search strategy, and timeline fields for an INPLASY form.'

Broaden trigger terms with natural user phrasings such as 'register a systematic review', 'INPLASY form', 'registration protocol', and 'draft registration fields'.

Make the 'Use when' clause situational rather than circular, e.g., 'Use when the user wants to register or pre-register a meta-analysis on INPLASY, or asks for help completing a registration form.'

DimensionReasoningScore

Specificity

Names the domain (INPLASY registration for meta-analyses) and one concrete action (generating registration content from a title and optional protocol), but does not enumerate several specific actions, matching the '1-2 concrete actions, not comprehensive' anchor. Not a 4 because no multiple distinct actions are listed; not a 2 because the action is specific rather than generic.

3 / 5

Completeness

Both 'what' ('Assists researchers in generating INPLASY registration content for meta-analyses from a title and optional protocol') and 'when' ('Use when the user wants to draft a INPLASY registration form') are present, but the 'when' clause is circular — it restates the 'what' rather than giving concrete trigger situations. Matches the anchor for both present but 'when' could be more explicit or specific; not a 5 for that reason.

4 / 5

Trigger Term Quality

'INPLASY', 'registration', 'meta-analyses', and 'protocol' are relevant keywords a user might say, but common variations and synonyms are missing (e.g., 'register a systematic review', 'registration form', 'systematic review protocol'). Fits the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

INPLASY is a specific registration platform, giving a clear niche with distinct triggers, but there is minor overlap risk with closely related systematic-review registration skills (e.g., PROSPERO — the body even titles itself 'PROSPERO Registration Helper'). Mostly distinct with minor overlap, matching anchor 4; not 5 due to that overlap and the single-registry scope being slightly blurred.

4 / 5

Total

14

/

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/Protocol Design/INPLASY-registration-helper/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.