Do I need API keys to use Appveyor automation via Rube MCP?

No API keys are required; add the MCP server URL and authorize through the Rube MCP workflow.

What should I do if tool schemas change?

Always fetch current schemas with RUBE_SEARCH_TOOLS before using a tool slug; do not hardcode slugs or arguments.

How can I ensure I’m connected to Appveyor?

Check RUBE_MANAGE_CONNECTIONS for the toolkit appveyor and confirm the status is ACTIVE before executing tools.

appveyor-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/appveyor-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Appveyor Automation via Rube MCP

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

Toolkit docs: 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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit appveyor
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: "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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/appveyor-automation/SKILL.mdView on GitHub

Overview

Automate Appveyor operations using Composio's Appveyor toolkit via Rube MCP. This workflow emphasizes discovering current tool schemas before execution and establishing a verified Appveyor connection for secure, repeatable automation.

How This Skill Works

You add the Rube MCP endpoint, verify connectivity with RUBE_SEARCH_TOOLS to fetch tool schemas, then connect to Appveyor with RUBE_MANAGE_CONNECTIONS. Once connected, you discover available tools, pick a tool_slug, and run RUBE_MULTI_EXECUTE_TOOL using the provided memory and session_id.

When to Use It

When you need up-to-date Appveyor tool schemas and want to avoid hardcoding slugs.
When setting up or verifying the Appveyor connection through Rube MCP before automation.
When you want to discover available Appveyor operations and their required arguments.
When executing a discovered tool within a session to ensure continuity.
When batching multiple Appveyor actions in a single workflow using RUBE_MULTI_EXECUTE_TOOL.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds to ensure tool schemas are current.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using a session.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs for related actions and handle pagination tokens if present.

Example Use Cases

Discover Appveyor tools and trigger a build by executing the appropriate discovered tool slug.
Verify the Appveyor connection is ACTIVE and retrieve the latest build status for a project.
List available Appveyor operations for a repository and choose one to automate.
Authenticate and establish an Appveyor connection using the provided auth flow.
Run multiple Appveyor tasks in a single workflow using RUBE_MULTI_EXECUTE_TOOL with memory and session.

Frequently Asked Questions

Add this skill to your agents