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

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

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 skill has a clear, actionable workflow and well-structured one-level-deep references, but a large fraction of the body is generic boilerplate (templated 'When to Use', 'Key Features', 'Implementation Details', a leaked example path) that pads the token budget without adding skill-specific value.

Suggestions

Remove or radically trim the boilerplate 'When to Use', 'Key Features', and 'Implementation Details' sections that restate the description and generic process language; keep only skill-specific guidance.

Fix the broken 'When to Use' bullet ('you need assists researchers in generating prospero registration content...') and drop the generic bullets about date_utils.py being 'the most direct path'.

Replace the leaked dated path in 'Example Usage' ('20260316/scientific-skills/Protocol Design/...') with a clean, current invocation example.

Embed an explicit input-validation checkpoint at the start of the Workflow (validate title/protocol present and in scope before proceeding) rather than relegating it to a separate section.

Dimension	Reasoning	Score
Conciseness	Several sections are padded boilerplate that add little: 'When to Use' restates the description (one bullet even contains a grammar error, 'you need assists'), 'Key Features' and 'Implementation Details' restate generic process language, and 'Example Usage' leaks a dated path ('20260316/scientific-skills/...'). This matches anchor 2 (noticeably verbose; several unnecessary padded sections) rather than 3 because the filler is substantial relative to the genuinely useful Workflow/Quality Rules content.	2 / 5
Actionability	Concrete executable commands are present ('python scripts/date_utils.py', 'python -m py_compile scripts/date_utils.py') and the workflow points to specific named prompt templates in references/prompt_templates.md (Steps 3.1/3.2/3.3). It is below 5 because the core generation work is delegated to the reference rather than given inline.	4 / 5
Workflow Clarity	The Workflow is a clear numbered sequence (Analyze Input -> Calculate Timeline -> Generate Content with sub-steps 3.1-3.3) and an Input Validation scope-gate is documented. It is not 5 because validation is a separate section rather than an explicit validate-then-proceed checkpoint embedded in the workflow, and not 3 because the sequence and scope gate are clearly present.	4 / 5
Progressive Disclosure	The body acts as an overview and correctly delegates the bulk of detail one level deep to references/prompt_templates.md and scripts/date_utils.py, both real files that are clearly signaled. It is below 5 because the body itself is cluttered with boilerplate sections that slightly obscure navigation.	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.

The description is clear, third-person, and explicitly covers both what the skill does and when to use it, with a distinct niche trigger. Its only weakness is that it describes one workflow rather than enumerating several distinct concrete actions.

Dimension	Reasoning	Score
Specificity	Names the PROSPERO/meta-analysis domain plus one-to-two concrete actions ('generating PROSPERO registration content', 'draft a PROSPERO registration form'), but does not list several distinct actions. It fits anchor 3 rather than 4 because the actions are restatements of one workflow rather than a comprehensive action list.	3 / 5
Completeness	It 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 a concrete trigger phrase.	5 / 5
Trigger Term Quality	Natural niche phrases users would say are present ('PROSPERO registration', 'meta-analyses', 'draft a PROSPERO registration form'), giving good keyword coverage. It is below 5 because there are no synonyms or file-extension variants, and above 3 because the coverage is solid within this specific niche.	4 / 5
Distinctiveness Conflict Risk	PROSPERO registration for meta-analyses is a narrow, well-defined niche with distinct triggers, so conflict with other skills is minimal.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 63c61d3

Reviewed: 8 hours ago

Table of Contents

Discovery Implementation Validation

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.