Agent skill

outline-builder

Convert a taxonomy (`outline/taxonomy.yml`) into a bullet-only outline (`outline/outline.yml`) with sections/subsections. **Trigger**: outline builder, bullet outline, outline.yml, 大纲生成, bullets-only. **Use when**: structure 阶段（NO PROSE），已有 taxonomy，需要生成可映射/可写作的章节与小节骨架（每小节≥3 bullets）。 **Skip if**: 已经有批准过且可映射的 outline（避免无意义 churn）。 **Network**: none. **Guardrail**: bullets-only；移除 TODO/模板语句；每小节至少 3 个可检查 bullets。

View SKILL.md on GitHub Repository
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/outline-builder

SKILL.md

Outline Builder

Build outline/outline.yml from either:

  • outline/taxonomy.yml (legacy H3-first compatibility path)
  • outline/chapter_skeleton.yml + outline/section_briefs.jsonl (section-first transition path)

Compatibility mode is active: this migration keeps the current output contract while moving intro/related defaults, Stage A bullet templates, and domain-specific comparison framing into references/ and assets/.

Load Order

Always read:

  • references/overview.md
  • references/stage_a_contract.md

Read by task:

  • references/intro_related_patterns.md when changing Introduction / Related Work defaults
  • references/examples_good.md and references/examples_bad.md for bullet calibration

Machine-readable asset:

  • assets/outline_defaults.yaml

Inputs

Required:

  • outline/taxonomy.yml

Optional human calibration only:

  • ref/agent-surveys/STYLE_REPORT.md
  • ref/agent-surveys/text/

Output

Keep the current output contract:

  • outline/outline.yml

Compatibility mode

Current mode is reference-first with script compatibility:

  • front-chapter defaults live in assets/outline_defaults.yaml
  • Stage A bullet defaults and comparison-axis packs live in assets/outline_defaults.yaml
  • examples and boundary rules live in references/
  • scripts/run.py still owns outline materialization, section-first input selection, and placeholder-safe overwrite behavior

Script boundary

Use scripts/run.py only for:

  • loading taxonomy or section-first structure inputs plus the defaults asset
  • rendering the outline skeleton deterministically
  • preserving existing non-placeholder outlines
  • choosing comparison-axis packs from machine-readable defaults

Do not treat the script as the main place for:

  • domain framing for Introduction / Related Work
  • long bullet banks or writing exemplars
  • prompt-heavy guidance about how a good outline should read

Output shape rules

Keep these stable:

  • outline/outline.yml is a YAML list
  • Introduction and Related Work remain the first two H2 sections
  • each H3 subsection contains the Stage A bullets: Intent: / RQ: / Evidence needs: / Expected cites:
  • each H3 subsection adds several topic-specific bullets after the Stage A fields
  • the helper never overwrites non-placeholder user work

Quick Start

  • python .codex/skills/outline-builder/scripts/run.py --help
  • python .codex/skills/outline-builder/scripts/run.py --workspace <workspace_dir>

Execution notes

When running this skill in compatibility mode, scripts/run.py currently reads:

  • outline/taxonomy.yml, or
  • outline/chapter_skeleton.yml + outline/section_briefs.jsonl
  • assets/outline_defaults.yaml

The optional style references under ref/agent-surveys/ are for human calibration only:

  • use ref/agent-surveys/STYLE_REPORT.md to sanity-check chapter counts / thickness
  • skim ref/agent-surveys/text/ only to calibrate structure rather than wording

Script

Quick Start

  • python .codex/skills/outline-builder/scripts/run.py --workspace <workspace_dir>

All Options

  • --workspace <dir>
  • --unit-id <id>
  • --inputs <path1;path2>
  • --outputs <path1;path2>
  • --checkpoint <C*>

Examples

  • python .codex/skills/outline-builder/scripts/run.py --workspace workspaces/<ws>

Troubleshooting

  • If Related Work still carries domain-specific framing, patch assets/outline_defaults.yaml before changing Python.
  • If subsection bullets feel generic, review references/stage_a_contract.md and references/examples_good.md.
  • If the outline is structurally valid but too fragmented, reroute to outline-budgeter rather than expanding this script.

Recommended Agent Skills

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