Agent skill
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`.
Install this agent skill to your Project
npx add-skill https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/front-matter-writer
SKILL.md
Front Matter Writer (compatibility router)
Purpose: produce the paper-level shell while preserving the current output contract and approval gate.
Load Order
Always read:
references/overview.md
Read by task:
references/abstract_archetypes.mdforsections/abstract.mdreferences/context_projection.mdwhen adjusting how chapter briefs are projected into Introduction / Related Work contextreferences/introduction_jobs.mdfor Introduction body filesreferences/related_work_positioning.mdfor Related Work body filesreferences/discussion_conclusion_patterns.mdforsections/discussion.mdandsections/conclusion.mdreferences/forbidden_stems.mdbefore revising any reader-facing prosereferences/examples_good.mdandreferences/examples_bad.mdfor calibration only
Machine-readable assets:
assets/front_matter_context.schema.jsonassets/front_matter_context_schema.json(compatibility alias for checklist-aligned naming)assets/front_matter_contract.jsonassets/front_matter_templates.jsonassets/front_matter_context_projection.json
Inputs
Required:
DECISIONS.mdwithApprove C2outline/outline.ymloutline/mapping.tsvcitations/ref.bib
Optional but useful:
GOAL.mdqueries.mdpapers/retrieval_report.mdpapers/core_set.csvoutline/coverage_report.mdoutline/writer_context_packs.jsonl
Outputs
Keep the current output contract:
sections/abstract.mdsections/S<sec_id>.mdfor front-matter H2 bodiessections/discussion.mdsections/conclusion.mdoutput/FRONT_MATTER_REPORT.mdoutput/FRONT_MATTER_CONTEXT.json
Compatibility mode
Current mode is reference-first with script compatibility:
- writing guidance lives in
references/ - the structured job contract lives in
assets/front_matter_contract.json - the hook bank used by the script lives in
assets/front_matter_templates.json scripts/run.pystill owns approval checks, metadata parsing, deterministic hook selection, file emission, and context-sidecar writing
That means:
- preserve current file shapes and approval behavior
- treat the assets as the active semantic source for section jobs, hook banks, and render guardrails
- avoid moving prose policy back into
SKILL.md
Script boundary
Use scripts/run.py as a deterministic helper for:
- approval gate enforcement
- front-matter file discovery / path selection
- metadata extraction
- rendering from
assets/front_matter_contract.json+assets/front_matter_templates.json - writing the report and context sidecar
Do not treat the script as the main place for long-form writing guidance.
Output shape rules
Keep these stable:
sections/abstract.mdstarts with## Abstractor## 摘要- Introduction / Related Work
sections/S<sec_id>.mdfiles are body-only sections/discussion.mdincludes## Discussionsections/conclusion.mdincludes## Conclusion- methodology note appears once in normal prose, not as pipeline/process narration
Quick Start
python .codex/skills/front-matter-writer/scripts/run.py --workspace workspaces/<ws>
Troubleshooting
- If the front matter sounds narrated, reload
references/forbidden_stems.mdandreferences/examples_bad.md. - If Related Work turns into a survey list, reload
references/related_work_positioning.md. - If the asset and the references drift, fix the asset/routing inside this skill package rather than expanding
SKILL.mdagain.
Execution notes
When running this skill in compatibility mode, scripts/run.py currently reads these inputs directly:
DECISIONS.mdforApprove C2outline/outline.ymlto resolve Introduction / Related Work section idsoutline/mapping.tsvfor front-matter citation placement contextcitations/ref.bibfor citation-key scopeGOAL.md,queries.md,papers/retrieval_report.md,papers/core_set.csv,outline/coverage_report.md, andoutline/writer_context_packs.jsonlas optional context sources
Script
Quick Start
python .codex/skills/front-matter-writer/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/front-matter-writer/scripts/run.py --workspace workspaces/<ws>
Troubleshooting
- If
DECISIONS.mdlacksApprove C2, the script will write a checkpoint block and exit. - If
citations/ref.biboroutline/outline.ymlis missing, restore those inputs before rerunning. - If the front matter feels too template-like, inspect the hook banks / section job graph before touching the script.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
thesis-compile-review
对中文毕业论文进行编译、warning 分级、模板模式检查、数据与引用复查,并把问题回写成可继续迭代的 review checklist。 **Trigger**: 毕业论文编译检查, thesis compile review, warning 分级, 终稿复查, main.pdf 检查. **Use when**: 论文已经回写到 TeX 交付层,需要确认是否真正达到“可提交”的质量,而不是只做到能编译。 **Skip if**: 还处于中间层重构阶段,`chapters/*.tex` 尚未形成稳定交付稿。 **Network**: none. **Guardrail**: 不在这里重构章节主线;如果发现结构问题,明确回退到上游修复。
thesis-question-list
维护中文毕业论文的 `codex_md/question_list.md`:把本轮问题、边界、优先级、协作方案和验收口径结构化,作为整条 thesis pipeline 的控制面。 **Trigger**: 毕业论文问题清单, thesis question list, 论文修改清单, 本轮目标, 结构问题梳理, review问题整理. **Use when**: 你已经有一批材料或上一轮 review 结果,需要明确这一轮到底修什么、不修什么,并给后续重构与编译复查提供统一入口。 **Skip if**: 当前只是在做一次性局部措辞修改,且没有形成新一轮结构/证据/编译问题。 **Network**: none. **Guardrail**: 不在这里写正文;不把问题单写成长篇散文;每条问题必须可执行、可验收。
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;尽量给出可追溯证据来源(来自稿件/引用/作者陈述)。
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。
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;避免泛泛而谈。
arxiv-search
Retrieve paper metadata from arXiv using keyword queries and save results as JSONL (`papers/papers_raw.jsonl`). **Trigger**: arXiv, arxiv, paper search, metadata retrieval, 文献检索, 论文检索, 拉取元数据, 离线导入. **Use when**: 需要一个初始论文集合(survey/snapshot 的 Stage C1),来源为 arXiv(在线检索或离线导入 export)。 **Skip if**: 已经有可用的 `papers/papers_raw.jsonl`,或数据源不是 arXiv。 **Network**: 在线检索需要网络;离线 `--input <export.*>` 不需要网络。 **Guardrail**: 只做 metadata;不要在 `output/` 写长 prose。
Didn't find tool you were looking for?