$ ~/registry/skill/composiohq-composio-skills-appveyor-automation

SKILL

appveyor-automation

Name: appveyor-automation
Author: Composio

Automate AppVeyor builds and pipeline tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill itself is an open-source prompt-only artifact with no declared built-in secrets, local execution, or local data access, so its baseline risk is low. However, it is designed to route actions through remote Rube MCP and Appveyor integrations, so actual data egress and third-party connection behavior should be reviewed at use time.

CredentialsCaution

The material says the skill itself needs no API keys, but the README explicitly requires an active Appveyor connection via `RUBE_MANAGE_CONNECTIONS` and an external auth flow. So the skill does not directly embed secrets, yet it guides users to grant third-party access to Appveyor, creating normal credential delegation and misconfiguration risk.

Network egressCaution

The README instructs users to add the remote MCP endpoint `https://rube.app/mcp` and invoke Appveyor tools through Composio/Rube. This means task content, arguments, and session data may be sent to the stated third-party service. The endpoint is explicit and function-related, so this is expected egress, but the scope of transmitted data still warrants attention.

Code executionLow risk

System checks mark it as prompt-only, and the material only provides workflow instructions and tool invocation examples. There is no indication that the skill itself starts local processes, runs scripts, or requests system-level execution privileges.

Data accessLow risk

There is no description of the skill directly reading or writing local files, databases, the clipboard, or other host resources; the skill itself behaves more like operational guidance. Any real data access would mainly depend on the downstream Rube/Appveyor tools rather than this prompt artifact.

Supply chainLow risk

The source is a GitHub open-source repository, the system marks it as open-source, and community adoption is high (64.7k stars); these are strong risk-lowering signals. Although the license is unspecified and maintenance status is unknown, the provided material shows no red flags such as closed-source opacity, dubious origin, or obvious malicious injection.

Recommendations

Enable it only after you trust `rube.app/mcp` and the Composio integration, and review their privacy and data-handling practices.
Use least-privilege authorization when connecting Appveyor; avoid granting repository or account scopes unrelated to the automation task.
Before sending task content, build logs, or project identifiers, verify that they do not contain sensitive information.
Prefer to pin and review the actual tool list and schemas before execution, rather than blindly running high-privilege operations returned by search.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "appveyor-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/appveyor-automation/SKILL.md
2. Save it as ~/.claude/skills/appveyor-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Buildkite pipelines and build management tasks through Rube MCP.

ComposioGet→

$ loading_