CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-baseline-generator

Generates a meta-analysis baseline characteristics section (text + table) from raw data. Supports Chinese and English. Use when the user provides baseline data and wants a formatted results section.

Quality

72%

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/Academic Writing/meta-baseline-generator/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 of this skill is genuinely good — a clear, executable 5-step workflow with real prompt and script bundle files correctly referenced. However, roughly a third of the body is auto-generated boilerplate that restates the description, pads with generic execution-model language, and even mis-references its own sections, costing it conciseness and some navigation clarity.

Suggestions

Delete the boilerplate 'When to Use', 'Key Features', 'Dependencies', 'Implementation Details', and 'Input Validation' sections (or collapse them to one line each) — they restate the description and add no skill-specific guidance.

Replace the hardcoded dated path ('cd "20260316/scientific-skills/..."') with a relative path from the skill root, and document the script's CLI form: `python scripts/text_processor.py <language> <text_description> <raw_table>`.

Add a short end-to-end example (sample baseline JSON → generated text + table → final process_content output) so the common case is copy-paste ready, and fix the broken grammar in the first 'When to Use' bullet if that section is kept.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded sections: 'When to Use' repeats the description verbatim (including the broken phrase 'when you need generates a meta-analysis baseline characteristics section'), 'Key Features' is meta-filler ('Scope-focused workflow aligned to: <description>', 'Structured execution path designed to keep outputs consistent and reviewable'), 'Dependencies' notes 'not explicitly version-pinned in this skill package. Add pinned versions if...', and 'Implementation Details' offers generic padding ('Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable'). None of this adds skill-specific knowledge Claude lacks. This matches anchor 2 ('several unnecessary explanations or padded sections'); the core Workflow/Rules/Testing sections are efficient, keeping it above score 1.

2 / 5

Actionability

The Workflow gives concrete, executable guidance: named inputs (title, baseline_information, language), prompt references that exist (references/prompts.md), and copy-paste-ready code calling process_content(text_description=..., raw_table=..., language=...) whose signature matches scripts/text_processor.py. Minor gaps keep it from 5: the example uses a hardcoded dated path ('cd "20260316/scientific-skills/..."'), the relative sys.path.append('scripts') depends on cwd, the script's CLI form (language text table) is not documented, and there is no end-to-end worked example with sample input/output.

4 / 5

Workflow Clarity

A clear 5-step sequence (Gather Inputs → Text Description via prompt → Markdown Table via prompt → Process and Combine via script → Output) with per-step inputs/outputs, plus Rules and Testing Guidelines that serve as post-hoc verification points. It fits anchor 4 ('clear sequence with most checkpoints present; minor validation gaps'): there is no explicit in-flow checkpoint (e.g., 'verify the table is valid markdown before combining'), but this is not a destructive/batch operation so no cap applies, and the sequence is far above the gap-ridden anchor 3.

4 / 5

Progressive Disclosure

Against the actual bundle: references/prompts.md and scripts/text_processor.py both exist, are one level deep, and are clearly signaled with markdown links from the Workflow steps — good structure with most content appropriately placed. It falls short of anchor 5 because the SKILL.md body itself carries redundant auto-generated sections ('When to Use', 'Key Features', 'Implementation Details') that restate the description instead of pointing outward, and 'See ## Workflow above' in Implementation Details is misdirection (Workflow appears below that section), leaving minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

73%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 solid description: third-person voice, explicit what-and-when structure, and a well-defined niche that is unlikely to trigger for the wrong skill. The main gaps are modest — the 'when' clause could carry more concrete trigger phrases (Table 1, manuscript/results-section writing) and the capability list could enumerate the concrete actions more fully.

Suggestions

Add concrete trigger variations to the 'when' clause, e.g., 'Use when writing the results section of a meta-analysis or systematic review paper, or when the user mentions baseline characteristics, Table 1, or study characteristics.'

Slightly expand the 'what' with the key concrete actions, e.g., '...generates the descriptive text, builds the markdown baseline table, and inserts the (Table 1) citation.'

DimensionReasoningScore

Specificity

The description names the domain ('meta-analysis baseline characteristics section') and 1-2 concrete actions ('(text + table) from raw data'), but does not enumerate the fuller set of concrete actions (e.g., generating the text summary, building the markdown table, inserting the Table 1 citation). This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; score 4 would require several listed specific actions like the PDF example ('extracts text, fills forms, converts pages').

3 / 5

Completeness

Both parts are explicit: 'what' is 'Generates a meta-analysis baseline characteristics section (text + table) from raw data. Supports Chinese and English.' and 'when' is 'Use when the user provides baseline data and wants a formatted results section.' However, the 'when' clause is a single trigger and could be more specific (it omits the manuscript-writing context and terms like 'Table 1' for a meta-analysis paper), matching anchor 4 ('both what and when; when could be more explicit or specific') rather than score 5's multiple concrete trigger phrases. It is clearly above score 3, which requires a missing or only weakly implied 'when'.

4 / 5

Trigger Term Quality

Natural phrases a user would say are present: 'meta-analysis', 'baseline characteristics', 'baseline data', 'formatted results section', 'Chinese and English'. A few natural terms are missing — e.g., 'Table 1', 'study characteristics', 'systematic review', 'results section of a paper' — so it fits 'Good keyword coverage; a few natural terms missing' rather than the comprehensive synonym/extension coverage of score 5.

4 / 5

Distinctiveness Conflict Risk

'meta-analysis baseline characteristics' is a clear niche with distinct triggers ('baseline data', 'meta-analysis'), so conflict risk with unrelated skills is minimal — matching anchor 5. Score 4 ('minor overlap risk with closely related skills') would apply if the trigger were broader, but 'provides baseline data' plus the meta-analysis framing keeps it distinct; it is well above the generic 'Works with document files' territory of scores 2-3.

5 / 5

Total

16

/

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/Academic Writing/meta-baseline-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.