Lifestyle & Tools
#mcp
semanticscholar-automation
Automate Semanticscholar tasks via Rube MCP (Composio). Always search tools first for current schemas.
DeepseekModel
Curated skill
Quality Excellent · 90
v1.0.0
Get
https://deepseekmodel.com/api/download.php?id=openteams-lab-openteams-assets-skills-semanticscholar-automation-skill-md&format=skill
Download .skill
Standard format with system_prompt and model_config, ready for any agent framework
The actual content of the system_prompt field in the .skill file.
name semanticscholar-automation description Automate Semanticscholar tasks via Rube MCP (Composio). Always search tools first for current schemas. requires {"mcp":["rube"]} Semanticscholar Automation via Rube MCP Automate Semanticscholar operations through Composio's Semanticscholar toolkit via Rube MCP. Toolkit docs : composio.dev/toolkits/semanticscholar Prerequisites Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Semanticscholar connection via RUBE_MANAGE_CONNECTIONS with toolkit semanticscholar 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 semanticscholar 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: "Semanticscholar 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 Semanticscholar task"}] session: {id: "existing_session_id"} Step 2: Check Connection RUBE_MANAGE_CONNECTIONS toolkits: ["semanticscholar"] 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 Semanticscholar-specific use case Connect RUBE_MANAGE_CONNECTIONS with toolkit semanticscholar 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
Keywords that activate this skill. Click one to copy it.
This skill does not provide trigger words.
The downloaded .skill package contains the following fields.
| Field | Description |
|---|---|
| format | Format tag (skill/v1) |
| skill_id | Unique skill ID |
| name | Skill name |
| version | Version |
| description | Description |
| category | Categories (array) |
| trigger_words | Trigger words |
| tags | Tags |
| source | Source |
| source_url | Source URL (this page) |
| exported_at | Exported at (set per download) |
| system_prompt | System prompt body |
| model_config | Model config: provider / model / temperature / max_tokens / top_p |
| examples | Examples |
| install_guide | Import guide for Coze / Dify / Claude / custom frameworks |
The same skill can be exported in different platform formats.
