CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

results-section-structurer

Organizes biomedical figures, analyses, and result blocks into a clear Results section structure with disciplined narrative ordering and evidence-aware presentation.

Quality

64%

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 ./awesome-med-research-skills/Academic Writing/results-section-structurer/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 skill body is well-structured at the reference level — every reference file exists, is one level deep, and is cited with its purpose — and the workflow is clearly sequenced with an explicit clarify-first gate. However, it is heavily self-redundant (the same rules restated in six sections, Hard Rules duplicated verbatim in references/hard-rules.md), and it leans on an undefined 'citation-support marker' that the mandatory output requires.

Suggestions

Consolidate the redundant sections ('Task', 'Core Function', 'Execution', 'Hard Rules', 'What This Skill Should Not Do', 'Quality Standard') into one statement of function plus one rule list, removing the verbatim duplication with references/hard-rules.md — the SKILL.md could shrink by roughly half.

Define the citation-support marker concretely (e.g., a literal marker format and an example PubMed search query) in references/citation-support-annotation-rules.md, since Section F of the mandatory output requires it but no artifact definition exists anywhere in the bundle.

Add one short worked example of a recommended Results section order (e.g., cohort -> primary finding -> mechanistic support -> sensitivity -> validation) to make Section D guidance concrete instead of purely procedural.

DimensionReasoningScore

Conciseness

The ~275-line body repeats the same directives many times across 'Task', 'Core Function', 'Execution', 'Hard Rules', 'What This Skill Should Not Do', and 'Quality Standard' (e.g., 'recommend uploading the study protocol ... or results report' appears at least six times), and the 'Hard Rules' section duplicates references/hard-rules.md nearly verbatim. It is noticeably verbose with several padded, redundant sections; it is not 1 because it never explains concepts Claude already knows — the padding is self-repetition, not background exposition — and not 3 because the redundancy is pervasive, not occasional.

2 / 5

Actionability

The 9-step execution flow and the mandatory A-I output structure give concrete, specific process guidance (appropriate for an instruction-only skill), but key details are missing: the 'citation-support marker' that must appear in Section F is never defined anywhere (references/citation-support-annotation-rules.md also just says 'the required citation-support marker'), there is no worked example of a structured Results output or a PubMed query format, and 'typical elements may include' leaves block design open. It is not 4 because an output-required artifact being undefined is more than a minor gap, and not 2 because the process itself is specific and sequenced rather than high-level hints.

3 / 5

Workflow Clarity

Steps are clearly sequenced: Step 1 gates long-form output on input sufficiency, the 'Input Validation' checklist defines what must be known, and Step 8 / Section A / Section I flag remaining uncertainty — real checkpoints for a writing task. It is not 5 because there is no explicit feedback loop describing what happens after the user supplies the missing materials (i.e., re-run the hierarchy identification), and not 3 because the clarify-first checkpoint is explicit and central rather than implicit.

4 / 5

Progressive Disclosure

All seven referenced files exist in references/, are exactly one level deep, and each is cited in the body with a stated purpose ('Use before any long-form structuring', 'Use to decide the order of...'), which is good, well-signaled navigation. It is not 5 because content is not appropriately split: the body inlines the Hard Rules verbatim in references/hard-rules.md and duplicates the ordering logic already in results-ordering-rules.md, so the SKILL.md is not a lean overview. It is not 3 because the reference structure itself is well organized and clearly signaled.

4 / 5

Total

13

/

20

Passed

Description

61%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 clear, reasonably specific niche — structuring biomedical Results sections — with good natural trigger terms, but it lacks any 'when to use' guidance and describes a single bundled action rather than enumerating capabilities. The buzzwordy closing phrase adds length without adding trigger value.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to structure, order, or reorganize a Results section, sequence figures, or fix a fragmented Results draft.'

Replace the vague closing phrase ('disciplined narrative ordering and evidence-aware presentation') with one or two more concrete capabilities or natural synonyms such as 'manuscript' or 'reorganize Results'.

DimensionReasoningScore

Specificity

The description names the domain ("biomedical figures, analyses, and result blocks") and one core action ("Organizes ... into a clear Results section structure"), but the trailing phrases "disciplined narrative ordering and evidence-aware presentation" are qualities of that single action rather than a list of several distinct concrete actions, matching the '1-2 concrete actions, not comprehensive' anchor. It is not score 4 because it does not enumerate multiple specific operations (e.g., sequence blocks, diagnose fragmentation, assign subsection roles), and not score 2 because the action and domain are concrete, not generic.

3 / 5

Completeness

The 'what' is clear (organize existing figures, analyses, and result blocks into a Results section structure), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. It is not 2 because the 'what' is specific rather than vague, and not 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Good keyword coverage of natural user phrasing: "Results section", "figures", "analyses", "result blocks", "biomedical" are all terms a user would plausibly say when needing this skill. It falls short of 5 because common synonyms like "manuscript", "paper", or "reorganize/restructure my results" are absent, and "disciplined narrative ordering" / "evidence-aware presentation" read as marketing language rather than natural trigger terms — which also keeps it above 3, where keyword coverage would be merely partial.

4 / 5

Distinctiveness Conflict Risk

The biomedical Results-section structuring niche is well staked out with distinct triggers ("Results section", "result blocks"), creating minimal conflict risk with unrelated skills. It is not 5 because within a manuscript-writing skill family (e.g., sibling skills for Discussion or Methods structuring) the overlap is real but minor, matching 'mostly distinct; minor overlap risk with closely related skills'.

4 / 5

Total

14

/

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

awesome-med-research-skills/Academic Writing/results-section-structurer/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.