Agent Knowledge Capture

PassAudited by ClawScan on May 1, 2026.

Overview

This appears to be a local knowledge-organizing skill, but users should verify the separate `know` command and be intentional about persistent indexing and scheduled cleanup.

Before installing, confirm the actual `know` executable comes from the expected ClawHub package, choose a limited knowledge directory, avoid storing secrets or highly sensitive material, and test cleanup manually before enabling any heartbeat or cron automation.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

You may be relying on a separate local command whose implementation is not shown in these artifacts.

Why it was flagged

The documented helper executable is central to the skill, but the supplied artifact set contains only SKILL.md and no install spec or code files, so users should confirm what executable they are actually installing or running.

Skill content
This installs `scripts/know` — add to PATH or use full path: `~/.openclaw/skills/knowledge/scripts/know`
Recommendation

Verify the `know` script/package source before adding it to PATH, running it, or scheduling it.

What this means

Sensitive, incorrect, or untrusted saved notes could be rediscovered and reused later.

Why it was flagged

The skill creates a persistent, searchable knowledge store intended for future retrieval, which is expected for its purpose but means saved content can influence later work.

Skill content
Default: `~/.soulshare/agent/knowledge/` ... `qmd collection add ~/.soulshare/agent/knowledge --name knowledge`
Recommendation

Keep the knowledge directory scoped, avoid storing secrets, and review or tag untrusted content clearly before indexing it.

What this means

Scheduled cleanup could change or remove knowledge entries without a fresh manual review each time.

Why it was flagged

The skill recommends recurring automatic maintenance that can mutate files in the knowledge store; this is disclosed and purpose-aligned, but it is still persistent automation.

Skill content
`know tidy --fix` ... `Auto-fix: normalize tags, move misplaced files, remove empty` ... `Recommended: Run `know tidy --fix` in heartbeats or nightly cron.`
Recommendation

Run `tidy` without `--fix` first, back up important notes, and only schedule `--fix` after confirming it affects the intended directory.