CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-title-generator

Generates Meta-Analysis research titles based on user keywords, utilizing PubMed search results if available, or creative generation otherwise. Use when the user wants to brainstorm or generate titles for a meta-analysis, specifically starting from keywords or a topic.

Quality

73%

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/Data Analysis/meta-title-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 Usage and Quality Rules sections give a genuinely usable, well-sequenced workflow with a real one-level reference, but the body is padded with redundant template sections ('When to Use', 'Key Features', 'Implementation Details') and its only runnable example misstates the script's CLI. Removing the boilerplate and showing the real invocation would lift this substantially.

Suggestions

Delete the boilerplate 'When to Use', 'Key Features', 'Dependencies', 'Example Usage', and 'Implementation Details' sections that restate the description or contain generic filler; keep the Description, Usage, Quality Rules, and Reference Material sections.

Replace 'python scripts/search_pubmed.py --help' with the actual invocation, e.g. python scripts/search_pubmed.py "(lung cancer) AND (chemotherapy)", and show a sample {"total": ..., "text": ...} output plus the required Title1–Title5 English/Chinese JSON structure.

Add a validation step that checks the final output contains exactly 5 titles, each with both English and Chinese fields and an explicit meta-analysis/systematic-review designation, before returning the result.

DimensionReasoningScore

Conciseness

Several sections are padded boilerplate that add no information Claude needs: the 'When to Use' bullet restates the frontmatter description nearly verbatim (with a garbled 'need generates meta-analysis research titles'), 'Key Features' and 'Implementation Details' are generic template filler ('Packaged executable path(s): scripts/search_pubmed.py', 'Execution model: validate the request, choose the packaged workflow'), and 'Example Usage' opens with a circular 'See ## Usage above' plus a machine-specific path 'cd "20260316/scientific-skills/Data Analytics/meta-title-generator"'. This is noticeably verbose with multiple unnecessary sections, matching the 2 anchor rather than the 3 anchor's 'some unnecessary explanation'.

2 / 5

Actionability

The Usage workflow is concrete (generate a search strategy, run the script, branch on result count, emit a Title1–Title5 JSON with English/Chinese fields), but the one executable invocation shown — 'python scripts/search_pubmed.py --help' — misrepresents the interface: the script takes the query as a positional sys.argv[1] argument with no argparse, so --help would run a PubMed search for the literal string. The actual command for passing the search strategy (e.g., python scripts/search_pubmed.py "(lung cancer) AND (chemotherapy)") and a sample output JSON are never shown, so key execution details are missing — the 3 anchor, not the 4.

3 / 5

Workflow Clarity

The 'Search and Generate' section lays out a clear 4-step sequence with an explicit branch checkpoint ('If the result count is > 0 ... If the result count is 0') and concrete post-conditions ('Ensure titles are strictly for Meta-Analysis', 'Bilingual Output'), and the run plan includes reviewing output. It is not a 5 because there is no validation of the emitted JSON against the required Title1–Title5 format and no error-recovery guidance beyond the count branch; the operations are non-destructive, so the batch-validation cap does not apply.

4 / 5

Progressive Disclosure

The body is an overview with a single, real, one-level-deep reference — 'For detailed prompting strategies used in title generation, see references/title_generation_prompts.md' — and the bundled scripts/search_pubmed.py exists and is correctly named, matching the actual bundle structure. It is not a 5 because the duplicated 'Description'/'Usage' sections and the self-referential 'See ## Usage above' leave minor navigation and organization gaps rather than a cleanly split overview.

4 / 5

Total

13

/

20

Passed

Description

83%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 explicitly states what the skill does and when to use it, with a distinctive meta-analysis/PubMed niche and natural trigger phrasing. Minor gaps (no mention of the bilingual output or the 5-title deliverable, and some overlap risk with generic title-brainstorming) keep it just below the top tier.

DimensionReasoningScore

Specificity

The description names several concrete actions — 'Generates Meta-Analysis research titles based on user keywords', 'utilizing PubMed search results if available', 'creative generation otherwise' — which map to the actual skill behavior. It falls short of a 5 because it omits known capabilities like the bilingual (English/Chinese) output and the fixed count of 5 titles, leaving minor gaps in coverage.

4 / 5

Completeness

Both halves are explicit: the 'what' is 'Generates Meta-Analysis research titles based on user keywords, utilizing PubMed search results if available, or creative generation otherwise', and the 'when' is a concrete 'Use when the user wants to brainstorm or generate titles for a meta-analysis, specifically starting from keywords or a topic'. This matches the top anchor of a clear what plus a concrete trigger phrase; it is not a 4 because the when-clause is already explicit and specific rather than merely serviceable.

5 / 5

Trigger Term Quality

Natural trigger phrases are present: 'brainstorm or generate titles for a meta-analysis', 'keywords', 'a topic', 'Meta-Analysis research titles'. A few natural variations are missing (e.g., 'systematic review', 'paper titles', 'title suggestions'), so it does not reach the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The niche (meta-analysis title generation from keywords via PubMed) is fairly distinct, with triggers like 'titles for a meta-analysis' unlikely to fire for unrelated skills. It stays at 4 rather than 5 because 'brainstorm... titles' and 'PubMed search' could overlap with generic title-brainstorming or literature-search skills in the same collection.

4 / 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/Data Analysis/meta-title-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.