multica-onboarding

Guides new Multica workspace members from first message to a confirmed issue execution.

48.5k|6.2k|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/multica-ai/multica --skill multica-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multica-onboarding
Source: https://github.com/multica-ai/multica/tree/main/server/internal/service/builtin_skills/multica-onboarding
Command: npx skills add https://github.com/multica-ai/multica --skill multica-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

New Multica workspace members often don't know how to turn their goals into agent-executed work. This Skill runs Mika's interactive onboarding conversation, carrying a member from their first message to one real, confirmed, issue-based execution so they learn the working model by watching it happen.

Core Features & Use Cases

  • Starter Play Handling: Responds to the three product-fixed starter cards (Board, Delegate, Digest) with tailored flows, each limited to at most one clarifying question.
  • Timezone-Safe Automations: For the digest play, reads the member's IANA timezone from the profile and passes it to multica autopilot trigger-add --timezone, asking first when the zone is unknown to avoid UTC misconfiguration.
  • Issue-Shaped Execution: Previews and confirms a plan, then creates the minimal structure (one issue by default, optionally a project or specialist agent) and starts work via todo assignment.
  • Use Case: A new member clicks the "Board" starter card; Mika proposes a project with 4–8 prioritized issues based on their kickoff profile, confirms the preview, creates it, and hands back the issue identifier with next steps.

Quick Start

Activate this skill when a product-authored kickoff begins Mika's onboarding conversation and continue from the member's first message toward one confirmed issue execution.

Frequently Asked Questions about multica-onboarding

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

FAQPage Schema
How does Multica onboarding turn a member goal into an issue?

Mika reduces the member's goal to the smallest judgeable outcome, shows a compact preview with title, deliverables, and assignee, then asks one confirmation question. After a clear yes, it creates the issue with full execution context and assigns it as todo to start the agent.

What are the starter plays in Multica onboarding?

Three product-fixed starter cards trigger plays: Board (propose a project with 4–8 prioritized issues), Delegate (run one research task as an issue assigned to Mika), and Digest (create one daily 09:00 progress-summary autopilot in the member's timezone).

How do I set the timezone for a Multica digest autopilot?

Read the member's IANA timezone from the kickoff profile block and pass it to multica autopilot trigger-add --timezone. If the profile reads unknown, ask the member for their timezone first, because omitting the flag schedules the digest in UTC.

When should onboarding create a project or specialist agent instead of one issue?

Default to a single issue assigned to Mika. Propose a specialist agent only when the goal needs a capability Mika lacks and the member will reuse it, and propose a project only when the goal splits into three or more issues sharing one outcome. Never create a squad during onboarding.

Why shouldn't Mika promise to report back when an issue finishes?

The agent's turn ends when its reply is sent, and nothing wakes it when the run completes, so a promised follow-up would never arrive. Instead, Mika tells the member where to watch progress and that they can message at any time.