appveyor-automation

Automate Appveyor continuous integration tasks through the Rube MCP gateway.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill appveyor-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: appveyor-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/appveyor-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill appveyor-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the need for manual interaction with the Appveyor web interface, allowing developers to trigger builds, monitor status, and manage deployments directly through their AI agent.

Core Features & Use Cases

  • Automated CI Management: Trigger builds and check project status without leaving the development environment.
  • Connection Management: Securely handle Appveyor authentication via the Rube MCP gateway.
  • Use Case: A developer can instruct their agent to check the status of a failing build, identify the error, and re-trigger the deployment pipeline after a code fix.

Quick Start

Ask the agent to search for available Appveyor tools and then trigger a build for the specified project.

Frequently Asked Questions about appveyor-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trigger an Appveyor build using this skill?

First, use RUBE_SEARCH_TOOLS to identify the correct build trigger tool, then call RUBE_MULTI_EXECUTE_TOOL with the required project and branch arguments.

What should I do if my Appveyor connection is inactive?

Call RUBE_MANAGE_CONNECTIONS with the appveyor toolkit to verify your status and follow the provided authentication link to re-establish the connection.

Can I use this skill to monitor build logs?

Yes, use RUBE_SEARCH_TOOLS to find log-retrieval tools within the Appveyor toolkit, then execute the tool using the specific build ID from your session.

Why must I call RUBE_SEARCH_TOOLS before executing commands?

Tool schemas and available endpoints change frequently; calling RUBE_SEARCH_TOOLS ensures your agent uses the most current arguments and prevents execution errors.

Are there limitations to the Appveyor automation?

The skill is limited by the tools exposed via the Rube MCP gateway; ensure your Appveyor account has the necessary permissions for the requested operations.