Agent skill · steipete
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.
What it needs
About 2k tokens when loaded.
What this skill does
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 sessionsspawn with runtime: "subagent", cleanup: "keep", and no collector mode. Have the child check knowledgestatus 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/knowledge-automation