webrenew/openclaw
skills/openclaw/SKILL.md
OpenClaw integration workflows for memories.sh. Use when: (1) Setting up OpenClaw with memories.sh (`openclaw onboard`, `memories init`), (2) Syncing OpenClaw workspace contracts (`~/.openclaw/workspace/AGENTS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`, `HEARTBEAT.md`, `BOOTSTRAP.md`, memory files, and skills), (3) Running lifecycle memory file workflows via `memories openclaw memory bootstrap|flush|snapshot|sync`, (4) Scheduling reminder prompts for OpenClaw refresh via `memories reminders`, (5) Troubleshooting OpenClaw workspace drift, missing skills, or path/config mismatches, (6) Updating OpenClaw runbooks or `llms.txt` guidance.
$ install --global
skillsauthnpx skillsauth add webrenew/memories openclawInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 2:00 AM6.9s2 files scanned
SKILL.md
- name:
- openclaw
- description:
- OpenClaw integration workflows for memories.sh. Use when: (1) Setting up OpenClaw with memories.sh (`openclaw onboard`, `memories init`), (2) Syncing OpenClaw workspace contracts (`~/.openclaw/workspace/AGENTS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`, `HEARTBEAT.md`, `BOOTSTRAP.md`, memory files, and skills), (3) Running lifecycle memory file workflows via `memories openclaw memory bootstrap|flush|snapshot|sync`, (4) Scheduling reminder prompts for OpenClaw refresh via `memories reminders`, (5) Troubleshooting OpenClaw workspace drift, missing skills, or path/config mismatches, (6) Updating OpenClaw runbooks or `llms.txt` guidance.
openclaw
Canonical setup and operational guidance for OpenClaw + memories.sh.
Quick Start
# First-time setup
openclaw onboard
cd your-project
memories init
memories generate claude -o ~/.openclaw/workspace/AGENTS.md --force
memories generate agents
mkdir -p ~/.openclaw/workspace/skills
if [ -d .agents/skills ]; then cp -R .agents/skills/. ~/.openclaw/workspace/skills/; fi
memories files ingest --global --include-config
memories files apply --global --include-config --force
# Optional: schedule a weekday reminder to run the refresh flow
memories reminders add "0 9 * * 1-5" "OpenClaw refresh: run generate + skills copy + files apply"
Workflow Decision Tree
- If
openclawis missing, stop and direct the user to official OpenClaw install docs. - If OpenClaw was not onboarded on this machine, run first-time setup.
- If setup exists and contract/rules changed, run workspace contract refresh.
- If the task is session lifecycle memory flow, run OpenClaw memory lifecycle commands (
bootstrap,flush,snapshot,sync) in that order as needed. - If behavior appears stale, run verification checks and troubleshooting in order.
- If workspace path is custom, read
~/.openclaw/openclaw.jsonand replace default~/.openclaw/workspacepaths.
Workspace Contract Refresh
cd your-project
memories generate claude -o ~/.openclaw/workspace/AGENTS.md --force
memories generate agents
if [ -d .agents/skills ]; then cp -R .agents/skills/. ~/.openclaw/workspace/skills/; fi
memories files ingest --global --include-config
memories files apply --global --include-config --force
Optional reminder check:
memories reminders list
memories reminders run
Memory Lifecycle Workflow (OpenClaw File Mode)
Use these when session context must persist across resets/compaction:
# 1) Bootstrap semantic + recent episodic context from OpenClaw files
memories openclaw memory bootstrap
# 2) Flush meaningful session events to today's daily log before compaction/reset
memories openclaw memory flush <session-id> --messages 15
# 3) Persist raw session snapshot in DB + OpenClaw snapshot file
memories openclaw memory snapshot <session-id> --trigger reset
# 4) Reconcile DB and OpenClaw files (import/export/both)
memories openclaw memory sync --direction both
Trigger guidance:
- Session start/new workspace:
bootstrap - Near context budget or inactivity compaction:
flush /new,/reset, manual handoff, or auto compaction boundaries:snapshot --trigger new_session|reset|manual|auto_compaction- Cross-device/manual file edits:
sync --direction import|export|both
Guardrails
- Prefer deterministic generate + ingest/apply flows over manual workspace edits.
- For lifecycle persistence, use
openclaw memory bootstrap|flush|snapshot|syncinstead of ad-hoc file writes. - Keep skills copy conditional so missing
.agents/skillsdoes not fail the flow. - Do not delete user workspace files unless explicitly requested.
- Treat project docs and official OpenClaw docs as source of truth.
Reference Files
- Operational workflows: See references/workflows.md for setup, verification, and troubleshooting.
Related Skills
webrenew/memories-sdk
tools
VerifiedTrustedCommunity
Build against the memories.sh SDK packages in application code. Use when working with `@memories.sh/core` or `@memories.sh/ai-sdk`, including: (1) Initializing `MemoriesClient`, (2) Reading, writing, searching, or editing memories from backend code, route handlers, workers, or scripts, (3) Integrating memories with the Vercel AI SDK via `memoriesMiddleware`, `memoriesTools`, `preloadContext`, or `createMemoriesOnFinish`, (4) Choosing and applying `tenantId` / `userId` / `projectId` scoping, (5) Managing SDK skill files or management APIs, or (6) Debugging memories SDK usage in TypeScript or JavaScript applications. Use `memories-cli` for CLI workflows, `memories-mcp` for MCP setup, and `memories-dev` for monorepo internals.
22SKILL.mdUpdated Apr 16, 2026
webrenew/memories-mcp
tools
VerifiedTrustedCommunity
MCP server integration for memories.sh — the persistent memory layer for AI agents. Use when: (1) Configuring the memories.sh MCP server for any client (Claude Code, Cursor, Windsurf, VS Code, v0, Claude Desktop, OpenCode, Factory), (2) Using MCP tools to store, search, retrieve memories, run lifecycle session workflows, or manage reminders, (3) Understanding get_context vs search_memories vs list_memories, (4) Working with streaming memory tools for SSE content, (5) Troubleshooting MCP connection issues, (6) Choosing between cloud MCP (HTTP) and local MCP (stdio) transports.
22SKILL.mdUpdated Apr 16, 2026
webrenew/memories-dev
tools
VerifiedTrustedCommunity
Developer guide for contributing to and extending the memories.sh codebase. Use when: (1) Understanding the memories.sh architecture and lifecycle model, (2) Adding new CLI commands or MCP tools, (3) Modifying the memory storage layer (SQLite/libSQL), (4) Working on the web dashboard (Next.js/Supabase), (5) Adding new generation targets for AI tools, (6) Extending cloud sync, session compaction, or embeddings functionality, (7) Debugging build, test, or deployment issues in the monorepo.
22SKILL.mdUpdated Apr 16, 2026
webrenew/memories-cli
tools
VerifiedTrustedCommunity
CLI reference and workflows for memories.sh — the persistent memory layer for AI agents. Use when: (1) Running memories CLI commands to add, search, edit, or manage memories, (2) Managing lifecycle workflows (session/checkpoint/compaction/consolidation/OpenClaw memory files), (3) Setting up memories.sh in a new project (memories init), (4) Generating AI tool config files (CLAUDE.md, .cursor/rules, etc.), (5) Importing existing rules from AI tools (memories ingest), (6) Managing cloud sync, embeddings, git hooks, or reminders, (7) Troubleshooting with memories doctor, (8) Working with memory templates, links, history, tags, or reminder schedules.
22SKILL.mdUpdated Apr 16, 2026