CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-section-author

Write one publication-style research-paper section as a bounded, citation-grounded LaTeX fragment from a writing plan, outline, citation plan, and optional figure/table context.

55

Quality

63%

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 ./src/opensquilla/skills/bundled/paper-section-author/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 is a well-organized, highly actionable instruction-only skill with concrete contracts and an explicit pre-reply verification checklist. Its main weakness is conciseness, driven by repeated expansion and anti-filler rules.

Suggestions

Consolidate the three repeated expand-if-short directives (lines 127-133) into a single stated rule to reduce redundancy.

Merge the duplicate anti-filler guidance (lines 107-108 and 170-171) into one location.

Add one short worked example (e.g. a 4-sentence abstract opener) to lift actionability from concrete directives to copy-paste-ready demonstration.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no concept padding), but several rules are restated — the expand-if-short directive appears three times (lines 127-133) and the anti-filler guidance is repeated (lines 107-108 and 170-171) — so it could be tightened.

3 / 5

Actionability

Guidance is highly concrete for an instruction-only skill: exact section openers, named subsections, `\cite{refN}` format, and explicit LaTeX-escape rules; the minor gap is the absence of a complete worked example of a finished section.

4 / 5

Workflow Clarity

A clear sequence is implied (identify thesis → draft per section contract → expand if below budget → 'silently verify' checklist before replying) with an explicit validation checklist; not a 5 because the steps are not presented as a single numbered runbook with error-recovery loops.

4 / 5

Progressive Disclosure

The body is well-sectioned (Inputs, Output contract, Structure expectations, Writing quality bar, Hard rules) with no nested or buried references and no bundle files to navigate; it exceeds the 50-line simple-skill exception, so it stays at 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

58%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 is appropriately specific and distinct, but it omits any explicit 'when to use' trigger guidance and lacks natural user-facing trigger phrases. It is solid but capped by the missing trigger clause.

Suggestions

Add an explicit trigger clause, e.g. 'Use when drafting a single section of a research paper as LaTeX from a writing plan and citation plan.'

Include natural user-facing phrases such as 'write my introduction', 'draft the method section', or 'author a paper section' alongside the technical terms.

DimensionReasoningScore

Specificity

States a concrete action ('Write one publication-style research-paper section as a bounded, citation-grounded LaTeX fragment') and enumerates specific inputs (writing plan, outline, citation plan, figure/table context); minor gap is that it is a single action rather than a list of several.

4 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Domain terms like 'research-paper section', 'LaTeX fragment', 'citation-grounded' are relevant but it lacks the natural phrases a user would actually say (e.g. 'write my introduction', 'draft the methods section') and any synonyms.

3 / 5

Distinctiveness Conflict Risk

The niche is specific (one LaTeX paper section from a writing-plan contract) and unlikely to fire for unrelated skills; only minor overlap risk with adjacent paper-authoring 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.

Validation15 / 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
TokenRhythm/opensquilla
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.