docs: update reader digest skill for MCP workflow path
This commit is contained in:
@@ -9,7 +9,9 @@ Run the reader-based daily digest as a fixed SOP. Treat this skill as the orches
|
||||
|
||||
## Core Rules
|
||||
|
||||
- Run `reader` / MCP for upstream fetching, extraction, filtering, payload generation, and selected-article post-processing.
|
||||
- Run `reader` as the formal upstream MCP workflow service for fetching, extraction, filtering, payload generation, result reading, and selected-article post-processing.
|
||||
- Prefer MCP workflow operations over direct long-lived CLI execution. Treat CLI as debug / fallback, not the default production path.
|
||||
- For reader run observation and result reading, prefer MCP tools such as status / payload / report queries instead of having OpenClaw or this skill hand-build reader output paths.
|
||||
- **For normal production runs, mark processed FreshRSS items as read. Only skip mark-read when the user explicitly says the run is debug/test/validation.**
|
||||
- **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.
|
||||
|
||||
Reference in New Issue
Block a user