Agent skill

opener-variator

Rewrite subsection openers so they stop reading like a generated table-of-contents: remove \"overview/narration\" stems and reduce repeated opener cadences across H3s. **Trigger**: opener variator, opener rewrite, rewrite openers, overview opener, 开头改写, 小节开头, 去overview, 去旁白. **Use when**: `writer-selfloop` is PASS but flags repeated opener stems / overview narration in `output/WRITER_SELFLOOP_TODO.md`, or the draft still has a subtle “generator cadence”. **Skip if**: you are pre-C2 (NO PROSE), or the section is evidence-thin (route upstream; don’t stylize filler). **Network**: none. **Guardrail**: do not invent facts; do not add/remove/move citation keys; do not move citations across subsections; keep meaning intact.

Stars 377
Forks 25

Install this agent skill to your Project

npx add-skill https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/opener-variator

SKILL.md

Opener Variator (H3 first paragraph rewrite)

Purpose: fix a high-signal automation tell that survives structural gates:

  • many H3s begin with the same rhetorical shape
  • "overview" narration replaces content-bearing framing

This skill is intentionally narrow:

  • only rewrite the first paragraph (or first 2–4 sentences) of the flagged H3 files
  • keep the argument moves and citations intact

Inputs

Required:

  • output/WRITER_SELFLOOP_TODO.md (Style Smells section)
  • the referenced sections/S<sub_id>.md files

Optional (helps you stay aligned):

  • outline/writer_context_packs.jsonl (use opener_mode, tension_statement, thesis)

Outputs

Note: keep this as an openers-last pass. Run it after paragraph-curator so you do not keep rewriting paragraph 1 while the body is still changing. Current compatibility policy: the script is marker-only; substantive opener repair should happen upstream in subsection-writer / chapter-lead-writer, not through blind regex rewriting.

  • Updated sections/S<sub_id>.md files (still body-only; no headings)

Workflow (route from the self-loop report)

  1. Open output/WRITER_SELFLOOP_TODO.md and locate ## Style Smells.
  2. Treat the flagged sections/S*.md list as the only scope for this pass.
  3. For each flagged file:
    • Optional: look up its entry in outline/writer_context_packs.jsonl and read opener_mode / tension_statement / thesis to stay aligned.
    • Do the real rewrite upstream in subsection-writer or chapter-lead-writer; do not rely on blind local regex passes.
    • Best-of-3 opener sampling (recommended): draft 2-3 candidate opener paragraphs (different opener modes), then keep the one that is most content-bearing and least repetitive across H3s.
  4. Rerun writer-selfloop and confirm the Style Smells list shrinks.

Role prompt: Opener Editor (paper voice)

text
You are rewriting the opening paragraph of a survey subsection.

Goal:
- replace narration/overview openers with a content-bearing framing
- vary opener cadence across subsections so the paper reads authored

Constraints:
- do not invent facts
- do not add/remove/move citation keys
- do not change the subsection’s thesis

Checklist:
- sentence 1 is content-bearing (tension/decision/failure/protocol/contrast), not “what we do in this section”
- paragraph 1 ends with a clear thesis/takeaway
- no slide navigation (“Next, we…”, “In this subsection…”, “This section provides an overview…“)

What to delete (high-signal narration)

Rewrite immediately if the opener contains any of:

  • “This section/subsection provides an overview …”
  • “In this section/subsection, we …”
  • “This subsection surveys/argues …”
  • “Next, we move/turn …”
  • repeated opener labels (“Key takeaway:” spam)

What to replace with (opener moves)

Pick one opener mode per H3 (the writer pack may suggest opener_mode). Do not copy labels; write as natural prose.

Allowed opener moves (choose 1; keep it concrete):

  • Tension-first: state the real trade-off; why it matters; end with thesis.
  • Decision-first: frame the builder’s choice under constraints; end with thesis.
  • Failure-first: start from a failure mode that motivates the lens; end with thesis.
  • Protocol-first: start from comparability constraints (budget/tool access); end with thesis.
  • Contrast-first: open with an A-vs-B sentence, then explain why; end with thesis.
  • Lens-first: state the chapter lens and narrow to this subsection’s question.

Mini examples (paraphrase; do not copy)

Bad (overview narration):

  • This subsection provides an overview of tool interfaces for agents.

Better (content-bearing):

  • Tool interfaces define what actions are executable; interface contracts therefore determine which evaluation claims transfer across environments.

Bad (process narration):

  • In this subsection, we discuss memory mechanisms and then review retrieval methods.

Better (tension-first):

  • Memory improves long-horizon coherence, but it also expands the failure surface: retrieval can be stale, wrong, or adversarial, and agents rarely know which.

Done checklist

  • No flagged file starts with “overview/narration” stems.
  • Paragraph 1 ends with a thesis/takeaway (same meaning).
  • Citation keys are unchanged (no adds/removes/moves).
  • writer-selfloop still PASSes and Style Smells shrink.

Script

