Set up or repair recurring Knowledge ingestion by checking the authorized source, worker access, schedule, and timezone. Verify the job configuration and run it through the scheduler, including saved coverage and checkpoint behavior.
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.
Run score Not tested
See how to installThis skill schedules recurring ingestion into Knowledge. It checks existing automations and their run status, then creates or repairs a job as needed. It confirms the source, intended agent or vault, run frequency, and timezone, and verifies that the worker can access the intended scope. It reads back the job configuration and runs the job through the scheduler, checking that records are saved and checkpoints are updated.
Use it when you want a regularly updated source ingested into Knowledge, or when an existing ingestion job has stopped working. It can also verify access rights and check for duplicate results through an actual scheduled run, rather than relying on the configuration alone.
Scheduling requires a compatible OpenClaw environment and owner delegation to the target vault. Running the workflow interactively does not verify that it works through the scheduler. If access is lost, writes must stop until delegation is authorized again.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 26, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
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.
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.
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:
knowledge-source-ingest for incremental coverage/reconciliation where
applicable, then knowledge-ingest or knowledge-meeting-ingest for content.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.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.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Set up and authenticate the 1Password CLI, then supply stored passwords and API keys to commands or configuration. The skill covers desktop integration, service accounts, and interactive sign-in while keeping secrets out of chat and logs.
Route requests from OpenClaw to external coding agents such as Claude Code or Cursor. Start or continue sessions using ACP, a protocol for connecting agents, or relay prompts directly through acpx while preserving conversation context.
Add a model provider to OpenClaw and verify it with a real response. The skill validates configuration, keeps credentials in environment or file references, and reports test results and any default model changes.
Prepare an agent activity transcript for a GitHub pull request or issue. Extract relevant prompts, decisions, and results from local logs, remove sensitive material, and preview the edited record before separately authorized publication.
Manage Apple Notes on macOS through memo, a command-line tool. Create, browse, search, edit, delete, and move notes between folders, or export selected notes to HTML or Markdown for use outside the app.
Manage Apple Reminders from your Mac with remindctl, a terminal tool. View tasks by date, add or edit reminders, organize lists, and mark tasks complete or delete them, including personal to-dos that sync to iOS.