跳到正文
cccskills
免费在 GitHub 公开

knowledge-automation

Create scheduled Knowledge ingestion automations with a verified worker, private-vault authority, and an end-to-end scheduled run. Use when asked to schedule or repair recurring ingestion from any source.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md4.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Knowledge automation

  1. Identify the job. Inspect existing automations before creating a replacement. Confirm the authorized source, intended agent/vault, cadence and timezone. Verify the running OpenClaw installation and its current automation CLI/schema; a different CLI on PATH may target an incompatible installation. Finish with the intended job and any existing checkpoint identified.

  2. Establish the worker's authority. For owner-private ingestion, use the verified OpenClaw 2026.9.8 composition: an operator-authored named-session automation targeting a retained, genuinely owner-delegated OpenClaw session. From the authorized owner conversation, use sessions_spawn with runtime: "subagent", cleanup: "keep", and no collector mode. Have the child check knowledge_status for the intended scope/agent/vault and read a known existing record when available; retain its returned session key. This is the persistent ingestion worker, not an internal research subagent. Operator scheduling alone does not grant private access. A fresh named session, detached current run, or headless script is not a substitute for delegation. Finish with a retained worker that has demonstrated intended access.

  3. Create the host automation. Use the verified installation's supported operator CLI (openclaw automations add, or edit the intended existing job), with an agent-turn message and --session "session:<returned-session-key>". Requester-scoped automation creation cannot target another conversation's workspace. If operator scheduling is unavailable, report that blocker; never fabricate owner context or edit stored authority receipts. Set the requested schedule/timezone, a sufficient timeout and a finite tool allow-list for the workflow. Discover the scheduled runtime's actual execution tools rather than assuming interactive tool names. Read back the target and job configuration.

    The job message must require, on every run:

    • Intended Knowledge scope/access preflight before acquisition or writes.
    • Fresh acquisition using the source's existing authorized credential route.
    • knowledge-source-ingest for incremental coverage/reconciliation where applicable, then knowledge-ingest or knowledge-meeting-ingest for content.
    • The selected workflow's verification before committing its checkpoint; preserve retryable work and the previous checkpoint on failure.
    • AUTOMATION_FAILED on its own first line for unresolved failure, followed by the reason. NO_REPLY is for successful no-change runs, not hidden errors.
  4. Prove the scheduled path. Run through the scheduler, not just interactive tools. Require a terminal run receipt, correct vault access, verified saved coverage and checkpoint readback. Repeat with unchanged source content and verify no duplicate publication. Confirm a real timer firing as well; job creation or source listing alone does not prove ingestion. When replacing a job, disable the old one after verification and confirm only one is active. Report any untested publication or repeat behavior explicitly.

  5. Report operation and limits. Give the job, cadence, next run and verified outcome. Check result delivery and failure alerts separately: quiet delivery (delivery.mode: "none") leaves results in automation history and does not imply proactive notifications. Parent reset/removal/reassignment revokes delegation; worker reset or removal can also invalidate access. Check the effective reset/retention policy. On lost authority, stop writes and checkpoint advancement; recover only through a newly authorized owner delegation and supported retargeting, never self-reauthorization.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Save durable preferences, decisions, project facts, commitments, and lessons cheaply with knowledge_remember, or short notes and page updates with attribution and readback. Use for explicit saves or agent-driven remembering when Knowledge is the selected memory provider.

中文简介正在准备中。当前显示原文说明。

openclaw/knowledge22026年10月21日 更新

Correct or withdraw specific saved Knowledge claims, explicit relationships, or pages at the user's request, preserving provenance and inspecting affected knowledge. Use for “that's wrong”, “retract that”, or a Knowledge chat reference; not automatic contradiction resolution or physical erasure.

中文简介正在准备中。当前显示原文说明。

openclaw/knowledge22026年10月21日 更新

Resolve and enrich Knowledge people, companies, projects, and concepts during an authorized ingestion or entity update, with sourced State, timelines, and back-links. Read-only identity questions do not authorize writes.

中文简介正在准备中。当前显示原文说明。

openclaw/knowledge22026年10月21日 更新

Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links. Routes meetings to knowledge-meeting-ingest and short thoughts to knowledge-capture.

中文简介正在准备中。当前显示原文说明。

openclaw/knowledge22026年10月21日 更新

Ingest meeting transcripts from any recorder into Knowledge with attendee enrichment, timeline merge, supported decisions and commitments, and verification of substance and sequence. Summary-only input is not a verified meeting ingestion.

中文简介正在准备中。当前显示原文说明。

openclaw/knowledge22026年10月21日 更新

Find and answer from saved Knowledge vault pages with source citations. Use for questions about stored documents, meetings, people, or projects; not for recalling conversation history or searching the web.

中文简介正在准备中。当前显示原文说明。

openclaw/knowledge22026年10月21日 更新

查看 openclaw 的全部技能

报告此技能的问题