$ ~/registry/skill/composiohq-composio-skills-mem-automation

SKILL

mem-automation

Name: mem-automation
Author: Composio

Automate Mem tasks through Rube MCP after checking current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This skill appears to be an open-source, prompt-only wrapper with strong community adoption, and the provided material does not show it directly requesting secrets, local execution, or local file access, so overall risk is relatively low. However, it is explicitly designed to rely on external Rube MCP and a Mem connection, so users should pay attention to data egress and supply-chain boundaries at runtime.

CredentialsCaution

The material says the skill itself requires no API key, but actual use requires activating a mem connection via RUBE_MANAGE_CONNECTIONS and possibly completing authorization through an external auth link; this means credentials primarily live in the downstream Rube/Mem integration rather than in the skill itself.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint https://rube.app/mcp and executing actions through Composio's Mem toolkit; therefore task content, arguments, or results are likely sent to Rube/Composio/Mem-related services. The endpoint is declared, but it is still a remote egress path.

Code executionLow risk

The system marks this as prompt-only, and the provided material does not show the skill itself spawning local processes, running scripts, or requesting system-level execution privileges; it mainly instructs use of external MCP tools.

Data accessCaution

The material does not show direct local file read/write, but its purpose is to automate Mem operations through remote tools; therefore the effective data access scope depends on the authorized Mem account and tool schemas, not on a local least-privilege model.

Supply chainLow risk

The source is an open GitHub repository with high community adoption (64.9k stars), which are strong risk-reducing signals; while the license is not stated and maintenance status is unknown, there are no clear red flags such as closed-source behavior, spoofed provenance, or obvious malicious injection.

Recommendations

Use it only after confirming that you trust the Rube/Composio/Mem service boundary, and verify the identity behind any external authorization page.
Before connecting Mem, review the scope of data being granted and avoid linking highly sensitive workspaces or primary accounts.
Prefer testing with a non-production account to inspect the actual tool schemas and actions returned by RUBE_SEARCH_TOOLS.
Keep an eye on upstream maintenance status and verify that the rube.app/mcp endpoint matches the published documentation.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "mem-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/mem-automation/SKILL.md
2. Save it as ~/.claude/skills/mem-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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_CONNECTIONS with toolkit mem
Always call RUBE_SEARCH_TOOLS first 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_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit mem
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_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, 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

Automate Finmei tasks and connect workflows through Rube MCP.

ComposioGet→

$ loading_