How do I install the Outline Refiner skill?

Run npx skillmds add majiayu000/outline-refiner in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Outline Refiner safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Outline Refiner?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Outline Refiner free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Outline Refiner?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Outline Refiner by majiayu000 — Agent Skill

Name: Outline Refiner
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Outline Refiner

Planner-pass coverage + redundancy report for an outline+mapping, producing `outline/coverage_report.md` and `outline/outline_state.jsonl`. **Trigger**: planner, dynamic outline, outline refinement, coverage report, 大纲迭代, 覆盖率报告. **Use when**: you have `outline/outline.yml` + `outline/mapping.tsv` and want a verifiable, NO-PROSE planner pass before writing. **Skip if**: you don't want any outline/mapping diagnostics (or you have a frozen/approved structure and will not change it). **Network**: none. **Guardrail**: NO PROSE; do not invent papers; only report coverage/reuse and propose structural actions as bullets.

majiayu000 54d42a6 2 files · 3.9 KB Updated Sep 9, 2026 567 repo stars

File contents

Outline Refiner (Planner pass, NO PROSE)

Goal: make the outline auditable by adding an explicit planner stage that answers:

Do we have enough mapped evidence per H3?
Are the same few papers reused everywhere?
Are subsection axes still generic/scaffold-y?
Is the outline likely to produce a paper-like structure (final ToC budget: ~6–8 H2; fewer, thicker H3s)?

This is a deterministic “planner” unit: it must not write survey prose.

Inputs

Required:

outline/outline.yml
outline/mapping.tsv

Optional (best-effort diagnosis; may be missing early in the pipeline):

outline/OUTLINE_BUDGET_REPORT.md (if present: explains recent merges; helps interpret mapping/coverage changes)
papers/paper_notes.jsonl (for evidence levels)
outline/subsection_briefs.jsonl (for axis specificity)
GOAL.md (for scope drift hints)

Outputs

outline/coverage_report.md (bullets + small tables; NO PROSE)
outline/outline_state.jsonl (append-only JSONL; one record per run)

Workflow (planner pass, NO PROSE)

Parse outline/outline.yml to enumerate H2 sections + H3 subsections (section sizing / budget).
- If outline/OUTLINE_BUDGET_REPORT.md exists, use it as the merge/change log so the coverage report can explain why structure changed.
Read outline/mapping.tsv and compute per-H3 coverage and reuse hotspots.
If papers/paper_notes.jsonl exists, summarize evidence levels (fulltext/abstract/title) for mapped papers.
If outline/subsection_briefs.jsonl exists, compute axis specificity (generic vs specific axes) per H3.
Optionally use GOAL.md to flag obvious scope drift (keywords not reflected in outline).
Write outline/coverage_report.md and append a run record to outline/outline_state.jsonl.

Freeze policy

If outline/coverage_report.refined.ok exists, the script will not overwrite outline/coverage_report.md.

Script

Quick Start

python .codex/skills/outline-refiner/scripts/run.py --help
python .codex/skills/outline-refiner/scripts/run.py --workspace workspaces/<ws>

All Options

--workspace <dir>: workspace root
--unit-id <U###>: unit id (optional; for logs)
--inputs <semicolon-separated>: override inputs (rare; prefer defaults)
--outputs <semicolon-separated>: override outputs (rare; prefer defaults)
--checkpoint <C#>: checkpoint id (optional; for logs)

Examples

Planner-pass diagnostics after section-mapper:
- python .codex/skills/outline-refiner/scripts/run.py --workspace workspaces/<ws>

Troubleshooting

Issue: report is missing evidence-level or axis-specificity columns

Cause:

Optional inputs are missing (no papers/paper_notes.jsonl and/or no outline/subsection_briefs.jsonl).

Fix:

Run paper-notes and/or subsection-briefs, then rerun outline-refiner.

---name: outline-refinerdescription: Planner-pass coverage + redundancy report for an outline+mapping, producing `outline/coverage_report.md` and `outline/outline_state.jsonl`. **Trigger**: planner, dynamic outline, outline refinement, coverage report, 大纲迭代, 覆盖率报告. **Use when**: you have `outline/outline.yml` + `outline/mapping.tsv` and want a verifiable, NO-PROSE planner pass before writing. **Skip if**: you don't want any outline/mapping diagnostics (or you have a frozen/approved structure and will not change it). **Network**: none. **Guardrail**: NO PROSE; do not invent papers; only report coverage/reuse and propose structural actions as bullets.--- # Outline Refiner (Planner pass, NO PROSE) Goal: make the outline *auditable* by adding an explicit planner stage that answers: - Do we have enough mapped evidence per H3? - Are the same few papers reused everywhere? - Are subsection axes still generic/scaffold-y? - Is the outline likely to produce a paper-like structure (final ToC budget: ~6–8 H2; fewer, thicker H3s)? This is a deterministic “planner” unit: it must not write survey prose. ## Inputs Required: - `outline/outline.yml` - `outline/mapping.tsv` Optional (best-effort diagnosis; may be missing early in the pipeline): - `outline/OUTLINE_BUDGET_REPORT.md` (if present: explains recent merges; helps interpret mapping/coverage changes) - `papers/paper_notes.jsonl` (for evidence levels) - `outline/subsection_briefs.jsonl` (for axis specificity) - `GOAL.md` (for scope drift hints) ## Outputs - `outline/coverage_report.md` (bullets + small tables; NO PROSE) - `outline/outline_state.jsonl` (append-only JSONL; one record per run) ## Workflow (planner pass, NO PROSE) 1. Parse `outline/outline.yml` to enumerate H2 sections + H3 subsections (section sizing / budget). - If `outline/OUTLINE_BUDGET_REPORT.md` exists, use it as the merge/change log so the coverage report can explain *why* structure changed. 2. Read `outline/mapping.tsv` and compute per-H3 coverage and reuse hotspots. 3. If `papers/paper_notes.jsonl` exists, summarize evidence levels (fulltext/abstract/title) for mapped papers. 4. If `outline/subsection_briefs.jsonl` exists, compute axis specificity (generic vs specific axes) per H3. 5. Optionally use `GOAL.md` to flag obvious scope drift (keywords not reflected in outline). 6. Write `outline/coverage_report.md` and append a run record to `outline/outline_state.jsonl`. ## Freeze policy - If `outline/coverage_report.refined.ok` exists, the script will not overwrite `outline/coverage_report.md`. ## Script ### Quick Start - `python .codex/skills/outline-refiner/scripts/run.py --help` - `python .codex/skills/outline-refiner/scripts/run.py --workspace workspaces/<ws>` ### All Options - `--workspace <dir>`: workspace root - `--unit-id <U###>`: unit id (optional; for logs) - `--inputs <semicolon-separated>`: override inputs (rare; prefer defaults) - `--outputs <semicolon-separated>`: override outputs (rare; prefer defaults) - `--checkpoint <C#>`: checkpoint id (optional; for logs) ### Examples - Planner-pass diagnostics after `section-mapper`: - `python .codex/skills/outline-refiner/scripts/run.py --workspace workspaces/<ws>` ## Troubleshooting ### Issue: report is missing evidence-level or axis-specificity columns **Cause**: - Optional inputs are missing (no `papers/paper_notes.jsonl` and/or no `outline/subsection_briefs.jsonl`). **Fix**: - Run `paper-notes` and/or `subsection-briefs`, then rerun `outline-refiner`.

Frequently asked questions