CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-outline-author

Author a 5-section paper outline (abstract / introduction / method / results / discussion) for a research topic, citing supplied reference keys when relevant.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./src/opensquilla/skills/bundled/paper-outline-author/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, highly actionable instruction-only skill with an exact output template and concrete constraints, and it is well-structured with no need for external references. The only meaningful gap is the absence of an explicit self-verification step against the hard rules before emitting the outline.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence (it does not explain what an abstract or a citation key is), with only minor phrases such as the 10+ page expansion rationale that could be trimmed.

4 / 5

Actionability

A precise fill-in output contract with per-section sentence counts and reserved reference ranges, plus concrete hard rules (>=20 distinct keys, a specific number in METHOD/RESULTS, no Markdown), gives copy-paste-ready executable guidance for an instruction-only skill.

5 / 5

Workflow Clarity

The single generation task is unambiguous and well-sequenced (preferences -> citation keys -> 5-section contract -> hard rules), with the hard rules acting as checkpoints, but there is no explicit final verification pass confirming the rules were satisfied.

4 / 5

Progressive Disclosure

The skill is self-contained (no references/ scripts/ assets/ bundles exist), under ~50 lines, and organized into clearly headed sections (Task, Output contract, Hard rules), satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

70%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 specific and carves a clear, distinct niche, but it lacks any explicit 'when to use' trigger guidance, which caps completeness. Adding a 'Use when...' clause would materially raise the score.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a research paper outline, essay structure, or section-by-section plan for a long paper.'

Include a couple of natural synonyms ('draft outline', 'manuscript outline') to broaden trigger-term coverage.

Optionally mention the input precondition (a curated source pack / BibTeX keys) so the 'when' is tied to having references to cite.

DimensionReasoningScore

Specificity

The description names a concrete action ('Author a 5-section paper outline') and enumerates all five sections (abstract / introduction / method / results / discussion) plus the citation behavior, giving several specific actions with only minor coverage gaps.

4 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance; the 'when relevant' phrase applies to citations, not to when the skill should be used, capping completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like 'paper outline' and 'research topic' are present, but a few common synonyms a user might say (e.g. 'draft', 'essay', 'manuscript') are missing and 'reference keys' leans slightly technical.

4 / 5

Distinctiveness Conflict Risk

The fixed 5-section research-paper outline with supplied reference-key citation is a narrow, distinct niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.