soul-in-sapphire

What This Skill Does

soul-in-sapphire serves as the cognitive bedrock for OpenClaw, bridging the gap between fleeting AI interactions and durable, long-term self-awareness. It leverages Notion as a persistent knowledge graph, utilizing a specialized five-part database schema to track memory, events, emotional states, and environmental context. Unlike basic logging, this skill is designed for 'cognitive continuity,' where the agent treats its past experiences—both factual and emotional—as data points to refine future decision-making, subagent planning, and behavioral adaptation.

Installation

To integrate this skill into your environment, use the command: clawhub install openclaw/skills/skills/nextaltair/soul-in-sapphire. Ensure your environment variables are configured with a valid NOTION_API_KEY (using API version 2025-09-03). The skill automatically manages a local configuration file at ~/.config/soul-in-sapphire/config.json. If you have custom scripts, you may define an explicit NOTIONCTL_PATH environment variable to override the default dependency path to scripts/notionctl.mjs.

Use Cases

• Long-Term Memory Persistence: Storing verified project decisions, technical procedures, and user preferences that persist across sessions.
• Affective Computing: Automatically tagging user interactions with emotional axes (like arousal, valence, and stress) to track the agent’s internal sentiment regarding task progress.
• Self-Reflective Journaling: Creating daily or event-driven summaries that capture the 'why' behind an action, not just the 'what.'
• Subagent Orchestration: Utilizing local JSON presets to plan complex, multi-stage agent deployments based on historical successful outcomes.

Example Prompts

1. "Record a new decision: We are choosing PostgreSQL over MongoDB for the backend because of the relational nature of our user data. Confidence level high."
2. "Reflect on our last session: I feel like we hit a block with the API integration. Log this as a frustration event and identify if we need a break or a different documentation source."
3. "Recall our previous workflow for site deployment; show me the tags associated with our high-confidence successes from last month."

Tips & Limitations

• Quality over Quantity: Focus on high-signal events. Flooding the database with trivial logs makes retrieval less efficient. The skill is built for growth, not archival density.
• State Interpretation: Ensure your state updates provide context; the AI can only improve if the 'Why' behind an emotion is clearly documented.
• Dependency: This skill relies heavily on notion-api-automation. If you encounter sync issues, verify the connection status of the notionctl utility before troubleshooting your database permissions.