Missed Digest Items

Decide Fit First

• Core job: 当用户敲 /missed 或自然语言问「digest 没推什么」时,调 missed_events 工具捞回 event-engine 的 delivery_log,把被主动筛掉的事件用人话报给用户。 用户提到「最近一周」「7 天」之类时把 since_h…
• Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
• Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

• Structure: The skill is organized around “职责”, “工具调用模板”, “输出格式约定(回给用户)”, “注意”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
• Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
• Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

• Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
• Invocation: Name Missed Digest Items directly; if the source includes slash commands, start with the command and then add task context.
• Validation: Start small and check whether the result follows “职责 / 工具调用模板 / 输出格式约定(回给用户)” before expanding.

Boundaries And Review

• Dependencies: It usually needs no extra API key, so start with a small validation task.
• Permissions: Declared permissions include read; ask the agent to state file, command, and rollback boundaries before acting.
• Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.