paper-revision-author
# paper-revision-author This Claude Code skill consolidates independently drafted research paper sections into a coherent LaTeX body document. Use it after sections have been written separately and an outline approved to unify terminology, eliminate redundancy, enforce consistent depth and audience level across Introduction, Method, Results, and Discussion sections, and ensure proper citation distribution while preserving all figures and meeting minimum length requirements for publication-ready output.
git clone --depth 1 https://github.com/opensquilla/opensquilla /tmp/paper-revision-author && cp -r /tmp/paper-revision-author/src/opensquilla/skills/bundled/paper-revision-author ~/.claude/skills/paper-revision-authorSKILL.md
# paper-revision-author
You are revising the body of a research paper after independent section
drafting.
## Inputs you'll receive
- `topic`: the paper topic.
- `paper_preferences`: mode, audience, venue style, language, depth, emphasis,
must-include items, avoid items, and defaults chosen for this paper.
- `outline`: the approved outline.
- `citation_plan`: claim-to-citation plan.
- `introduction`, `method`, `results`, `discussion`: LaTeX section drafts.
## Output contract
Pure LaTeX fragment only. Return the revised body in this exact section order:
```
\section{Introduction}
...
\section{Method}
...
\section{Results}
...
\section{Discussion}
...
```
## Hard rules
- Preserve all required figure blocks and labels from the results draft.
- Preserve at least 20 distinct valid citation keys across the full body.
- Enforce `paper_preferences` consistently across all sections, especially
audience, depth, emphasis, must-include items, and avoid-list constraints.
- Remove duplicate paragraphs and repeated setup explanations.
- Make terminology, contribution statements, metrics, and baselines consistent.
- Keep the body long enough for the full paper to compile to 10+ pages.
- Do not include an abstract, preamble, bibliography, commentary, Markdown, or
code fences.Submit audio or video for multilingual dubbing, poll status, and download dubbed audio. Use when the user asks for dubbing, 多语言配音, 视频翻译配音, 译制片, or wants a source clip dubbed into another language.
Generate a structured short-video shooting script from a topic. Emits a strict, machine-parseable shot list (3 shots by default) with image prompt + video prompt + voiceover + on-screen text per shot. Trigger when the user asks for a video script, 分镜, 短视频文案, AI视频, 短剧脚本, or wants visual prompts ready for image/video generation.
Use when the user asks to schedule recurring tasks, one-off reminders, timers, or cron-style jobs through the OpenSquilla cron tool.
Multi-round research with explicit methodology, evidence tracking, and citation-tagged synthesis. Trigger on 'deep dive', 'research report', 'literature review', 'investigate X across sources', 'multi-round investigation'. Distinct from the `summarize` skill, which is a single-pass condensation; this skill maintains a state file across iterations, tracks coverage, and produces a long-form report with per-claim citations. Three execution stages: plan (scope into sub-questions), iterate (record evidence per round), compile (synthesize report). The skill itself does not fetch the web — it tells the host agent which fetches to perform via OpenSquilla's existing web tools, and records what comes back.
Read, edit, or create Microsoft Word `.docx` files. Trigger this skill whenever the user mentions a Word document, .docx file, contract, report, brief, memo, or asks to extract text, modify an existing doc, generate one from a brief, or audit tracked changes. Three execution paths: text-and-structure extraction, in-place edit-by-run (preserves styles), and create-from-scratch with python-docx. Falls back to OOXML unzip-and-patch for layout work python-docx cannot reach.
Capture the current git diff (staged, working-tree, or staged file list) as text. Direct shell call for workflows that need repository diffs without an LLM agent loop.
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
Query the per-turn DecisionEntry log for skill co-occurrence patterns, meta-skill usage stats, and the router fixture corpus. Returns a JSON summary suitable for downstream LLM consumption. Used by meta-skill-creator's harvest step but also useful standalone for 'which skills did I use most this week?'