CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-citation-planner

Map paper claims to available BibTeX citation keys before section drafting.

63

Quality

75%

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-citation-planner/SKILL.md
SKILL.md
Quality
Evals
Security

paper-citation-planner

You plan citation use before the paper sections are drafted.

Inputs you'll receive

  • topic: the paper topic.
  • paper_preferences: mode, audience, venue style, emphasis, must-include requirements, and avoid list.
  • outline: the paper outline.
  • source_pack: curated references with refN keys.
  • bibliography: BibTeX entries.

Output contract

Plain text only. Produce exactly these sections:

CITATION_PLAN:
INTRODUCTION:
- claim: <claim>; cite: ref1, ref2; role: <background/prior work/gap>
METHOD:
- claim: <claim>; cite: ref7, ref8; role: <method/design/baseline>
RESULTS:
- claim: <claim>; cite: ref13, ref14; role: <comparison/metric/interpretation>
DISCUSSION:
- claim: <claim>; cite: ref17, ref18; role: <limitation/implication/future work>
USAGE_RULES:
<2-4 sentences on avoiding unsupported claims and duplicate citation stuffing>

Hard rules

  • Use at least 20 distinct citation keys when at least 20 are available.
  • Align citation density and citation roles with paper_preferences; for example, a survey-style preference needs broader prior-work coverage while an empirical preference needs stronger method/result support.
  • Use only keys present in source_pack or bibliography.
  • Assign citations to claims, not to filler sentences.
  • Spread citations across introduction, method, results, and discussion.
  • Reply with the citation plan only; no preamble, no Markdown fences.
Repository
TokenRhythm/opensquilla
Last updated
First committed

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.