Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Appveyor Automation via Rube MCP

agent tool_use skill risk: medium

Appveyor Automation via Rube MCP

Instructs the model to automate Appveyor operations through Composio's Appveyor toolkit via Rube MCP by first calling RUBE_SEARCH_TOOLS, verifying connections with RUBE_MANAGE_CONN…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: appveyor-automation
description: "Automate Appveyor tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Appveyor Automation via Rube MCP

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

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

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Appveyor connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `appveyor`
- 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 `appveyor`
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: "Appveyor 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 Appveyor task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["appveyor"]
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 Appveyor-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `appveyor` |
| 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)*

REQUIRED CONTEXT

  • Rube MCP connection
  • active Appveyor connection via RUBE_MANAGE_CONNECTIONS

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_GET_TOOL_SCHEMAS
  • RUBE_REMOTE_WORKBENCH

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Always discover available tools before executing workflows
  4. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  5. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  6. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  7. Use exact field names and types from the search results
  8. Reuse session IDs within a workflow
  9. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • verify active connection before execution
  • reuse session ids
  • include memory parameter

FAILURE MODES

  • Hardcoding tool slugs or arguments without first calling RUBE_SEARCH_TOOLS
  • Executing tools before confirming ACTIVE connection status
  • Omitting the memory parameter from RUBE_MULTI_EXECUTE_TOOL
  • Failing to reuse session IDs or handle pagination

EXAMPLES

Includes multiple example RUBE tool calls (SEARCH_TOOLS, MANAGE_CONNECTIONS, MULTI_EXECUTE_TOOL) with sample arguments and session handling.

CAVEATS

Dependencies
  • RUBE_SEARCH_TOOLS available
  • Active Appveyor connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Concrete example of a complete end-to-end tool call sequence
  • Error handling or retry strategy
Ambiguities
  • Placeholder text 'your specific Appveyor task' is left generic without examples

QUALITY

OVERALL
0.78
CLARITY
0.78
SPECIFICITY
0.88
REUSABILITY
0.65
COMPLETENESS
0.82

IMPROVEMENT SUGGESTIONS

  • Replace the generic use_case placeholder with 2-3 concrete examples
  • Add a minimal working example of RUBE_MULTI_EXECUTE_TOOL with sample arguments

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT