From agentmind
Implements self-learning memory system for OpenClaw AI agents that detects preferences, workflows, and code styles from interactions. Useful for reviewing learned behaviors or leveraging prior knowledge in sessions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agentmind:agentmind-openclawThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Self-learning memory system that makes AI agents understand you better over time.
Self-learning memory system that makes AI agents understand you better over time. Automatically detects your preferences, workflows, and code style from interactions.
Use when user asks about learned preferences, wants to review agent behavior patterns, or when starting a session that should leverage previously learned knowledge.
/agentmind status — Show learning overview/agentmind instincts — List learned behaviors/agentmind evolve — Trigger evolution cycle/agentmind preferences — Show detected preferences/agentmind approve <id> — Approve a learned behavior/agentmind reject <id> — Reject a learned behaviorUnlike the Claude Code plugin which uses lifecycle hooks, the OpenClaw adaptation works through:
memory/*.md files and conversation history to detect patternsanalyze to discover new patterns from recent interactions# Install as OpenClaw skill
cp -r skills/agentmind-openclaw ~/.openclaw/skills/agentmind/
# Create cron for periodic learning (every 6 hours)
openclaw cron create --name "AgentMind Learn" \
--schedule "0 */6 * * *" \
--task "Run AgentMind analysis on recent memory files"
~/.openclaw/workspace/agentmind/instincts.json~/.openclaw/workspace/agentmind/observations/AgentMind complements OpenClaw's built-in memory_search (pull-based) with
push-based injection — high-confidence instincts are automatically included
in the agent's context without needing to search for them.
npx claudepluginhub youhai020616/agentmind --plugin agentmindGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.