knowledge is what brings us together
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only knowledge-base skill is coherent, but users should know it stores a lightweight persistent memory index and makes scoped local file/git changes in a chosen knowledge folder.
Install only if you want the agent to maintain a persistent local knowledge base. Pick a dedicated folder, avoid adding secrets or highly sensitive documents, review bulk imports or reorganizations, and be careful before configuring any git remote or syncing the folder.
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.
Stored knowledge categories and summaries may be reused across sessions and may influence later answers.
The skill deliberately stores a persistent knowledge-base path and category index that can affect future conversations.
The agent's persistent memory should contain a lightweight index of the knowledge base so that category awareness is always in context — even before this skill is activated.
Use a dedicated knowledge folder, avoid storing highly sensitive material unless intended, and periodically review or clear the persistent memory index if it becomes outdated or unwanted.
The agent may create local folders and files as part of normal setup.
The skill instructs the agent to run a local shell command to create directories in the chosen knowledge-base path.
create ... `unsorted/raw/` and `unsorted/summary/` directories (use `mkdir -p` via Bash)
Choose a dedicated, non-sensitive knowledge-base directory and review any broad import or reorganization request before approving it.
Captured knowledge may remain in git history even after later edits or moves.
The skill directs local git initialization and commits for version history, which is purpose-aligned but creates persistent local history of stored content.
If git is available and the knowledge base directory is not already a git repository, initialize one (`git init`). ... After meaningful operations ... commit the changes
Do not store secrets or sensitive documents in the knowledge base, and only configure or push a remote repository if you intentionally want the content synced elsewhere.