AGENT SKILL
memberspot-automation
Automate Memberspot tasks via Rube MCP (Composio). Always search tools first for current schemas.
使用场景Skill与智能体开发
- License 许可
- MIT
- 最近更新
- 2026-06-24
- Stars
- ★ 66
- Forks
- 24
01 前言 Front Matter
- name
- memberspot-automation
- requires
- { "mcp": [ "rube" ] }
- description
- Automate Memberspot tasks via Rube MCP (Composio). Always search tools first for current schemas.
02 资源文件 6
- 参考文档references/eval-framework.md5.3 KB
- 参考文档references/injection-detector.md6.6 KB
- 参考文档references/prompt-regression.md4.1 KB
- 参考文档references/test-patterns.md3.2 KB
- 参考文档references/tooling-evals.md3.8 KB
- 脚本scripts/detect_injection.py8.1 KB
03 SKILL.md 正文
Memberspot Automation via Rube MCP
Automate Memberspot operations through Composio's Memberspot toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/memberspot
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Memberspot connection via
RUBE_MANAGE_CONNECTIONSwith toolkitmemberspot - 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 toolkitmemberspot - 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: "Memberspot 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 Memberspot task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["memberspot"]
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 Memberspot-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit memberspot |
| 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