paper-preference-planner

Extracts paper-writing preferences from user requests into a structured preference brief.

6.8k|540|Updated May 6, 2026
One-click install
npx skills add https://github.com/opensquilla/opensquilla --skill paper-preference-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paper-preference-planner
Source: https://github.com/opensquilla/opensquilla/tree/main/src/opensquilla/skills/bundled/paper-preference-planner
Command: npx skills add https://github.com/opensquilla/opensquilla --skill paper-preference-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before an AI pipeline researches, outlines, or drafts an academic paper, it needs to know the user's writing preferences. This Skill extracts those preferences from the original request and produces a standardized preference brief, so downstream steps never guess or invent requirements.

Core Features & Use Cases

  • Dual Decision Modes: Chooses DIRECT mode for immediate generation with conservative academic defaults, or PREFERENCE_DRIVEN mode when the user supplies concrete requirements or requests an interview.
  • Structured Output Contract: Emits a fixed PAPER_PREFERENCES brief covering topic, audience, venue style, language, depth, citation style, emphasis, must-includes, avoidances, open questions, and defaults used.
  • Non-Blocking Interviews: When the user wants to discuss details first, it lists concise questions while still providing safe defaults so the pipeline can continue.
  • Use Case: A user asks for a survey paper on retrieval-augmented generation in author-year citation style; the Skill records those stated preferences exactly and marks all unspecified fields as defaults.

Quick Start

Extract the paper-writing preferences from my request to write a systems paper about vector databases for a practitioner audience.

Frequently Asked Questions about paper-preference-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I collect user preferences before generating an academic paper?

Run a preference-extraction step on the original user request before any research or drafting. It classifies the request as DIRECT or PREFERENCE_DRIVEN and outputs a structured brief covering topic, audience, venue style, citation style, and emphasis.

What is the difference between DIRECT and PREFERENCE_DRIVEN paper generation?

DIRECT mode applies conservative academic defaults when the user wants immediate generation or gives no interview instruction. PREFERENCE_DRIVEN mode preserves the user's stated details exactly and lists missing questions without blocking the pipeline.

Can preference extraction continue if the user wants an interview first?

Yes. When the user asks to discuss details first, the brief includes concise questions under QUESTIONS_FOR_USER while still providing safe defaults, so direct generation can continue in the same pipeline without blocking.

How does the planner avoid inventing paper requirements?

It never fabricates preferences that conflict with or embellish the request. Any unspecified field is filled with a conservative default and explicitly recorded under DEFAULTS_USED so downstream steps know it was not user-specified.

What output format does the paper preference brief use?

The output is plain text only in a fixed PAPER_PREFERENCES structure with fields for mode, topic, audience, venue style, language, depth, citation style, emphasis, must-include items, avoidances, questions, and defaults used. No Markdown fences or preamble are included.