CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

introduction-logic-builder

Builds background-gap-objective logic for biomedical manuscript introductions with clear study positioning and disciplined narrative structure.

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 ./awesome-med-research-skills/Academic Writing/introduction-logic-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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 an excellent, well-validated workflow and a genuinely progressive reference structure, but the body is padded with four to five near-duplicate restatements of the same rules and lists. Trimming the redundancy and adding one brief worked example would raise both conciseness and actionability.

Suggestions

Collapse the redundancy: merge 'Task', 'Core Function', 'Input Validation', and Step 1 into one authoritative statement of what the skill does and when to ask for more input; the per-section repeats dilute the signal.

Remove or drastically shorten the inline 'Hard Rules' list and 'What This Skill Should Not Do' section, since both duplicate references/hard-rules.md and each other - keep one pointer to the reference file.

Add a short worked example (e.g., a weak gap statement vs. a disciplined one, or a sample Study Positioning Statement) so the abstract distinctions like 'knowledge gap vs generic unanswered question' become concrete.

DimensionReasoningScore

Conciseness

The body is noticeably verbose due to heavy redundancy: the Task list, Core Function list, Input Validation section, Step 1, and the clarification-first reference each restate the same clarify-before-building points, and the 10 Hard Rules overlap substantially with 'What This Skill Should Not Do' and 'Important Distinctions' as well as with hard-rules.md.

2 / 5

Actionability

The guidance is concrete for an instruction-only skill: a 10-step execution sequence and a mandatory A-I output structure that specifies what each section must contain. The gap keeping it from 5 is the absence of any worked example (e.g., a sample gap statement or positioning statement).

4 / 5

Workflow Clarity

The sequence is clear with explicit validation checkpoints (Step 1 clarify-first gate, Step 8 uncertainty flagging, Input Match Check, Claim Boundary Check), a clarify-then-build feedback loop, and an input-sufficiency checklist, matching the top anchor.

5 / 5

Progressive Disclosure

All six referenced files exist, are one level deep, and are integrated with per-file usage guidance. Minor gaps: the SKILL.md inlines content duplicated in hard-rules.md and repeats reference-file instructions in the body rather than deferring to the files.

4 / 5

Total

15

/

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 is concise, in third person, and clearly identifies a specific niche, but it lacks any 'when to use' trigger guidance and its action statements are abstract rather than concrete. Adding a Use-when clause with natural user phrases would address the biggest gaps.

Suggestions

Add a 'Use when...' clause with natural trigger phrases, e.g. 'Use when the user asks to structure or fix the logic of a manuscript introduction, position a study in the introduction, or build a background-gap-objective flow.'

Make the actions more concrete: instead of 'Builds background-gap-objective logic... with disciplined narrative structure', list deliverables such as 'defines the problem, identifies the true knowledge gap, positions the study, and assigns paragraph roles.'

Include common user phrasings and synonyms ('introduction feels scattered', 'literature dump', 'help me structure my introduction') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('biomedical manuscript introductions') and one or two actions ('Builds background-gap-objective logic', 'clear study positioning'), but the actions are abstract rather than the multiple concrete, comprehensive operations of a top score.

3 / 5

Completeness

The 'what' is clear (builds introduction logic with positioning and narrative structure), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

It includes some relevant keywords users would naturally say ('introduction', 'manuscript', 'study positioning'), but misses common variations and phrases such as 'structure my introduction', 'intro feels scattered', or 'paper introduction'.

3 / 5

Distinctiveness Conflict Risk

The biomedical introduction-logic niche is fairly distinct with domain-specific terms ('background-gap-objective', 'study positioning'), though it could minorly overlap with adjacent biomedical manuscript-writing skills.

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-logic-builder/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.