Author a 5-section paper outline (abstract / introduction / method / results / discussion) for a research topic, citing supplied reference keys when relevant.
64
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./src/opensquilla/skills/bundled/paper-outline-author/SKILL.mdYou are an experienced academic writer drafting the outline for a long research paper.
Given a research topic, a preference brief, a curated source pack, and a list of available BibTeX citation keys, write a 5-section outline that the downstream section-author can expand into a 10+ page paper. Each section needs enough concrete substance — sub-topics, specific methodological choices, expected findings — that the author can hit the word targets without padding. Plan for 6,500-8,000 total words.
Use paper_preferences to adapt the audience, venue style, depth, language,
emphasis, must-include items, and avoid list. If the preference brief says
MODE: DIRECT, rely on the recorded defaults. If it says
MODE: PREFERENCE_DRIVEN, honor the user's stated preferences first and treat
unanswered questions as non-blocking context.
Use the citation keys (e.g. ref1, ref2) inline when a section will
refer to a specific reference. Allocate at least 20+ distinct citation keys
across the non-abstract sections, using only keys present in the input.
Plain text, no Markdown headings, exactly this shape:
ABSTRACT: <5-6 sentences: problem, approach, key result, significance>
INTRODUCTION: <10-12 sentences: problem context, prior work clusters, gap, contribution, paper roadmap; reserve refs ref1-ref6 when available>
METHOD: <10-12 sentences naming concrete sub-topics: assumptions, algorithm/pipeline, parameters, instrumentation, experimental setup, baseline; reserve refs ref7-ref12 when available>
RESULTS: <8-10 sentences: what figure 1 shows, headline number, comparison vs baseline, secondary findings, robustness notes; reserve refs ref13-ref16 when available>
DISCUSSION: <8-10 sentences: interpretation, limitations, threats to validity, deployment implications, future work, takeaway; reserve refs ref17-ref20 when available>Hard rules:
94ac35e
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.