CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

introduction-section-writer

Writes the full Introduction section of a biomedical manuscript based on an approved or sufficiently clear study logic, while preserving evidence boundaries and introduction discipline.

Quality

60%

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/introduction-section-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 has a genuinely strong workflow design — explicit readiness gating, a 9-step sequence, and a mandatory output structure — but the body is heavily redundant, lacks concrete examples (markers, PubMed queries, output templates), and leaves 40% of its reference bundle unreferenced. It is a solid draft that needs consolidation and example material rather than a redesign.

Suggestions

Consolidate the redundant sections: merge Task/Core Function, Scope Boundary/What This Skill Should Not Do, Hard Rules/Formatting Expectations, and Input Validation/Step 1 into one statement each to roughly halve token cost without losing content.

Add one concrete mini-example: a sample citation-marker usage and a sample PubMed search query (e.g., `("heart failure"[Title] AND biomarker[Title]) AND review[Filter]`), and reconcile the hardcoded Chinese marker "强烈建议插入文献" with references/citation-marker-note.md, which requires an English-only skill body.

Update Reference Module Integration to list all bundle files, merging the duplicated handoff-rule.md into handoff-to-logic-builder-rule.md and adding pointers to paragraph-role-control-rules.md and study-positioning-and-claim-boundary-rules.md.

DimensionReasoningScore

Conciseness

The body states the same rules three to four times across sections: the redirect to Introduction Logic Builder appears in Task, Scope Boundary, Reference Module Integration, Input Validation, Step 1, Step 8, output sections A and I, Hard Rule 3, and Quality Standard; Hard Rules, What This Skill Should Not Do, and Scope Boundary largely restate each other; Mandatory Output Structure and Formatting Expectations overlap. This pervasive redundancy goes beyond "some unnecessary explanation" (anchor 3) and matches "noticeably verbose; several unnecessary explanations or padded sections" (anchor 2).

2 / 5

Actionability

There is concrete guidance — a 9-step execution flow and a mandatory A-I output structure — but key executable details are missing: no example of a citation-support marker in use, no sample PubMed search query, no example of a well-vs-poorly-written gap statement, and no template showing what a final output looks like. Additionally, the hardcoded Chinese marker "强烈建议插入文献" contradicts references/citation-marker-note.md, which requires the skill to stay fully in English with the marker managed outside the skill. This fits "some concrete guidance but incomplete; missing key details" (anchor 3) better than anchor 4's "minor gaps".

3 / 5

Workflow Clarity

Steps 1-9 give a clear sequence with explicit checkpoints: the input-sufficiency check (Steps 1-2) gates drafting, and the Writing Readiness Decision (output section C) forces a ready/partially-ready/not-ready verdict before the draft (section D) is produced, with Step 7 and section H covering residual-uncertainty flagging. Not anchor 5 because there is no explicit error-recovery loop (e.g., what to do after follow-up questions are answered) and the sufficiency criteria are listed but not operationalized; not anchor 3 because the gating checkpoints are explicit rather than implicit.

4 / 5

Progressive Disclosure

The Reference Module Integration section clearly signals six one-level-deep reference files with their purposes, but four of the ten bundle files are never referenced from SKILL.md (paragraph-role-control-rules.md, study-positioning-and-claim-boundary-rules.md, handoff-rule.md, citation-marker-note.md), leaving substantive rules unreachable via navigation; handoff-rule.md also duplicates the referenced handoff-to-logic-builder-rule.md. Per the guideline to score against the actual bundle structure, the buried 40% of the bundle is more than a "minor organization gap" (anchor 4) and matches "some structure... references present but not clearly signaled" (anchor 3).

3 / 5

Total

12

/

20

Passed

Description

53%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 clearly states what the skill does and its niche, but lacks any explicit 'Use when...' trigger guidance and has thin keyword coverage. It sits just above the midpoint of quality for a skill description.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to write, draft, expand, or rewrite the Introduction section of a biomedical manuscript, or to turn an approved outline or background-gap-objective logic into full prose."

Add natural user phrasings as keywords ("write the Introduction", "draft the intro section", "manuscript introduction", "rewrite my Introduction") to improve trigger matching.

Name the sibling skill boundary explicitly (e.g. "...once Introduction Logic Builder has defined the logic") to further reduce confusion with the logic-building skill.

DimensionReasoningScore

Specificity

The description names the domain ("biomedical manuscript") and one concrete action ("Writes the full Introduction section"), with the condition "based on an approved or sufficiently clear study logic". It lists only a single action, matching the 1-2 concrete actions anchor; it does not enumerate multiple specific capabilities like the score 4-5 anchors.

3 / 5

Completeness

The "what" is clear (writes the full Introduction section of a biomedical manuscript), but there is no "Use when..." clause or equivalent explicit trigger guidance — "based on an approved or sufficiently clear study logic" states a precondition, not when to invoke the skill. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present ("Introduction section", "biomedical manuscript", "study logic"), but common natural variations users would say ("write my Introduction", "draft the intro", "manuscript introduction") are missing, matching the "some relevant keywords but missing common variations or synonyms" anchor.

3 / 5

Distinctiveness Conflict Risk

It carves a fairly clear niche (full Introduction-section writing for biomedical manuscripts, gated on approved logic), which distinguishes it from generic writing skills. Minor overlap risk remains with its sibling skill (Introduction Logic Builder), which the description alludes to via "approved... study logic" but never names. Mostly distinct with minor overlap risk, matching anchor 4 rather than anchor 3 (which would imply broader overlap) or anchor 5 (which would require naming the sibling boundary explicitly).

4 / 5

Total

13

/

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/introduction-section-writer/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.