multica-autopilots

Use when creating, updating, inspecting, triggering, or debugging a Multica autopilot (scheduled, webhook, or manual).

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, executable reference that balances a dense domain model with concrete CLI commands and a clear debugging workflow. Progressive disclosure is handled cleanly with one real referenced file.

Dimension	Reasoning	Score
Conciseness	Largely lean and information-dense, assuming Claude's competence, with only minor over-explanation (e.g. the webhook durable-admission paragraph) that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready CLI commands covering list/get/create/update/runs/trigger-add/trigger/rotate, plus concrete numbered debugging commands for the common cases.	5 / 5
Workflow Clarity	A numbered 6-step debugging workflow and a 'read before mutating' checkpoint give a clear sequence with verification, though an explicit post-mutation validation checklist is absent.	4 / 5
Progressive Disclosure	Clear sectioned overview (Quick start, Core model, CLI, Debugging, Side effects) with a single well-signaled one-level reference to references/autopilots-source-map.md, which exists in the bundle.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tight, concrete description that clearly states both capabilities and trigger conditions for a well-scoped niche. It avoids fluff and over-claims while covering the main operations a user would request.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions ('creating, updating, inspecting, triggering, or debugging') plus three trigger kinds, giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers 'what' (the enumerated create/update/inspect/trigger/debug actions) and 'when' ('Use when...' with scheduled/webhook/manual triggers) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keywords a user would say ('create', 'debug', 'trigger', 'scheduled', 'webhook'), but lacks the synonym and extension richness that defines a 5.	4 / 5
Distinctiveness Conflict Risk	Targets a narrow, named niche ('Multica autopilot') with distinct triggers, making conflict with other skills unlikely.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: multica-ai/multica
Path: server/internal/service/builtin_skills/multica-autopilots/SKILL.md
Commit: 11ab949

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.