Knowledge Organizer
ReviewAudited by ClawScan on May 1, 2026.
Overview
The skill’s behavior matches a knowledge-base organizer, but it needs expected access to your local vault and third-party sync credentials.
Install only if you want an agent to organize the specified vault and optionally sync selected content to Feishu or Tencent IMA. Provide IMA and Feishu credentials only for workflows that need them, verify any custom API endpoint before use, and try dry-run or validation commands before large imports.
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.
When invoked with a real destination, the skill can create or update knowledge-base content locally or in connected services.
The skill can mutate local notes or upload documents to third-party services, which is expected for its purpose but important user-visible authority.
You can write directly into Obsidian or sync to Feishu Knowledge Base and Tencent IMA.
Choose the destination explicitly, use dry-run or validation modes where available, and back up important vaults before broad sync runs.
Anyone running the IMA workflow with these credentials can import documents into the configured IMA account or folder.
IMA sync sends note content using IMA API credentials to the configured import endpoint; this is purpose-aligned but grants account-level import authority.
url = f"{config.base_url.rstrip('/')}/import_doc" ... "ima-openapi-apikey": config.api_keyUse scoped, rotatable API keys; keep the default trusted IMA endpoint unless intentionally testing; do not provide IMA credentials for Obsidian-only use.
The skill may process titles, frontmatter, paths, tags, and note contents from the configured vault while deduplicating or finding related notes.
Duplicate detection scans the existing knowledge base, so private local note content may be read and compared during normal operation.
articles = scan_knowledge_base(resolved_kb_path)
Set OPENCLAW_KB_ROOT or vault_root only to the intended vault, exclude sensitive notes from that vault if needed, and review outputs before syncing externally.