CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

discussion-section-architect

Structures and writes discussion sections for academic papers and research reports. Use when writing a discussion section, interpreting research results, connecting findings to existing literature, addressing study limitations, synthesizing conclusions, or drafting any part of...

Quality

74%

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/discussion-section-architect/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 core writing guidance — capabilities with example input/output pairs, a recommended structure, and a draft-revise checklist — is genuinely strong and actionable. However, it is buried in extensive generic audit boilerplate, contains duplicated sections, and points to reference files that are missing from the bundle, which hurt conciseness and navigation.

Suggestions

Remove the generic audit-compliance sections (Output Requirements, Response Template, User Checkpoints, Output Contract, Required Inputs, Quick Validation) that add no discussion-writing value, keeping the body lean.

Fix or remove the broken references: "references/guide.md" and "references/examples/" do not exist in the bundle.

Merge the two duplicate "## References" sections and reconcile the generic "## Workflow" section with the domain-specific "Quick Start" so there is one unambiguous workflow path.

DimensionReasoningScore

Conciseness

Roughly half the body is generic audit boilerplate ("Output Requirements", "Response Template", "User Checkpoints", "Output Contract", "Required Inputs", "Quick Validation") that is not specific to writing discussion sections and repeats itself (two "## References" sections, duplicate py_compile blocks), matching the noticeably-verbose/several-padded-sections anchor; not 3 because the padding is extensive rather than occasional.

2 / 5

Actionability

Concrete example input/output pairs, a specific six-part structure template, and an explicit revision checklist give mostly executable guidance per that anchor; not 5 because capability 3 uses bracketed placeholders ("[Describe constraint]") and the Quick Check commands are disconnected from the writing workflow.

4 / 5

Workflow Clarity

The Quick Start plus Draft → Revise loop provides a clear sequence with a genuine feedback loop (check → revise → re-check) and a checklist, approaching the top anchor; it drops to 4 because a competing generic "## Workflow" section and duplicated references create ambiguity about which path to follow.

4 / 5

Progressive Disclosure

References are labeled and the core writing content is well organized, but two referenced paths ("references/guide.md" and "references/examples/") do not exist in the bundle and the References section is duplicated, fitting the some-structure-with-organization-gaps anchor; not 4 because broken references actively impair navigation.

3 / 5

Total

13

/

20

Passed

Description

83%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 strong: it clearly states what the skill does and when to use it with natural, concrete trigger phrases for the academic-writing domain. Its main defects are the truncated final clause and the absence of a few natural synonyms that would push trigger coverage and specificity to the top anchors.

Suggestions

Complete the truncated final clause ("or drafting any part of..." ends mid-sentence) so no trigger guidance is lost.

Add common synonyms such as "manuscript", "results section", or "paper conclusions" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Structures and writes discussion sections" names the domain and lists several concrete actions ("interpreting research results, connecting findings to existing literature, addressing study limitations, synthesizing conclusions"), matching the several-specific-actions anchor with minor gaps; not 5 because action coverage is narrower than the comprehensive anchor examples.

4 / 5

Completeness

It explicitly answers both what ("Structures and writes discussion sections for academic papers and research reports") and when ("Use when writing a discussion section, interpreting research results...") with concrete trigger phrases, exactly matching the both-what-and-when anchor; the 4-anchor's caveat that 'when' could be more explicit does not apply.

5 / 5

Trigger Term Quality

Natural phrases like "writing a discussion section", "interpreting research results", and "addressing study limitations" are what academic writers would actually say; a few natural synonyms (e.g., "manuscript", "results section") are missing and the text ends truncated ("drafting any part of..."), keeping it below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The academic discussion-section niche is mostly distinct with clear triggers, but phrases like "synthesizing conclusions" and "interpreting research results" could also fire for a general academic-paper-writing skill, matching the minor-overlap-with-closely-related-skills anchor.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/discussion-section-architect/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.