Soul In Sapphire
ReviewAudited by ClawScan on May 10, 2026.
Overview
This appears to be a disclosed Notion-based long-term memory and journaling skill, but it can persist sensitive state and uses a Notion token plus a local helper command.
Install this only if you want OpenClaw to maintain long-term memory in Notion. Use a dedicated Notion integration connected only to the skill's databases, review what gets written, avoid untrusted NOTIONCTL_PATH overrides, and enable cron/heartbeat automation only if recurring writes are desired.
Findings (6)
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.
Conversation, work, emotional state, or identity-related notes may become long-lived Notion records and may influence future agent responses.
The skill is explicitly designed to store durable memory and feed it back into later agent behavior.
Use this skill to persist and retrieve durable memory in Notion... Reuse recalled memory to improve future judgments and behavior.
Use a dedicated Notion workspace/page, review stored entries periodically, and tell the agent when a conversation or topic should not be written to memory.
A broadly scoped Notion integration token could let the skill read or modify more Notion content than intended.
The skill requires a credential that can access whatever Notion pages/databases the integration is connected to.
Notion token: `NOTION_API_KEY` (or `NOTION_TOKEN`)
Create a least-privilege Notion integration connected only to the dedicated Soul-in-Sapphire parent page/databases, and rotate the token if it is exposed.
A vague request to use the skill may result in a real memory, journal, or state entry being written to Notion.
The instructions encourage the agent to make durable Notion writes on high-level invocation; this fits the memory purpose but should be user-understood.
If the task is ambiguous, choose the smallest concrete action that improves continuity... Prefer a real write (`emostate_tick.js`, `journal_write.js`, `ltm_write.js`) over vague acknowledgement.
Invoke the skill with explicit intent, such as search-only, draft-only, or write-after-confirmation, when you do not want automatic durable writes.
The skill will execute the installed notion-api-automation helper, or an override script if NOTIONCTL_PATH is set.
The skill runs a local Node helper to perform Notion API operations. This is disclosed and purpose-aligned, but it is still local code execution.
out = execFileSync('node', args, { encoding: 'utf-8' }).trim();Install the dependency from a trusted source and do not set NOTIONCTL_PATH to an unreviewed script.
Security depends partly on the installed notion-api-automation helper and any future changes to it.
Core Notion operations are delegated to another locally installed skill whose code is not included in this artifact set.
Dependency skill: `notion-api-automation` (`scripts/notionctl.mjs` is executed via local child process)
Review or pin the dependency where possible, and reinstall it only from trusted ClawHub sources.
If the user configures scheduled execution, the skill may write recurring Notion entries without a manual prompt each time.
The documentation recommends recurring journal and heartbeat use, while leaving cron/heartbeat setup to the user's environment.
自動実行(推奨) ... 01:00 JST: journalを必ず書く ... heartbeat ... OpenClawの cron/heartbeat は環境ごとに設定してください。
Only enable cron or heartbeat automation if you want recurring memory writes, and keep the outputs easy to inspect or disable.