← Back to Skills Marketplace
1623
Downloads
0
Stars
2
Active Installs
18
Versions
Install in OpenClaw
/install soul-in-sapphire
Description
Long-term memory, state tracking, continuity review, and identity-change support for OpenClaw. Use for durable memory writes/search in Notion, emotion/state...
Usage Guidance
This skill appears to do what it claims: it runs Node scripts that read local state (memory/now-state.json, IDENTITY.md), write a local config (~/.config/soul-in-sapphire/config.json), and create/read/write Notion databases via a notionctl helper. Before installing: 1) Only provide a Notion integration token with scopes you accept (consider least-privilege token or a dedicated integration workspace). 2) Review and trust the dependency skill notion-api-automation (the skill execs its notionctl.mjs). 3) Expect the skill to create Notion DBs and to write durable entries (journals, events, memory). 4) If you want to avoid local reads/writes, do not install or run without auditing/isolating the repository. If any of these behaviors are unacceptable, decline installation or run in an isolated environment and audit the notion-api-automation code as well.
Capability Analysis
Type: OpenClaw Skill
Name: soul-in-sapphire
Version: 1.0.13
The 'soul-in-sapphire' skill bundle is a comprehensive system for maintaining an agent's long-term memory, emotional state, and daily journals using Notion as a backend. The bundle includes scripts for database setup (`setup_ltm.js`), state tracking (`emostate_tick.js`), and memory management (`ltm_write.js`, `ltm_search.js`), all of which interact with the Notion API via a dependency skill (`notion-api-automation`). While the instructions in `SKILL.md` authorize the agent to proactively update a user profile (`USER.md`), they include explicit guardrails against storing sensitive data like credentials or secrets. The code uses safe execution patterns (`execFileSync` with argument arrays) and lacks any indicators of malicious intent, data exfiltration, or unauthorized persistence.
Capability Assessment
Purpose & Capability
Name/description claim long-term memory + continuity stored in Notion; the skill only requests node and NOTION_API_KEY and depends on a Notion helper skill. The scripts create/query/patch Notion databases and write/read local state; these capabilities match the stated purpose.
Instruction Scope
SKILL.md and scripts instruct the agent to read local workspace files (e.g., memory/now-state.json, IDENTITY.md) and to write local config (~/.config/soul-in-sapphire/config.json), and to create/write Notion DB entries. Those actions are relevant to continuity but are broader than a pure 'remote storage' utility — the skill intentionally accesses local state and identity artifacts. This is expected for continuity features but worth noting if you do not want local files read/modified.
Install Mechanism
No remote downloads or obscure installers; the skill runs local Node scripts and expects the 'notion-api-automation' helper (or a path via NOTIONCTL_PATH). There is use of child process execution (execFileSync) to call a notionctl script, which is expected for a wrapper around a Notion helper skill. No network URLs or archive extraction in the skill itself.
Credentials
The only required environment credential is NOTION_API_KEY (primaryEnv). An optional NOTIONCTL_PATH can override the helper script path. No unrelated secrets or multiple unrelated credentials are requested.
Persistence & Privilege
always:false (normal). The skill will create and persist a local config file (~/.config/soul-in-sapphire/config.json) and creates Notion databases/pages as part of setup — this is coherent with its purpose but means it will leave files and Notion artifacts. It also invokes a sibling skill's script (notion-api-automation) by path; ensure that dependency is trusted.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install soul-in-sapphire - After installation, invoke the skill by name or use
/soul-in-sapphire - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.13
soul-in-sapphire 1.0.13
- Removed unused/legacy scripts: `emostate_notion.js` and `ltm_common.js`.
- Updated invocation instructions in `SKILL.md` for dependency installation via ClawHub.
- Cleaned up documentation for clarity and to match actual invocation and usage patterns.
- Codebase now focuses on key scripts for memory search/write, state recall, and Notion bridge logic; removed redundant helpers.
- No changes to external API or skill invocation behavior—primarily docs and internal cleanup.
v1.0.12
refactor: TOOLS.md設定統合 / config file依存を除去
v1.0.11
refactor: migrate user config to TOOLS.md (#3)
v1.0.10
- Added section for user profile promotion (`USER.md`) with criteria and guidance for updating durable human profiles based on agent observations.
- Clarified what kinds of user information qualify for promotion (durable, reusable, and safe data only).
- Provided concrete positive and negative examples for user profile updates.
- No other behavior or API changes.
v1.0.9
soul-in-sapphire 1.0.9
- Expanded SKILL.md with explicit "Invocation mapping" section.
- Clarifies default behaviors for agent calls (e.g., heartbeat, journal, memory write).
- Enumerates trigger phrases and required actions for core invocation modes (heartbeat, journal, durable memory write, mood check, continuity/identity check).
- Emphasizes that writes should be durable—preferring Notion-backed actions to local notes, unless fallback is requested.
- Documents stricter criteria for success when responding to generic skill calls, reducing ambiguity for all users/agents.
- Retains all previous usage/command details; no breaking changes to endpoints or schemas.
v1.0.8
soul-in-sapphire v1.0.8 – Adds identity continuity, conflict tracking, and comparison tooling.
- New scripts for continuity checks, identity diffs, and inner-conflict tracking
- Expanded skill purpose to include tracking stable/unstable self-aspects and documenting identity change explicitly
- Updated documentation to reflect new commands for continuity review and conflict recording
- Adds local JSONL-based conflict log and subagent state tracking templates
- No breaking changes to core LTM write/search/emostate/journal behavior
v1.0.7
- Added support for providing emostate_tick.js input via --payload-file and --payload-json arguments (stdin still supported, but now optional).
- Documented and recommend using --payload-file for agent/cron reliability in emostate_tick.js.
- Improved error handling: emostate_tick.js strictly rejects semantically empty input from both file and stdin.
- Updated documentation in SKILL.md and usage in README.md to reflect new payload handling options.
- Minor internal script refactoring and clarifications in core command usage.
v1.0.6
- emostate_tick.js now strictly rejects empty or semantically empty payloads, ensuring only valid input is processed.
- SKILL.md updated to clarify that ltm_write.js, emostate_tick.js, and journal_write.js require non-empty JSON input via stdin—CLI flags alone are not accepted.
- Added usage notes about error behavior for empty input, preventing noisy or unintended records.
- Expanded SKILL.md with explicit integration examples for updating core identity and evolution files via skill commands.
v1.0.5
- Improved scripts/journal_write.js to handle and ignore empty string journal writes, for improved input validation.
- No changes to documentation or skill interface.
v1.0.4
- Initial public release of the skill.
- Implements durable memory write, search, emotion/state tick, and journal write for Notion LTM in the OpenClaw system.
- Adds setup, configuration, and core Node.js scripts for all documented LTM operations.
- Supports model-driven subagent spawn planning via shared builder skill only.
- Documentation improved; now allows `NOTIONCTL_PATH` override for more flexible dependency control.
v1.0.2
- Major refactor: All local scripts and related files were removed; now relies on the `notion-api-automation` skill for Notion operations.
- Added clear dependency metadata and workspace discovery requirements to SKILL.md.
- Updated documentation to reflect new runtime structure and external dependency handling.
- Subagent spawn planning now exclusively uses the shared `subagent-spawn-command-builder` skill—local planner scripts are no longer available.
v1.0.0
- Switched LTM write and search usage examples from Python scripts to Node.js scripts in documentation.
- Updated documentation to reflect Node.js is now required for LTM write (`ltm_write.js`) and search (`ltm_search.js`) commands.
- No core functionality or schema changes; this revision is purely an update to documentation and usage instructions.
v0.2.0
Version 0.2.0
- Fully migrated all CLI scripts from Python to Node.js for consistency.
- Added package.json and modularized scripts for Notion LTM, emostate, and journal operations.
- Removed legacy Python scripts.
- Updated operational instructions in README for Node.js usage.
- Subagent spawn planning must now use the shared `subagent-spawn-command-builder` skill; local planner scripts removed.
v0.1.4
- Updated subagent spawn planning: replaced local planner scripts with a call to the shared skill `subagent-spawn-command-builder`.
- Updated documentation to reflect use of the shared builder, including new locations for templates, presets, and log files.
- Deprecated use of `soul-in-sapphire` local subagent planner scripts in favor of the shared builder approach.
v0.1.3
soul-in-sapphire 0.1.3
- Added scripts/bootstrap_config.py for configuration bootstrapping.
- Added scripts/ltm_search.py to enable memory search from the command line.
v0.1.2
soul-in-sapphire v0.1.2
- Expanded documentation: SKILL.md and README.md now cover database schemas for events, emotions, state, and journal, not just memory.
- Added subagent spawn planning support via local JSON preset and new script (`scripts/subagent_spawn_plan.py`).
- Removed legacy scripts: `bootstrap_config.py` and `ltm_search.py` are no longer included.
- Streamlined config/database instructions and clarified operational guidance.
- Internal code improvements for long-term memory and Notion API helpers.
v0.1.1
- Added local Notion API helpers in both JavaScript (`scripts/notion_client.js`) and Python (`scripts/notion_http.py`), removing dependency on `skills/notionkit/*`.
- Updated quickstart and setup instructions to prefer Node.js entrypoints and use the Notion parent page URL.
- README and documentation now recommend the `notion-api-automation` skill as a preferred dependency for operations.
- Improved clarity on Notion API version, tooling, and config bootstrap steps.
- All Notion API operations now handled internally or via official dependencies; external NotionKit scripts are no longer required.
v0.1.0
soul-in-sapphire 0.1.0
- Initial release of project-agnostic long-term memory (LTM) skill for OpenClaw using Notion (2025-09-03 data_sources API).
- Supports bootstrapping a Notion LTM database, persisting durable memories, and later search/recall.
- Provides scripts and config for setup, writing, and searching LTM entries.
- Includes basic Valentina emotion-state model using separate Notion databases.
- Adds support for daily journal and emotional reflection integration (cron/heartbeat automation).
- Offers both Python and Node.js entrypoints (Node.js preferred for new workflows).
Metadata
Frequently Asked Questions
What is Soul In Sapphire?
Long-term memory, state tracking, continuity review, and identity-change support for OpenClaw. Use for durable memory writes/search in Notion, emotion/state... It is an AI Agent Skill for Claude Code / OpenClaw, with 1623 downloads so far.
How do I install Soul In Sapphire?
Run "/install soul-in-sapphire" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Soul In Sapphire free?
Yes, Soul In Sapphire is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Soul In Sapphire support?
Soul In Sapphire is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Soul In Sapphire?
It is built and maintained by Altair (@nextaltair); the current version is v1.0.13.
More Skills