CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-manuscript-generator

Generates a first draft of a clinical meta-analysis paper. Input the research report (including Methods and Results sections), language, and title to automatically generate a complete paper draft including Abstract, Introduction, Discussion, and other sections, with automatic ...

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/meta-manuscript-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 a genuinely actionable, well-sequenced workflow with concrete code examples, word budgets, and citation handling — stronger than typical instruction-only skills. Its weaknesses are padded boilerplate sections, end-only validation for a batch retrieval pipeline, and a broken reference link to the writing guide.

Suggestions

Fix the broken reference: the body links references/writing-guide.md but the bundle file is references/writing-guide-en.md — update the link (and consider also shipping a Chinese variant if 'Chinese or English' output is supported).

Trim the 'When to Use', 'Key Features', and 'Implementation Details' sections — they restate the description or state generic packaging boilerplate; consolidate into 2–3 trigger bullets.

Add per-stage validation checkpoints for the batch PubMed retrieval (e.g., verify PMID lists are non-empty and from the last 5 years before writing sections that depend on them), rather than validating only via the final checklist.

Fix the fenced-code boundary: '## Input Validation' and '## References' currently render inside the 'Final Output Format' code block, confusing document structure with manuscript template.

DimensionReasoningScore

Conciseness

The core workflow content (phases, word counts, citation formats) is dense and useful, but the 'When to Use' section repeats the frontmatter description almost verbatim, and 'Key Features'/'Implementation Details' are boilerplate filler ('See `## Workflow` above for related details.'). Not 2 because the majority of sections carry real task-specific weight.

3 / 5

Actionability

Provides executable import-and-call examples for both scripts, the PubMed E-utilities base URL, per-keyword article counts (15/10/5), the `[PMID: xxx]` -> `[[n]](link)` pipeline, and exact AMA citation format. Not 5 because minor gaps remain (no CLI example for search_references.py, `new_references=""` semantics undocumented).

4 / 5

Workflow Clarity

Five clearly sequenced stages (parse -> retrieve -> write -> insert refs -> integrate) plus a Quality Checklist and an Error Handling section with feedback guidance. Not 5 because validation is end-of-pipeline only — there are no per-stage checkpoints for the batch PubMed retrieval (e.g., verifying PMIDs were retrieved before writing sections that must cite them).

4 / 5

Progressive Disclosure

Sectioning is good and both referenced scripts exist, but the only reference link in the body — 'Detailed guidelines are available in [references/writing-guide.md](references/writing-guide.md)' — points to a file that does not exist (the actual bundle file is references/writing-guide-en.md), so the sole navigation path to detailed guidance is broken. Not 4 because a broken primary reference is more than a minor organization gap.

3 / 5

Total

14

/

20

Passed

Description

58%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 concrete, well-scoped capability with clear inputs and outputs, but it is literally truncated mid-sentence ('with automatic ...'), which cuts off its trigger terms, and it lacks any 'Use when...' guidance. Fixing the truncation and adding explicit trigger conditions would raise it substantially.

Suggestions

Restore the truncated tail of the description — it currently ends 'with automatic ...', cutting off what was clearly going to mention PubMed reference retrieval and systematic-review support.

Add an explicit trigger clause, e.g. 'Use when drafting a systematic review or meta-analysis manuscript, or when the user provides Methods/Results sections and wants a publishable paper draft.'

Include natural synonyms users would say: 'systematic review', 'manuscript', 'SCI journal', 'PubMed references'.

DimensionReasoningScore

Specificity

Names the domain ('clinical meta-analysis paper') and several concrete actions: 'generate a complete paper draft including Abstract, Introduction, Discussion, and other sections' with defined inputs (research report, language, title). Not 5 because the description is literally truncated ('with automatic ...'), leaving coverage incomplete.

4 / 5

Completeness

The 'what' is clear (generates a full paper draft from a research report), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'clinical meta-analysis paper', 'research report', and 'Methods and Results sections' are natural user phrases, but common synonyms like 'systematic review', 'manuscript', 'SCI journal', or 'PubMed references' are missing — partly due to the truncation.

3 / 5

Distinctiveness Conflict Risk

'Generates a first draft of a clinical meta-analysis paper' carves a clear niche distinct from general writing skills; only minor overlap risk with broader academic-writing skills. Not 5 because the trigger surface (any 'paper writing' request) could attract related requests.

4 / 5

Total

14

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/meta-manuscript-generator/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.