tighten reader digest skill rules

2026-04-02 10:25:27 +08:00
parent 12e766952c
commit 1de4a08200
2 changed files with 55 additions and 0 deletions
@@ -14,11 +14,14 @@ Run the reader-based daily digest as a fixed SOP. Treat this skill as the orches
 - **Do not generate the daily digest from examples or placeholder data. Always require a real payload first.**
 - Generate the daily digest markdown from the payload in OpenClaw.
 - Split outputs into a **public digest** for Hugo and an **internal review digest** for chat / operator decision-making.
+- **Public digest and internal review digest are orchestration-layer outputs, and by default are generated by the current OpenClaw session model rather than inheriting reader `LLM_*` settings.**
 - Publish only the public digest to Hugo.
 - Report the internal review digest back to the user in chat.
 - **Do not upload the full daily digest to IMA.**
 - **Do not upload any selected article summary to IMA until the user has explicitly confirmed the selection.**
 - Upload **only user-selected articles** to IMA as individual knowledge notes.
+- **The formal IMA upload object must be the generated single-article summary content (Markdown note / note content), not the original article webpage URL.**
+- **Importing original article URLs into IMA can be used only as temporary source collection, and does not count as completing the daily summary deposition flow.**
 - Default IMA target for daily single-article summaries is the `daily` knowledge base.
 - Resolve that default target from reader `.env` (`IMA_DAILY_KNOWLEDGE_BASE_ID`, `IMA_DAILY_KNOWLEDGE_BASE_NAME`) and verify it at runtime before upload.
 - If the configured daily knowledge base is missing, try to locate it by name; if still missing, create `daily` and continue.
@@ -81,10 +84,15 @@ Public digest writing rules:
 - Use `digest-brief.json` as the default source when available.
 - Treat it as a public-only view that already excludes non-keep items.
 - Keep the tone suitable for public browsing and Hugo publishing.
+- Style should follow `references/public-digest-example.md` as the default public-writing example.
+- Public digest is a **public reading draft / editor-style public note**, not a workflow report.
+- In `今日概览`, focus on the day’s topic lines, shared signals, and broader industry movement; do **not** describe filtering mechanics or internal selection process.
 - Do **not** expose internal workflow labels or operator language such as `待确认`, `建议沉淀到 IMA`, `keep/review/drop`, or `selection_decision`.
+- Explicitly avoid wording such as `共筛出`, `候选`, `保留`, `入选`, `待确认`, `建议沉淀` in public digest.
 - Prefer concise but information-dense writing.
 - For each item under `今日重点`, include not only summary and highlights, but also one short editor-style value sentence, for example: `这篇内容更值得关注的原因在于……`.
 - When rendering highlights in public digest, prefer a short label such as `值得关注：` followed by one item per line, instead of packing multiple points into a single long sentence.
+- In `延伸阅读`, every item must include source attribution in the form: `- [标题](url)｜来源`.

 Recommended **internal review digest** structure:

@@ -164,6 +172,18 @@ Default target knowledge base for this phase:
 - Verify the target at runtime through IMA APIs / skill lookups before upload
 - If the configured target does not exist, try to find `daily` by name; if still absent, create it and continue

+Completion criteria for this phase:
+
+- a selected article has been summarized from extracted content
+- a single-article Markdown summary file has been generated
+- the object uploaded into IMA is the summary content / note content derived from that Markdown
+- the upload target is the `daily` knowledge base unless the user explicitly requests otherwise
+
+Do not treat the following as completion of summary deposition:
+
+- importing the original article webpage URL into IMA
+- storing the original article only as source material without the generated summary content
+
 Do not upload:

 - the full daily digest