CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-results-forest-plot-analyzer

Analyzes forest plots for meta-analysis, generating detailed descriptions and formatting figure legends in Chinese or English. Use when the user wants to interpret a forest plot image, describe its statistical significance (heterogeneity, p-value), and format the output with s...

Quality

73%

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-results-forest-plot-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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's actual core content — a two-step Vision-LLM-then-script workflow with concrete formatting rules and an example — is well specified and executable. However, the body is buried under extensive generic boilerplate, duplicated validation sections, and cross-references that add tokens without skill-specific value, and the documented commands do not fully match the packaged script's real CLI.

Suggestions

Remove the generic template sections (When to Use, Key Features, Implementation Details, Deterministic Output Rules, Completion Checklist, etc.) that contain no skill-specific information, keeping only the Workflow, Usage, Examples, and validation guidance.

Merge the duplicate "Validation Shortcut" and "Quick Validation" sections, and replace the circular "See `## Usage` above" cross-references with the actual content placed once.

Document the real CLI of `scripts/format_result.py` (positional `text language` arguments) and the Chinese header/footer formatting branch, and remove the fabricated expected-output block.

DimensionReasoningScore

Conciseness

Roughly two-thirds of the body is generic template boilerplate with no skill-specific content ("Use this skill when the request matches its documented task boundary", "keep results reproducible, identify assumptions explicitly", and ~10 similar sections). It is not 1 because it never explains concepts Claude already knows and the core Workflow/Usage/Examples sections are efficient; it is not 3 because the padding is extensive, duplicated across sections, and includes a time-sensitive date-stamped path ("cd \"20260316/scientific-skills/...\"").

2 / 5

Actionability

The Workflow gives precise formatting rules ("Inserts `(Figure 2)` before the last punctuation mark", exact header/footer strings) plus a worked input→process→output example and runnable commands. It is not 5 because the documented validation command `python scripts/format_result.py --help` does not match the script's actual positional `text language` CLI, and the script's Chinese header/footer branch is undocumented in the body.

4 / 5

Workflow Clarity

The two-step sequence (Vision LLM image analysis with explicit prompt guidelines → script formatting) is unambiguous, with validation shortcuts, a completion checklist, and failure handling. It is not 5 because the "Expected output format" block after the validation command is aspirational rather than what the script produces, and the duplicated validation sections create minor confusion.

4 / 5

Progressive Disclosure

Both referenced bundle paths (`scripts/format_result.py`, `scripts/validate_skill.py`) exist and are one level deep, but the SKILL.md organization is muddled: "Validation Shortcut" and "Quick Validation" duplicate each other, sections point forward and backward with "See `## Usage` above", and boilerplate sections are interleaved with the real content. It is not 4 because these duplications and circular cross-references are more than minor organization gaps; it is not 2 because the file does have clear section headers and all references resolve.

3 / 5

Total

13

/

20

Passed

Description

78%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, well-targeted description that names a niche domain, multiple concrete actions, and explicit trigger conditions in third person. Its main defect is that the text is truncated mid-phrase, which cuts off the final trigger condition and drops coverage of at least one natural term.

Suggestions

Complete the truncated final clause (e.g., "...and format the output with specific figure legends") so the trigger guidance ends cleanly.

Add natural synonyms such as "effect size", "confidence interval", or "pooled effect" to improve trigger-term coverage for meta-analysis requests.

DimensionReasoningScore

Specificity

"Analyzes forest plots for meta-analysis, generating detailed descriptions and formatting figure legends in Chinese or English" lists several specific concrete actions in a clear domain. It is not 3 because more than 1-2 concrete actions are named, and not 5 because the final action is cut off mid-phrase ("format the output with s...").

4 / 5

Completeness

Both the "what" (analyze forest plots, generate descriptions, format legends) and an explicit "Use when the user wants to..." trigger clause are present. It is not 5 because the when-clause is truncated mid-sentence ("format the output with s"), leaving the trigger guidance incomplete.

4 / 5

Trigger Term Quality

Natural terms like "forest plot", "meta-analysis", "heterogeneity", "p-value", and "interpret a forest plot image" match what a user would actually say. It is not 5 because common synonyms such as "effect size", "confidence interval", or "pooled results" are absent, and the truncated ending drops at least one trigger phrase.

4 / 5

Distinctiveness Conflict Risk

"forest plots for meta-analysis" with "heterogeneity, p-value" triggers carves out a clear niche with distinct trigger terms and minimal overlap risk with other skills.

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/Academic Writing/meta-results-forest-plot-analyzer/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.