mem-automation
Automates Mem note-taking and management via Rube MCP integration.
Install
mkdir -p .claude/skills/mem-automation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11068" && unzip -o skill.zip -d .claude/skills/mem-automation && rm skill.zipInstalls to .claude/skills/mem-automation
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Automate Mem tasks via Rube MCP (Composio). Always search tools first for current schemas.Key capabilities
- →Discover Mem tool schemas
- →Manage Mem connections
- →Execute Mem operations
- →Handle pagination in responses
How it works
It uses Rube MCP to discover current tool schemas for Mem, verifies an active connection, and executes multi-tool workflows while maintaining session state.
Inputs & outputs
When to use mem-automation
- →Automating note creation
- →Retrieving Mem content
- →Managing note workflows
About this skill
Mem Automation via Rube MCP
Automate Mem operations through Composio's Mem toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/mem
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Mem connection via
RUBE_MANAGE_CONNECTIONSwith toolkitmem - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitmem - If connection is not ACTIVE, follow the returned auth link to complete setup
- Confirm connection status shows ACTIVE before running any workflows
Tool Discovery
Always discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Mem operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
Core Workflow Pattern
Step 1: Discover Available Tools
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Mem task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["mem"]
session_id: "your_session_id"
Step 3: Execute Tools
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
Known Pitfalls
- Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling
RUBE_SEARCH_TOOLS - Check connection: Verify
RUBE_MANAGE_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, even if empty ({}) - Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
- Pagination: Check responses for pagination tokens and continue fetching until complete
Quick Reference
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Mem-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit mem |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Powered by Composio
When not to use it
- →Direct API access without Rube MCP
- →Hardcoding tool slugs
Prerequisites
Limitations
- →Requires Rube MCP availability
- →Tool schemas change frequently
How it compares
It mandates dynamic tool discovery via Rube MCP rather than relying on static, hardcoded API integrations.
Compared to similar skills
mem-automation side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| mem-automation (this skill) | 0 | 6mo | No flags | Intermediate |
| notion-knowledge-capture | 10 | 9mo | No flags | Intermediate |
| apple-reminders | 25 | 2mo | Review | Beginner |
| memory-keeper-proactive-context-maintenance | 6 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by ranbot-ai
View all by ranbot-ai →You might also like
notion-knowledge-capture
makenotion
Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.
apple-reminders
openclaw
Manage Apple Reminders via the `remindctl` CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
memory-keeper-proactive-context-maintenance
b4CU-R4U
Automatically detect and maintain memory freshness by monitoring context staleness, significant code changes, task completions, and phase transitions. Proactively suggests and executes memory sync operations with user confirmation. Use when the user says "sync memory", "update context", or when the Skill detects that context is stale (>2 hours), significant changes have occurred (new commits), tasks completed, or major milestones reached. Replaces passive "context is stale" warnings with active maintenance.
notion-meeting-intelligence
openai
Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
agent-memory
yamadashy
Use this skill when the user asks to save, remember, recall, or organize memories. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check your notes', 'clean up memories'. Also use proactively when discovering valuable findings worth preserving.
apple-notes
openclaw
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks OpenClaw to add a note, list notes, search notes, or manage note folders.