CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-protocol-writer

Generates a PROSPERO-compliant Meta-analysis protocol based on Title and PICOS. Use when the user wants to write a protocol for a systematic review or meta-analysis.

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/meta-protocol-writer/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 (title validation, PICOS gathering, section generation via the referenced prompts, final assembly) is concrete and well-validated with appropriate offloading to `references/prompts.md`. However, the body is padded with templated filler sections — "When to Use", "Key Features", "Implementation Details" — that add tokens without actionable content and include one broken cross-reference, dragging down conciseness and slightly muddying navigation.

Suggestions

Delete or drastically trim the filler sections ("When to Use", "Key Features", "Implementation Details", "Input Validation") — most bullets are generic templated text; keep only the actual Workflow, Dependencies, and Error Handling content.

Fix the broken pointer "See `## Workflow` above for related details" (Workflow appears below that section) or remove the line entirely.

Make the final step verifiable: replace "Ensure all headings match the PROSPERO requirements" with the concrete heading list or a pointer to where it is defined, and add a check that the word-count constraints (Rationale 5-150, Objectives 10-200) were met.

DimensionReasoningScore

Conciseness

Noticeably verbose: several padded sections add little value — the templated "When to Use" bullets ("needs a packaged method instead of ad-hoc freeform output"), the generic "Key Features" list, and an "Implementation Details" section that mostly repeats other sections and contains a broken pointer ("See `## Workflow` above" when Workflow appears below). These dilute an otherwise tight core workflow, matching the anchor for several unnecessary padded sections.

2 / 5

Actionability

The Workflow section gives mostly executable guidance: explicit title validation rules with word limit (< 25 words), PICOS gathering, word-count constraints ("Rationale (5-150 words), Objectives (10-200 words)"), runnable commands, and correct pointers to the real prompts in `references/prompts.md`. Minor gaps remain, e.g., "Ensure all headings match the PROSPERO requirements" without stating what those are or where to find them.

4 / 5

Workflow Clarity

The four-step workflow is clearly sequenced with real validation checkpoints — title validation with an explicit retry loop ("If the title fails validation, explain why and ask for a revised title") and missing-PICOS handling. It falls short of a 5 because there is no post-generation verification step (e.g., checking the enforced word counts) and the final "ensure headings match" instruction lacks a concrete check.

4 / 5

Progressive Disclosure

Good structure: the detailed prompts are correctly split into `references/prompts.md` (verified to contain the three referenced prompts) and referenced one level deep with clear signaling ("Use the prompts in `references/prompts.md`"), and `scripts/utils.py` exists as referenced. Minor gaps: the generic "Reference material available in `references/`" filler bullet and the broken "See `## Workflow` above" self-reference slightly impair navigation, keeping it below the clean anchor-5 structure.

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: it clearly and explicitly states what the skill does and when to use it, with distinctive domain terminology (PROSPERO, PICOS) that minimizes trigger conflicts. The only weaknesses are limited action coverage (just "generates") and a few missing natural synonyms such as registration-related terms.

Suggestions

Add one or two more concrete actions (e.g., validates the title against PROSPERO requirements, drafts the Methods search strategy) to lift specificity beyond a single verb.

Include commonly used variations such as "register a review", "review protocol", or "PRISMA" in the when-clause to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — "Generates a PROSPERO-compliant Meta-analysis protocol based on Title and PICOS" — which matches the anchor for 1-2 concrete actions without comprehensive coverage; it does not list several distinct actions that would warrant a 4.

3 / 5

Completeness

It explicitly answers both what ("Generates a PROSPERO-compliant Meta-analysis protocol based on Title and PICOS") and when ("Use when the user wants to write a protocol for a systematic review or meta-analysis") with concrete trigger phrases, matching the top anchor; not a 4 because the when-clause is as explicit and specific as the anchor-5 example.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("write a protocol", "systematic review", "meta-analysis", "PROSPERO", "PICOS") that users would plausibly say, but common variations like "register/registration", "review protocol", or "PRISMA" are missing, so it falls just short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Terms like "PROSPERO-compliant", "Meta-analysis protocol", and "PICOS" carve a clear niche with distinct triggers and minimal conflict risk with other skills, matching the anchor-5 example's specificity.

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/meta-protocol-writer/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.