multica-autopilots

Manage Multica autopilot lifecycles across schedule, webhook, and manual triggers.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/waltcow/multica --skill multica-autopilots
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multica-autopilots
Source: https://github.com/waltcow/multica/tree/main/server/internal/service/builtin_skills/multica-autopilots
Command: npx skills add https://github.com/waltcow/multica --skill multica-autopilots

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates Multica autopilot lifecycle management.

Core Features & Use Cases

  • Manage autopilot lifecycles end-to-end (create, update, delete) and observe runs across agents and squads.
  • Support multiple execution modes (create_issue vs run_only) and triggers (schedule, webhook, manual).
  • Enforce admission rules via squad leaders and provide observability, run history, and URL rotation boundaries.

Quick Start

Create an autopilot named "daily-health-check" that triggers on a daily schedule and reports results back to a tracked issue for visibility.

Frequently Asked Questions about multica-autopilots

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

FAQPage Schema
How do I automate scheduled automation triggers for recurring tasks?

You can trigger autopilots via webhooks, schedules, or manual execution, with each run recorded for observability and traceability. The system enforces readiness checks and side-effect boundaries across all trigger types.

How does webhook trigger handling work for automation orchestration?

Webhook triggers initiate autopilot runs by sending external event payloads to the orchestration system, which validates readiness, applies admission rules via squad leaders, and executes the defined lifecycle side-effects.

Can I enforce approval workflows before running automation triggers?

Squad leaders enforce admission rules to gate autopilot execution readiness, providing safeguards and traceability. This governance mechanism ensures only approved automation runs proceed across agents and squads.

What is the best way to manage automation lifecycle orchestration end-to-end?

End-to-end lifecycle management handles creating, updating, triggering, and debugging autopilots across schedule, webhook, and manual triggers. It supports execution modes like create_issue and run_only with side-effect boundaries.

How do I debug failed automation runs and observe execution history?

Built-in observability and run history tracking inspect execution states to debug failed automation runs. Readiness checks and side-effect boundaries provide traceability to identify where the autopilot lifecycle failed.