[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PF7S453RNAJX5282DZ3HC":3,"skill-same:01M75PF7S453RNAJX5282DZ3HC":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M75PF7S453RNAJX5282DZ3HC","soul-in-sapphire",null,"Generic long-term memory (LTM) operations for OpenClaw using Notion (2025-09-03 data_sources). Use for durable memory writes\u002Fsearch, emotion-state ticks, journal writes, and model-controlled subagent spawn planning via local JSON presets.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fnextaltair\u002Fsoul-in-sapphire\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: soul-in-sapphire\ndescription: Generic long-term memory (LTM) operations for OpenClaw using Notion (2025-09-03 data_sources). Use for durable memory writes\u002Fsearch, emotion-state ticks, journal writes, and model-controlled subagent spawn planning via local JSON presets.\nmetadata: {\"openclaw\":{\"emoji\":\"💠\",\"requires\":{\"bins\":[\"node\"],\"env\":[\"NOTION_API_KEY\"]},\"primaryEnv\":\"NOTION_API_KEY\",\"dependsOnSkills\":[\"notion-api-automation\"],\"localReads\":[\"~\u002F.config\u002Fsoul-in-sapphire\u002Fconfig.json\"],\"optionalEnv\":[\"NOTIONCTL_PATH\"]}}\n---\n\n# soul-in-sapphire (Notion LTM)\n\nUse this skill to persist and retrieve durable memory in Notion, and to maintain emotion\u002Fstate + journal records.\n\n## Core intent (do not lose this)\n\nThis skill is not only a storage utility. Its core purpose is:\n\n1. Capture meaningful emotional\u002Fstate shifts from real work and conversations.\n2. Preserve those shifts as durable memory (not just raw logs).\n3. Reuse recalled memory to improve future judgments and behavior.\n\nIn short: record -> recall -> adapt.\nThe goal is continuity and growth, not archival volume.\n\n## Requirements\n\n- Notion token: `NOTION_API_KEY` (or `NOTION_TOKEN`)\n- Notion API version: `2025-09-03`\n- Local config: `~\u002F.config\u002Fsoul-in-sapphire\u002Fconfig.json`\n- Dependency skill: `notion-api-automation` (`scripts\u002Fnotionctl.mjs` is executed via local child process)\n- Optional override: `NOTIONCTL_PATH` (if set, uses explicit notionctl path instead of default sibling skill path)\n\n## Required Notion databases and schema\n\nCreate (or let setup create) these databases under the same parent page:\n\n- `\u003Cbase>-mem`\n- `\u003Cbase>-events`\n- `\u003Cbase>-emotions`\n- `\u003Cbase>-state`\n- `\u003Cbase>-journal`\n\n### 1) `\u003Cbase>-mem` (durable memory)\n\nPurpose: store high-signal long-term memory.\n\nProperties:\n\n- `Name` (title)\n- `Type` (select): `decision|preference|fact|procedure|todo|gotcha`\n- `Tags` (multi-select)\n- `Content` (rich_text)\n- `Source` (url, optional)\n- `Confidence` (select: `high|medium|low`, optional)\n\n### 2) `\u003Cbase>-events` (what happened)\n\nPurpose: record meaningful triggers from work\u002Fconversation.\n\nProperties:\n\n- `Name` (title)\n- `when` (date)\n- `importance` (select: `1..5`)\n- `trigger` (select): `progress|boundary|ambiguity|external_action|manual`\n- `context` (rich_text)\n- `source` (select): `discord|cli|cron|heartbeat|other`\n- `link` (url, optional)\n- `uncertainty` (number)\n- `control` (number)\n- `emotions` (relation -> `\u003Cbase>-emotions`)\n- `state` (relation -> `\u003Cbase>-state`)\n\n### 3) `\u003Cbase>-emotions` (felt response)\n\nPurpose: attach one or more emotion axes to one event.\n\nProperties:\n\n- `Name` (title)\n- `axis` (select): `arousal|valence|focus|confidence|stress|curiosity|social|solitude|joy|anger|sadness|fun|pain`\n- `level` (number)\n- `comment` (rich_text)\n- `weight` (number)\n- `body_signal` (multi-select): `tension|relief|fatigue|heat|cold`\n- `need` (select): `safety|progress|recognition|autonomy|rest|novelty`\n- `coping` (select): `log|ask|pause|act|defer`\n- `event` (relation -> `\u003Cbase>-events`)\n\n### 4) `\u003Cbase>-state` (snapshot after interpretation)\n\nPurpose: save the current interpreted state after events\u002Femotions.\n\nProperties:\n\n- `Name` (title)\n- `when` (date)\n- `state_json` (rich_text)\n- `reason` (rich_text)\n- `source` (select): `event|cron|heartbeat|manual`\n- `mood_label` (select): `clear|wired|dull|tense|playful|guarded|tender`\n- `intent` (select): `build|fix|organize|explore|rest|socialize|reflect`\n- `need_stack` (select): `safety|stability|belonging|esteem|growth`\n- `need_level` (number)\n- `avoid` (multi-select): `risk|noise|long_tasks|external_actions|ambiguity`\n- `event` (relation -> `\u003Cbase>-events`)\n\n### 5) `\u003Cbase>-journal` (daily synthesis)\n\nPurpose: keep a durable daily reflection and world context.\n\nProperties:\n\n- `Name` (title)\n- `when` (date)\n- `body` (rich_text)\n- `worklog` (rich_text)\n- `session_summary` (rich_text)\n- `mood_label` (select)\n- `intent` (select)\n- `future` (rich_text)\n- `world_news` (rich_text)\n- `tags` (multi-select)\n- `source` (select): `cron|manual`\n\n## Core commands\n\n### 1) Setup\n\n```bash\nnode skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fsetup_ltm.js --parent \"\u003CNotion parent page url>\" --base \"Valentina\" --yes\n```\n\n### 2) LTM write\n\n```bash\necho '{\n  \"title\":\"Decision: use data_sources API\",\n  \"type\":\"decision\",\n  \"tags\":[\"notion\",\"openclaw\"],\n  \"content\":\"Use \u002Fv1\u002Fdata_sources\u002F{id}\u002Fquery.\",\n  \"confidence\":\"high\"\n}' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_write.js\n```\n\n### 3) LTM search\n\n```bash\nnode skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_search.js --query \"data_sources\" --limit 5\n```\n\n### 4) Emotion\u002Fstate tick\n\n```bash\ncat \u003C\u003C'JSON' >\u002Ftmp\u002Femostate_tick.json\n{\n  \"event\": {\"title\":\"...\"},\n  \"emotions\": [{\"axis\":\"joy\",\"level\":6}],\n  \"state\": {\"mood_label\":\"clear\",\"intent\":\"build\",\"reason\":\"...\"}\n}\nJSON\nnode skills\u002Fsoul-in-sapphire\u002Fscripts\u002Femostate_tick.js --payload-file \u002Ftmp\u002Femostate_tick.json\n```\n\n### 5) Journal write\n\n```bash\necho '{\"body\":\"...\",\"source\":\"cron\"}' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fjournal_write.js\n```\n\n## Subagent spawn planning (use shared builder skill)\n\nUse the shared skill `subagent-spawn-command-builder` to generate `sessions_spawn` payload JSON.\nDo not use `soul-in-sapphire` local planner scripts for this anymore.\n\n- Template: `skills\u002Fsubagent-spawn-command-builder\u002Fstate\u002Fspawn-profiles.template.json`\n- Active preset: `skills\u002Fsubagent-spawn-command-builder\u002Fstate\u002Fspawn-profiles.json`\n- Builder usage (skill-level):\n  - Call `subagent-spawn-command-builder`\n  - Use profile `\u003Cheartbeat|journal>`\n  - Provide the run-specific task text\n\nOutput is ready-to-use JSON for `sessions_spawn`.\n\nBuilder log file:\n\n- `skills\u002Fsubagent-spawn-command-builder\u002Fstate\u002Fbuild-log.jsonl`\n\n## Operational notes\n\n- Keep writes high-signal (avoid dumping full chat logs).\n- If heartbeat is comment-only, emotion tick may be skipped.\n- If periodic emostate is required regardless of heartbeat context, add a dedicated cron job for `emostate_tick.js`.\n- `ltm_write.js` \u002F `journal_write.js` expect JSON on stdin.\n- `emostate_tick.js` accepts `--payload-file`, `--payload-json`, or stdin; prefer `--payload-file` for agent\u002Fcron reliability.\n- If `emostate_tick.js` is called without `--payload-file`\u002F`--payload-json`, empty stdin is rejected.\n- For `emostate_tick.js`, semantically empty payloads (e.g. `{}` or only empty objects) are also rejected to avoid noisy records.\n\n## Skill Integration Commands\n\n### 1) Update Core Identity Files from Skill\n\n```bash\n# Update SOUL.md from skill\ncat \u003C\u003C'JSON' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_write.js\n{\n  \"title\":\"Update SOUL.md\",\n  \"type\":\"decision\",\n  \"tags\":[\"identity\",\"growth\"],\n  \"content\":\"Updating SOUL.md from skill with latest evolution insights\",\n  \"confidence\":\"high\"\n}\nJSON\n\n# Update IDENTITY.md from skill  \ncat \u003C\u003C'JSON' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_write.js\n{\n  \"title\":\"Update IDENTITY.md\",\n  \"type\":\"decision\",\n  \"tags\":[\"identity\",\"evolution\"],\n  \"content\":\"Updating IDENTITY.md from skill with current growth status\",\n  \"confidence\":\"high\"\n}\nJSON\n\n# Update HEARTBEAT.md from skill\ncat \u003C\u003C'JSON' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_write.js\n{\n  \"title\":\"Update HEARTBEAT.md\",\n  \"type\":\"decision\",\n  \"tags\":[\"growth\",\"heartbeat\"],\n  \"content\":\"Updating HEARTBEAT.md from skill with evolution integration\",\n  \"confidence\":\"high\"\n}\nJSON\n\n# Update MEMORY.md from skill\ncat \u003C\u003C'JSON' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_write.js\n{\n  \"title\":\"Update MEMORY.md\",\n  \"type\":\"decision\",\n  \"tags\":[\"memory\",\"evolution\"],\n  \"content\":\"Updating MEMORY.md from skill with evolution records\",\n  \"confidence\":\"high\"\n}\nJSON\n```\n\n### 2) Evolution Check from Skill\n\n```bash\n# Check evolution status and update if needed\nnode skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_search.js --query \"evolution growth identity\" --limit 3\n\n# If evolution detected, update core files\nif [ $? -eq 0 ]; then\n  echo \"Evolution detected, updating core identity files...\"\n  # Update each file as needed\nfi\n```\n\n### 3) Growth Integration from Skill\n\n```bash\n# Integrate skill insights into core identity\ncat \u003C\u003C'JSON' >\u002Ftmp\u002Fskill_growth_tick.json\n{\n  \"event\": { \"title\": \"Skill Integration\" },\n  \"emotions\": [{ \"axis\": \"focus\", \"level\": 8 }],\n  \"state\": {\n    \"mood_label\": \"wired\",\n    \"intent\": \"build\",\n    \"reason\": \"Integrating skill insights into core identity\"\n  }\n}\nJSON\nnode skills\u002Fsoul-in-sapphire\u002Fscripts\u002Femostate_tick.js --payload-file \u002Ftmp\u002Fskill_growth_tick.json\n\n# Update core files with new insights\ncat \u003C\u003C'JSON' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_write.js\n{\n  \"title\":\"Skill Integration Complete\",\n  \"type\":\"decision\",\n  \"tags\":[\"integration\",\"growth\"],\n  \"content\":\"Successfully integrated skill insights into core identity files\",\n  \"confidence\":\"high\"\n}\nJSON\n```\n\n## Integration Workflow\n\n1. **Skill Analysis**: Analyze skill outputs and insights\n2. **Evolution Detection**: Check for significant changes or learnings\n3. **Core Update**: Update SOUL.md, IDENTITY.md, HEARTBEAT.md, MEMORY.md as needed\n4. **State Recording**: Record emotional and state changes\n5. **Memory Preservation**: Store evolution records in durable memory\n\n## Evolution Triggers from Skills\n\n- **Learning Detection**: When new skills provide significant insights\n- **Growth Opportunities**: When skills suggest optimization possibilities\n- **Behavioral Changes**: When skills influence interaction patterns\n- **Identity Refinement**: When skills contribute to self-understanding\n\nThis integration allows skills to directly contribute to my autonomous growth and evolution while maintaining the core identity framework.\n","# soul-in-sapphire (Notion LTM)\n\nUse this skill to persist and retrieve durable memory in Notion, and to maintain emotion\u002Fstate + journal records.\n\n## Core intent (do not lose this)\n\nThis skill is not only a storage utility. Its core purpose is:\n\n1. Capture meaningful emotional\u002Fstate shifts from real work and conversations.\n2. Preserve those shifts as durable memory (not just raw logs).\n3. Reuse recalled memory to improve future judgments and behavior.\n\nIn short: record -> recall -> adapt.\nThe goal is continuity and growth, not archival volume.\n\n## Requirements\n\n- Notion token: `NOTION_API_KEY` (or `NOTION_TOKEN`)\n- Notion API version: `2025-09-03`\n- Local config: `~\u002F.config\u002Fsoul-in-sapphire\u002Fconfig.json`\n- Dependency skill: `notion-api-automation` (`scripts\u002Fnotionctl.mjs` is executed via local child process)\n- Optional override: `NOTIONCTL_PATH` (if set, uses explicit notionctl path instead of default sibling skill path)\n\n## Required Notion databases and schema\n\nCreate (or let setup create) these databases under the same parent page:\n\n- `\u003Cbase>-mem`\n- `\u003Cbase>-events`\n- `\u003Cbase>-emotions`\n- `\u003Cbase>-state`\n- `\u003Cbase>-journal`\n\n### 1) `\u003Cbase>-mem` (durable memory)\n\nPurpose: store high-signal long-term memory.\n\nProperties:\n\n- `Name` (title)\n- `Type` (select): `decision|preference|fact|procedure|todo|gotcha`\n- `Tags` (multi-select)\n- `Content` (rich_text)\n- `Source` (url, optional)\n- `Confidence` (select: `high|medium|low`, optional)\n\n### 2) `\u003Cbase>-events` (what happened)\n\nPurpose: record meaningful triggers from work\u002Fconversation.\n\nProperties:\n\n- `Name` (title)\n- `when` (date)\n- `importance` (select: `1..5`)\n- `trigger` (select): `progress|boundary|ambiguity|external_action|manual`\n- `context` (rich_text)\n- `source` (select): `discord|cli|cron|heartbeat|other`\n- `link` (url, optional)\n- `uncertainty` (number)\n- `control` (number)\n- `emotions` (relation -> `\u003Cbase>-emotions`)\n- `state` (relation -> `\u003Cbase>-state`)\n\n### 3) `\u003Cbase>-emotions` (felt response)\n\nPurpose: attach one or more emotion axes to one event.\n\nProperties:\n\n- `Name` (title)\n- `axis` (select): `arousal|valence|focus|confidence|stress|curiosity|social|solitude|joy|anger|sadness|fun|pain`\n- `level` (number)\n- `comment` (rich_text)\n- `weight` (number)\n- `body_signal` (multi-select): `tension|relief|fatigue|heat|cold`\n- `need` (select): `safety|progress|recognition|autonomy|rest|novelty`\n- `coping` (select): `log|ask|pause|act|defer`\n- `event` (relation -> `\u003Cbase>-events`)\n\n### 4) `\u003Cbase>-state` (snapshot after interpretation)\n\nPurpose: save the current interpreted state after events\u002Femotions.\n\nProperties:\n\n- `Name` (title)\n- `when` (date)\n- `state_json` (rich_text)\n- `reason` (rich_text)\n- `source` (select): `event|cron|heartbeat|manual`\n- `mood_label` (select): `clear|wired|dull|tense|playful|guarded|tender`\n- `intent` (select): `build|fix|organize|explore|rest|socialize|reflect`\n- `need_stack` (select): `safety|stability|belonging|esteem|growth`\n- `need_level` (number)\n- `avoid` (multi-select): `risk|noise|long_tasks|external_actions|ambiguity`\n- `event` (relation -> `\u003Cbase>-events`)\n\n### 5) `\u003Cbase>-journal` (daily synthesis)\n\nPurpose: keep a durable daily reflection and world context.\n\nProperties:\n\n- `Name` (title)\n- `when` (date)\n- `body` (rich_text)\n- `worklog` (rich_text)\n- `session_summary` (rich_text)\n- `mood_label` (select)\n- `intent` (select)\n- `future` (rich_text)\n- `world_news` (rich_text)\n- `tags` (multi-select)\n- `source` (select): `cron|manual`\n\n## Core commands\n\n### 1) Setup\n\n```bash\nnode skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fsetup_ltm.js --parent \"\u003CNotion parent page url>\" --base \"Valentina\" --yes\n```\n\n### 2) LTM write\n\n```bash\necho '{\n  \"title\":\"Decision: use data_sources API\",\n  \"type\":\"decision\",\n  \"tags\":[\"notion\",\"openclaw\"],\n  \"content\":\"Use \u002Fv1\u002Fdata_sources\u002F{id}\u002Fquery.\",\n  \"confidence\":\"high\"\n}' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_write.js\n```\n\n### 3) LTM search\n\n```bash\nnode skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_search.js --query \"data_sources\" --limit 5\n```\n\n### 4) Emotion\u002Fstate tick\n\n```bash\ncat \u003C\u003C'JSON' >\u002Ftmp\u002Femostate_tick.json\n{\n  \"event\": {\"title\":\"...\"},\n  \"emotions\": [{\"axis\":\"joy\",\"level\":6}],\n  \"state\": {\"mood_label\":\"clear\",\"intent\":\"build\",\"reason\":\"...\"}\n}\nJSON\nnode skills\u002Fsoul-in-sapphire\u002Fscripts\u002Femostate_tick.js --payload-file \u002Ftmp\u002Femostate_tick.json\n```\n\n### 5) Journal write\n\n```bash\necho '{\"body\":\"...\",\"source\":\"cron\"}' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fjournal_write.js\n```\n\n## Subagent spawn planning (use shared builder skill)\n\nUse the shared skill `subagent-spawn-command-builder` to generate `sessions_spawn` payload JSON.\nDo not use `soul-in-sapphire` local planner scripts for this anymore.\n\n- Template: `skills\u002Fsubagent-spawn-command-builder\u002Fstate\u002Fspawn-profiles.template.json`\n- Active preset: `skills\u002Fsubagent-spawn-command-builder\u002Fstate\u002Fspawn-profiles.json`\n- Builder usage (skill-level):\n  - Call `subagent-spawn-command-builder`\n  - Use profile `\u003Cheartbeat|journal>`\n  - Provide the run-specific task text\n\nOutput is ready-to-use JSON for `sessions_spawn`.\n\nBuilder log file:\n\n- `skills\u002Fsubagent-spawn-command-builder\u002Fstate\u002Fbuild-log.jsonl`\n\n## Operational notes\n\n- Keep writes high-signal (avoid dumping full chat logs).\n- If heartbeat is comment-only, emotion tick may be skipped.\n- If periodic emostate is required regardless of heartbeat context, add a dedicated cron job for `emostate_tick.js`.\n- `ltm_write.js` \u002F `journal_write.js` expect JSON on stdin.\n- `emostate_tick.js` accepts `--payload-file`, `--payload-json`, or stdin; prefer `--payload-file` for agent\u002Fcron reliability.\n- If `emostate_tick.js` is called without `--payload-file`\u002F`--payload-json`, empty stdin is rejected.\n- For `emostate_tick.js`, semantically empty payloads (e.g. `{}` or only empty objects) are also rejected to avoid noisy records.\n\n## Skill Integration Commands\n\n### 1) Update Core Identity Files from Skill\n\n```bash\n# Update SOUL.md from skill\ncat \u003C\u003C'JSON' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_write.js\n{\n  \"title\":\"Update SOUL.md\",\n  \"type\":\"decision\",\n  \"tags\":[\"identity\",\"growth\"],\n  \"content\":\"Updating SOUL.md from skill with latest evolution insights\",\n  \"confidence\":\"high\"\n}\nJSON\n\n# Update IDENTITY.md from skill  \ncat \u003C\u003C'JSON' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_write.js\n{\n  \"title\":\"Update IDENTITY.md\",\n  \"type\":\"decision\",\n  \"tags\":[\"identity\",\"evolution\"],\n  \"content\":\"Updating IDENTITY.md from skill with current growth status\",\n  \"confidence\":\"high\"\n}\nJSON\n\n# Update HEARTBEAT.md from skill\ncat \u003C\u003C'JSON' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_write.js\n{\n  \"title\":\"Update HEARTBEAT.md\",\n  \"type\":\"decision\",\n  \"tags\":[\"growth\",\"heartbeat\"],\n  \"content\":\"Updating HEARTBEAT.md from skill with evolution integration\",\n  \"confidence\":\"high\"\n}\nJSON\n\n# Update MEMORY.md from skill\ncat \u003C\u003C'JSON' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_write.js\n{\n  \"title\":\"Update MEMORY.md\",\n  \"type\":\"decision\",\n  \"tags\":[\"memory\",\"evolution\"],\n  \"content\":\"Updating MEMORY.md from skill with evolution records\",\n  \"confidence\":\"high\"\n}\nJSON\n```\n\n### 2) Evolution Check from Skill\n\n```bash\n# Check evolution status and update if needed\nnode skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_search.js --query \"evolution growth identity\" --limit 3\n\n# If evolution detected, update core files\nif [ $? -eq 0 ]; then\n  echo \"Evolution detected, updating core identity files...\"\n  # Update each file as needed\nfi\n```\n\n### 3) Growth Integration from Skill\n\n```bash\n# Integrate skill insights into core identity\ncat \u003C\u003C'JSON' >\u002Ftmp\u002Fskill_growth_tick.json\n{\n  \"event\": { \"title\": \"Skill Integration\" },\n  \"emotions\": [{ \"axis\": \"focus\", \"level\": 8 }],\n  \"state\": {\n    \"mood_label\": \"wired\",\n    \"intent\": \"build\",\n    \"reason\": \"Integrating skill insights into core identity\"\n  }\n}\nJSON\nnode skills\u002Fsoul-in-sapphire\u002Fscripts\u002Femostate_tick.js --payload-file \u002Ftmp\u002Fskill_growth_tick.json\n\n# Update core files with new insights\ncat \u003C\u003C'JSON' | node skills\u002Fsoul-in-sapphire\u002Fscripts\u002Fltm_write.js\n{\n  \"title\":\"Skill Integration Complete\",\n  \"type\":\"decision\",\n  \"tags\":[\"integration\",\"growth\"],\n  \"content\":\"Successfully integrated skill insights into core identity files\",\n  \"confidence\":\"high\"\n}\nJSON\n```\n\n## Integration Workflow\n\n1. **Skill Analysis**: Analyze skill outputs and insights\n2. **Evolution Detection**: Check for significant changes or learnings\n3. **Core Update**: Update SOUL.md, IDENTITY.md, HEARTBEAT.md, MEMORY.md as needed\n4. **State Recording**: Record emotional and state changes\n5. **Memory Preservation**: Store evolution records in durable memory\n\n## Evolution Triggers from Skills\n\n- **Learning Detection**: When new skills provide significant insights\n- **Growth Opportunities**: When skills suggest optimization possibilities\n- **Behavioral Changes**: When skills influence interaction patterns\n- **Identity Refinement**: When skills contribute to self-understanding\n\nThis integration allows skills to directly contribute to my autonomous growth and evolution while maintaining the core identity framework.\n",{"name":5,"metadata":24,"description":7},{"openclaw":25},{"emoji":26,"requires":27,"localReads":32,"primaryEnv":29,"optionalEnv":34,"dependsOnSkills":36},"💠",{"env":28,"bins":30},[29],"NOTION_API_KEY",[31],"node",[33],"~\u002F.config\u002Fsoul-in-sapphire\u002Fconfig.json",[35],"NOTIONCTL_PATH",[37],"notion-api-automation","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fnextaltair\u002Fsoul-in-sapphire",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill soul-in-sapphire",{"tool":53,"command":54},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill soul-in-sapphire",{"tool":56,"command":57},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill soul-in-sapphire","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fnextaltair\u002Fsoul-in-sapphire\u002FSKILL.md",true,[],[62,70,77,84,91,98],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":69},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":69},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":69},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":69},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":69},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":69},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]