/install anchor-sheet
Anchor Sheet (evidence → write hooks) [NO PROSE]
Purpose: make “what to actually say” explicit:
- select quantitative snippets (numbers/percentages)
- select evaluation anchors (benchmarks/datasets/metrics)
- select limitations/failure hooks
This prevents the writer from producing paragraph-shaped but content-poor prose.
Inputs
outline/evidence_drafts.jsonlcitations/ref.bib
Outputs
outline/anchor_sheet.jsonl
Output format (outline/anchor_sheet.jsonl)
JSONL (one object per H3 subsection).
Required fields:
sub_id,titleanchors(list; each anchor hashook_type,text,citations, and optionalpaper_id/evidence_id/pointer)
Workflow
- Read
outline/evidence_drafts.jsonl. - Prefer anchors that contain:
- a number (%, counts, scores)
- an explicit benchmark/dataset/metric name
- an explicit limitation/failure statement
- Filter anchors to only citation keys present in
citations/ref.bib. - Write
outline/anchor_sheet.jsonl.
Quality checklist
- Every H3 has >=10 cite-backed anchors (A150++ hard target).
- At least 1 anchor contains digits when the evidence pack contains digits.
- No placeholders (
TODO/…/(placeholder)).
Consumption policy (for C5 writers)
Anchors are intended to prevent “long but empty” prose. Treat them as must-use hooks, not optional ideas.
Recommended minimums per H3 (A150++):
-
=3 protocol anchors (benchmark/dataset/metric/budget/tool access)
-
=3 limitation/failure hooks (concrete, not generic “future work”)
- If digits exist in the evidence pack: include >=1 cited numeric anchor (digit + citation in the same paragraph)
Note:
- Anchor text is trimmed for readability and does not include ellipsis markers (to reduce accidental leakage into prose).
Script
Quick Start
python scripts/run.py --helppython scripts/run.py --workspace workspaces/\x3Cws>
All Options
--workspace \x3Cdir>--unit-id \x3CU###>--inputs \x3Csemicolon-separated>--outputs \x3Csemicolon-separated>--checkpoint \x3CC#>
Examples
- Default IO:
python scripts/run.py --workspace workspaces/\x3Cws>
- Explicit IO:
python scripts/run.py --workspace workspaces/\x3Cws> --inputs "outline/evidence_drafts.jsonl;citations/ref.bib" --outputs "outline/anchor_sheet.jsonl"
Refinement marker (recommended; prevents churn)
When you are satisfied with anchor facts (and they are actually subsection-specific), create:
outline/anchor_sheet.refined.ok
This is an explicit "I reviewed/refined this" signal:
- prevents scripts from regenerating and undoing your work
- (in strict runs) can be used as a completion signal before writing
- 确保已安装 OpenClaw(本地或 Docker 部署)
- 在对话框中输入安装命令:
/install anchor-sheet - 安装完成后,直接呼叫该 Skill 的名称或使用
/anchor-sheet触发 - 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
Anchor Sheet 是什么?
Extract per-subsection “anchor facts” (NO PROSE) from evidence packs so the writer is forced to include concrete numbers/benchmarks/limitations instead of ge... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 143 次。
如何安装 Anchor Sheet?
在 OpenClaw 或 Claude Code 对话框中运行命令「/install anchor-sheet」即可一键安装,无需额外配置。
Anchor Sheet 是免费的吗?
是的,Anchor Sheet 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。
Anchor Sheet 支持哪些平台?
Anchor Sheet 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。
谁开发了 Anchor Sheet?
由 WILLOSCAR(@willoscar)开发并维护,当前版本 v1.0.0。