multica-autopilots
Use when creating, updating, inspecting, triggering, or debugging a Multica autopilot (scheduled, webhook, or manual).
- Installs
- 39
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/multica-ai/multica --skill multica-autopilots- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads multica-autopilots automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Multica Autopilots
Quick start
Autopilots are durable automations. Read before mutating:
multica autopilot list --output json
multica autopilot get <autopilot-id> --output json
multica autopilot runs <autopilot-id> --output json
Do not run trigger, delete, trigger-delete, or trigger-rotate-url to test. Those are real side effects.
Core model
An autopilot is not an agent. It is a rule that dispatches work to an agent, or to a squad's leader agent.
The chain is: trigger fires (schedule, webhook, or manual) -> autopilot_run row -> execution_mode decides output -> assignee readiness check -> issue/task execution -> run status sync. Webhooks have a durable admission step in front: HTTP ingress stores a queued webhook_delivery, synchronously creates or reuses its idempotent run, and returns 200 with status=accepted|skipped plus run_id; a database-leased worker then resumes accepted runs and owns recoverable issue/task dispatch.
Execution modes:
create_issuecreates a Multica issue, making the run visible as issue state.run_onlycreates an agent task directly. No issue is created; any durable report location has to come from other task context or instructions.
issue-title-template only supports {{date}}. Do not invent {{trigger_id}}, {{branch}}, or other variables.
CLI
multica autopilot list --output json
multica autopilot get <autopilot-id> --output json
multica autopilot create --title "<title>" --description "<task prompt>" --agent <agent-name-or-id> --mode create_issue|run_only --output json
multica autopilot update <autopilot-id> --status active|paused --output json
multica autopilot runs <autopilot-id> --output json
multica autopilot trigger-add <autopilot-id> --kind schedule --cron "0 9 * * *" --timezone Asia/Shanghai --output json
multica autopilot trigger-add <autopilot-id> --kind webhook --label "ci" --output json
multica autopilot trigger <autopilot-id> --output json
multica autopilot trigger-rotate-url <autopilot-id> <trigger-id> --yes --output json
Use trigger only when the user explicitly asks for a manual run. Use trigger-rotate-url only when rotating a webhook URL; the old URL stops being valid.
autopilot get redacts webhook_token, webhook_path, and webhook_url by default while reporting whether a token exists and its non-sensitive hint. Only add --show-secrets when the user explicitly asks to retrieve the live webhook credential; the command warns on stderr. Do not paste webhook tokens or signing material into comments, logs, docs, or PRs.
Debugging
For "why didn't it run":
multica autopilot get <id> --output json— status, mode, assignee, triggers.multica autopilot runs <id> --output json— run status and failure reason.- If assigned to a squad, inspect the squad:
multica squad get <squad-id> --output json; execution goes to the leader. - Inspect the target agent/runtime:
multica agent get <agent-id> --output jsonandmultica runtime list --output json. - For webhooks, inspect delivery status:
queuedmeans the worker has not completed dispatch;failedcarries the worker error. A provider retry with the sameX-GitHub-Delivery/Idempotency-Keyreuses the original delivery. - For
create_issue, inspect the created issue if the run records one.
Side effects
These mutate durable state or start work: create, update, delete, trigger add/update/delete/rotate, trigger, and webhook calls to /api/webhooks/autopilots/{token}.
More source-backed details: references/autopilots-source-map.md.
FAQ
What does the multica-autopilots skill do?
Use when creating, updating, inspecting, triggering, or debugging a Multica autopilot (scheduled, webhook, or manual).
How do I install multica-autopilots?
Run npx skills add https://github.com/multica-ai/multica --skill multica-autopilots in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/multica-autopilots/ (personal) or .claude/skills/multica-autopilots/ (project).
Which AI agents can use multica-autopilots?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is multica-autopilots safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains multica-autopilots?
It is published by multica-ai in multica-ai/multica. It has 39 recorded installs.
More from multica-ai/multica
multica-working-on-issues
multica-ai/multica
Superseded by the multica-platform skill — load that instead. This file only records where the Multica issue contracts moved to.
multica-creating-agents
multica-ai/multica
Use when creating, inspecting, or debugging a Multica agent definition via the multica agent CLI or POST /api/agents. Not for assigning issues to agents that already exist, and not for runtime task prompts.
multica-projects-and-resources
multica-ai/multica
Use when creating, inspecting, updating, or debugging Multica projects and their resources (githubrepo, localdirectory).
multica-squads
multica-ai/multica
Use when creating, inspecting, updating, assigning to, or debugging a Multica squad, including how leader routing picks who runs.
multica-skill-importing
multica-ai/multica
Use when asked to import or install a specific skill into this Multica workspace from a URL or slug. Not for choosing which skill the user needs; never treat a local installer such as npx skills add as the final install.
multica-runtimes-and-repos
multica-ai/multica
Use when a Multica runtime or daemon misbehaves: agent not running, task not claimed, runtime offline, workdir or session reuse, repository checkout.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.