Quick Start

  • python .codex/skills/opener-variator/scripts/run.py --workspace workspaces/<ws>

All Options

  • --workspace <dir> (required)
  • --unit-id <U###>
  • --inputs <semicolon-separated>
  • --outputs <semicolon-separated>
  • --checkpoint <C#>

Examples

  • Rewrite openers in a survey workspace:
    • python .codex/skills/opener-variator/scripts/run.py --workspace workspaces/survey-llm-agents

Expand your agent's capabilities with these related and highly-rated skills.

WILLOSCAR/research-units-pipeline-skills

thesis-compile-review

对中文毕业论文进行编译、warning 分级、模板模式检查、数据与引用复查,并把问题回写成可继续迭代的 review checklist。 **Trigger**: 毕业论文编译检查, thesis compile review, warning 分级, 终稿复查, main.pdf 检查. **Use when**: 论文已经回写到 TeX 交付层,需要确认是否真正达到“可提交”的质量,而不是只做到能编译。 **Skip if**: 还处于中间层重构阶段,`chapters/*.tex` 尚未形成稳定交付稿。 **Network**: none. **Guardrail**: 不在这里重构章节主线;如果发现结构问题,明确回退到上游修复。

377 25
Explore
WILLOSCAR/research-units-pipeline-skills

front-matter-writer

Write the survey's front matter files (Abstract, Introduction, Related Work, Discussion, Conclusion) in paper voice, with high citation density and a single evidence-policy paragraph. **Trigger**: front matter writer, introduction writer, related work writer, abstract writer, discussion writer, conclusion writer, 引言, 相关工作, 摘要, 讨论, 结论. **Use when**: you are in C5 (prose allowed) and need the paper-like shell to stop the draft reading like stitched subsections. **Skip if**: `Approve C2` is missing in `DECISIONS.md`, or `citations/ref.bib` is missing. **Network**: none. **Guardrail**: no invented facts/citations; no pipeline jargon in final prose; no repeated evidence disclaimers; only use keys present in `citations/ref.bib`.

377 25
Explore
WILLOSCAR/research-units-pipeline-skills

thesis-question-list

维护中文毕业论文的 `codex_md/question_list.md`:把本轮问题、边界、优先级、协作方案和验收口径结构化,作为整条 thesis pipeline 的控制面。 **Trigger**: 毕业论文问题清单, thesis question list, 论文修改清单, 本轮目标, 结构问题梳理, review问题整理. **Use when**: 你已经有一批材料或上一轮 review 结果,需要明确这一轮到底修什么、不修什么,并给后续重构与编译复查提供统一入口。 **Skip if**: 当前只是在做一次性局部措辞修改,且没有形成新一轮结构/证据/编译问题。 **Network**: none. **Guardrail**: 不在这里写正文;不把问题单写成长篇散文;每条问题必须可执行、可验收。

377 25
Explore
WILLOSCAR/research-units-pipeline-skills

novelty-matrix

Create a novelty/prior-work matrix comparing the submission’s contributions against related work (overlaps vs deltas). **Trigger**: novelty matrix, prior-work matrix, overlap/delta, 相关工作对比, 新颖性矩阵. **Use when**: peer review 中评估 novelty/positioning,需要把贡献与相关工作逐项对齐并写出差异点证据。 **Skip if**: 缺少 claims(先跑 `claims-extractor`)或你不打算做新颖性定位分析。 **Network**: none (retrieval of additional related work is out-of-scope unless provided). **Guardrail**: 明确 overlap 与 delta;尽量给出可追溯证据来源(来自稿件/引用/作者陈述)。

377 25
Explore
WILLOSCAR/research-units-pipeline-skills

protocol-writer

Write a systematic review protocol into `output/PROTOCOL.md` (databases, queries, inclusion/exclusion, time window, extraction fields). **Trigger**: protocol, PRISMA, systematic review, inclusion/exclusion, 检索式, 纳入排除. **Use when**: systematic review pipeline 的起点(C1),需要先锁定 protocol 再开始 screening/extraction。 **Skip if**: 不是做 systematic review(或 protocol 已经锁定且不允许修改)。 **Network**: none. **Guardrail**: protocol 必须包含可执行的检索与筛选规则;需要 HUMAN 签字后才能进入 screening。

377 25
Explore
WILLOSCAR/research-units-pipeline-skills

rubric-writer

Write a rubric-based peer review report (`output/REVIEW.md`) using extracted claims and evidence gaps (novelty/soundness/clarity/impact). **Trigger**: rubric review, referee report, peer review write-up, 审稿报告, REVIEW.md. **Use when**: peer-review pipeline 的最后阶段(C3),已有 `output/CLAIMS.md` + `output/MISSING_EVIDENCE.md`(以及可选 novelty matrix)。 **Skip if**: 上游产物未就绪(claims/evidence gaps 缺失)或你不打算输出完整审稿报告。 **Network**: none. **Guardrail**: 给可执行建议(actionable feedback),并覆盖 novelty/soundness/clarity/impact;避免泛泛而谈。

377 25
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results