MCP.Market

knowledge-automation skill

by openclaw·openclaw/openclaw·394k stars·MIT

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.

A100/100content scan

Is the knowledge-automation skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-11-01.

No findings.

Install the knowledge-automation skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/openclaw/openclaw.git /tmp/openclaw
mkdir -p ~/.claude/skills
cp -r /tmp/openclaw/extensions/knowledge/skills/knowledge-automation ~/.claude/skills/knowledge-automation
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Knowledge automation

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.

  1. Identify the job. Inspect existing automations before creating a replacement.

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.

  1. Establish the worker's authority. For owner-private ingestion, use the

operator CLI (openclaw automations add, or edit the intended existing job), with an agent-turn message and --session "session:". 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.

  1. Create the host automation. Use the verified installation's supported

The job message must require, on every run:

applicable, then knowledge-ingest or knowledge-meeting-ingest for content.

  • 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

preserve retryable work and the previous checkpoint on failure.

  • The selected workflow's verification before committing its checkpoint;

by the reason. NO_REPLY is for successful no-change runs, not hidden errors.

  • AUTOMATION_FAILED on its own first line for unresolved failure, followed

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.

  1. Prove the scheduled path. Run through the scheduler, not just interactive

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.

  1. Report operation and limits. Give the job, cadence, next run and verified

More skills from openclaw/openclaw

  • A1passwordSet up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.
  • Aacp-routerRoute plain-language requests for Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Grok Build, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either OpenClaw ACP runtime sessions or direct acpx-driven sessions ("telephone game" flow). For coding-agent thread requests, read this skill first, then use only `sessions_spawn` for thread creation. Codex chat binding defaults to the native Codex app-server plugin unless ACP is explicit or background spawn needs ACP.
  • Aadd-model-providerAdd and live-prove a model provider with non-interactive config one-liners, without exposing credentials.
  • Aagent-transcriptRequested GitHub PR/issue agent transcripts: redact, trim, preview, and insert safely.
  • Aapple-notesCreate, view, edit, delete, search, move, or export Apple Notes via the memo CLI on macOS.
  • Aapple-remindersList, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.
  • Aauto-qaRun OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.
  • AautoreviewStructured code review through the shared OpenClaw agent-skills installation.
  • Abear-notesCreate, search, and manage Bear notes via grizzly CLI.
  • Ablock-kitUse proactively for structured or interactive Slack replies, and when asked to author or validate native Slack Block Kit JSON.
  • AblogwatcherMonitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.
  • AblucliBluOS CLI (blu) for discovery, playback, grouping, and volume.

All agent skills → · MCP servers