CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prospero-registration-helper

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

Quality

76%

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/prospero-registration-helper/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.

The core Workflow and Quality Rules sections are genuinely actionable and well-anchored to real bundle files, but roughly a third of the body is template filler (Key Features, Implementation Details, parts of When to Use) that restates the description and pads token cost. Cleaning out the boilerplate and fixing the broken cross-reference would lift this materially.

Suggestions

Delete or drastically trim the 'Key Features', 'Dependencies', and 'Implementation Details' sections and the last four bullets of 'When to Use': they restate the description verbatim or offer non-triggers ('Use this skill when scripts/date_utils.py is the most direct path'), and the 'Implementation Details' opener 'See `## Workflow` above' points to a section that appears below it.

Replace the Example Usage build-artifact path ('cd "20260316/scientific-skills/Protocol Design/..."') with a path-agnostic invocation, and add a short sample of the script's date output so users can verify the run.

Add an explicit final validation step to the Workflow (e.g., 'Step 4: Verify all `{}` placeholders are preserved and all `<>` placeholders are filled') so the Quality Rules requirement acts as a checkpoint rather than side documentation.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded sections: 'Key Features' restates the description verbatim ('Scope-focused workflow aligned to: Assists researchers in generating...'), the first 'When to Use' bullet is a garbled restatement ('when you need assists researchers in generating prospero registration content...'), and 'Implementation Details' opens with a broken pointer ('See `## Workflow` above' when Workflow is below) followed by generic filler. The padding occupies entire sections rather than being occasional over-explanation, so it sits below the 3 anchor; the lean, genuinely instructive Workflow and Quality Rules sections keep it above a 1.

2 / 5

Actionability

Mostly executable guidance: concrete commands (`python scripts/date_utils.py`, the py_compile check) and workflow steps naming specific prompt sections ('Review Title and Basic Details', 'Eligibility Criteria', 'Timeline and Methods') that all exist in references/prompt_templates.md. Falls short of 5 because the Example Usage cd path ('20260316/scientific-skills/Protocol Design/...') is a build artifact users won't have and no sample output is shown.

4 / 5

Workflow Clarity

Clear 3-step sequence (Analyze Input, Calculate Timeline, Generate Content) with sub-steps, a real script for dates, and missing-input/out-of-scope handling in the Error Handling and Input Validation sections. Not 5 because no post-generation validation checkpoint is embedded in the workflow itself (e.g., verifying `{}` placeholders survived is stated in Quality Rules but not as a step); not 3 because checkpoints are largely present across the workflow and error-handling sections.

4 / 5

Progressive Disclosure

Good structure against the actual bundle: the heavy content (prompt templates) correctly lives in references/prompt_templates.md, one level deep, with section names matching those cited in the body, and scripts/date_utils.py exists. Falls short of 5 because navigation is diluted by generic filler bullets ('Reference material available in `references/` for task-specific guidance') and the broken 'See `## Workflow` above' self-reference.

4 / 5

Total

14

/

20

Passed

Description

82%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 strong description that clearly and explicitly states both the capability and when to use it, in third person, with a distinct niche trigger. The main gap is keyword breadth: it misses natural synonyms like 'systematic review registration' or 'preregister', and it could enumerate more concrete actions (PICO, eligibility criteria, timeline).

DimensionReasoningScore

Specificity

Names the domain ('PROSPERO registration content for meta-analyses') and 1-2 concrete actions ('generating... from a title and optional protocol'), but does not list several specific actions such as PICO extraction, eligibility criteria, or timeline generation that would warrant a 4.

3 / 5

Completeness

Explicitly answers both what ('Assists researchers in generating PROSPERO registration content for meta-analyses from a title and optional protocol') and when ('Use when the user wants to draft a PROSPERO registration form') with concrete trigger phrases, matching the 5 anchor; the when-clause is specific, not merely present.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('PROSPERO', 'registration', 'meta-analyses', 'draft a PROSPERO registration form'), but misses common synonyms a user would naturally say, such as 'systematic review registration' or 'preregister', so it falls short of the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (PROSPERO registration for meta-analyses) with a distinct trigger term unlikely to collide with other skills; no overlap territory is implicated, matching the 5 anchor for minimal conflict risk.

5 / 5

Total

17

/

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/prospero-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.