ragic-automation✓ ناجح

Automate Ragic tasks via Rube MCP (Composio). Always search tools first for current schemas.

55من ١٠٠
٤٨٢
★ نجوم
٢
↓ تنزيلات
٨٧
◉ مشاهدات

// تثبيت المهارة

تثبيت المهارة

المهارات هي كود تابع لأطراف ثالثة من مستودعات GitHub العامة. يفحص SkillHub الأنماط الخبيثة المعروفة، لكنه لا يستطيع ضمان السلامة. راجع الكود المصدري قبل التثبيت.

تثبيت عام (على مستوى المستخدم):

npx skillhub install openteams-lab/openteams/ragic-automation

تثبيت في المشروع الحالي:

npx skillhub install openteams-lab/openteams/ragic-automation --project

skill.install.customTargetHelp

npx skillhub install openteams-lab/openteams/ragic-automation --target-dir /path/to/skills

المسار المقترح: ~/.claude/skills/ragic-automation/

مراجعة الذكاء الاصطناعي

55
من ١٠٠
جودة التعليمات65
دقة الوصف50
الفائدة52
السلامة التقنية55

Scored 55 due to moderate structure and a functional 3-step MCP workflow pattern. However, it lacks depth in error handling, has generic execution instructions, and description lacks negative triggers.

betamoderatebackend-devsautomation-engineersragic-automationmcp-integrationdatabase-automation
تمت المراجعة بواسطة review-skill-gateway(z-ai/glm-5.2) في 18‏/7‏/2026

محتوى SKILL.md

---
name: ragic-automation
description: "Automate Ragic tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Ragic Automation via Rube MCP

Automate Ragic operations through Composio's Ragic toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/ragic](https://composio.dev/toolkits/ragic)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Ragic connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ragic`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ragic`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Ragic 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 Ragic task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["ragic"]
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 Ragic-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ragic` |
| 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](https://composio.dev)*

الترخيص

الترخيص المُعلن: Apache-2.0

النص الكامل للترخيص متاح في المستودع المصدري.

عرض الترخيص في المستودع المصدري — النسخة المنشورة هناك هي المرجع.