CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-results-sensitivity-analysis

Generates the "Results" section for meta-analysis sensitivity analysis based on statistical tables and titles. Use when the user wants to describe sensitivity analysis results or format sensitivity tables for a meta-analysis paper.

Quality

67%

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-sensitivity-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 knows its two-step core workflow (LLM describes the table, script formats the output) but buries it under ~10 sections of generic template boilerplate, contradictory validation guidance, and a commented-out example that references a nonexistent script. The signal-to-noise ratio is low and the executable path is unverifiable as documented.

Suggestions

Cut the generic boilerplate sections (Key Features, Dependencies, Implementation Details, Required Inputs, Output Contract, Validation and Safety Rules, Failure Handling, Deterministic Output Rules, Completion Checklist) and keep only the workflow, input parameters, quality rules, and one validation command — this alone would roughly halve the body.

Make the usage example executable: either ship scripts/format_result.py (currently referenced but missing from the bundle) with a real call, or replace the commented-out pseudocode with a concrete worked example of the expected input table and resulting formatted output.

Resolve the contradictions: 'Validation Shortcut' instructs running validate_skill.py --help while 'Quick Validation' says no local script validation is required, and 'See ## Usage above' / 'See ## Workflow above' point to sections that appear later — fix these to a single consistent validation step and correct cross-reference direction.

DimensionReasoningScore

Conciseness

The ~175-line body is dominated by generic boilerplate sections ('Key Features', 'Dependencies', 'Implementation Details', 'Required Inputs', 'Output Contract', 'Deterministic Output Rules', 'Completion Checklist') that restate the description verbatim and pad with process filler Claude already knows. This matches the 'noticeably verbose; several padded sections' anchor rather than the 'mostly efficient with some tightening' anchor, since the padding is pervasive rather than incidental.

2 / 5

Actionability

There are concrete commands ('python scripts/validate_skill.py --help') and documented input parameters, but the core usage example is entirely commented-out pseudocode importing 'format_sensitivity_result' from 'scripts/format_result.py' — a file that does not exist in the bundle. This matches the 'pseudocode instead of executable code; missing key details' anchor: not 4 because the primary execution path is non-executable, not 2 because real commands and parameter documentation are present.

3 / 5

Workflow Clarity

The Workflow section lists two clear steps and the skill includes checklists and failure handling, but these are undermined by contradictions — 'Validation Shortcut: run python scripts/validate_skill.py --help' versus 'Quick Validation: No local script validation step is required' — and misdirected cross-references ('See ## Usage above' points to a section that appears later in the document). Sequence is present but checkpoints are confused, matching anchor 3 rather than 4.

3 / 5

Progressive Disclosure

Section headers provide some structure, but the body is monolithic (generic governance sections inline that add no navigational value), there is no references/ bundle to disclose into, and one referenced script (scripts/format_result.py) is missing from the actual bundle, which contains only validate_skill.py. This matches the 'some structure but could be better organized' anchor rather than the well-organized anchor 4.

3 / 5

Total

11

/

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 description: it explicitly states what the skill does and when to use it, with natural, domain-appropriate trigger terms and a clearly bounded niche. Its only weaknesses are modest action variety and some missing synonyms for trigger coverage.

DimensionReasoningScore

Specificity

Names a narrow domain (meta-analysis sensitivity analysis) with about two concrete actions — 'Generates the "Results" section... based on statistical tables and titles' and 'format sensitivity tables' — but the verbs largely restate one another rather than listing several distinct capabilities, matching the 1-2-concrete-actions anchor rather than the several-actions anchor.

3 / 5

Completeness

Explicitly answers both 'what' (first sentence: generates the Results section from statistical tables and titles) and 'when' with concrete trigger phrases ('Use when the user wants to describe sensitivity analysis results or format sensitivity tables for a meta-analysis paper'). Clearly matches the top anchor, not the 4 anchor whose 'when' is only partially explicit.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'sensitivity analysis', 'meta-analysis', 'Results section', 'sensitivity tables', 'statistical tables'. Missing common synonyms a user might say (e.g., 'leave-one-out', 'robustness check'), so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

'meta-analysis sensitivity analysis' is a clear niche with distinct triggers, minimizing confusion with unrelated skills. Minor overlap risk remains with closely related meta-analysis writing skills (e.g., subgroup-analysis or forest-plot Results generators), so the mostly-distinct anchor fits better than the minimal-conflict anchor.

4 / 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-results-sensitivity-analysis/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.