multica-runtimes-and-repos

Diagnose Multica runtime daemon heartbeats, task claiming, and repo checkout context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose and debug Multica runtimes, including daemon heartbeats, task claiming, workspace/session reuse, and repository checkout context, so teams can quickly surface root causes.

Core Features & Use Cases

  • Runtime status diagnostics: check runtime online/offline state and last_seen_at hints to determine agent activity.
  • Daemon and claim tracing: inspect the daemon heartbeat and task-claim chain to identify where a task stalls.
  • Repo/workspace context validation: verify available workspace repos, project resources, and local_directory caveats to ensure correct task context.
  • Safe diagnostic workflow: provide a guided, non-destructive interrogation of the runtime and related resources.

Quick Start

Check the runtime status for a given agent and verify the daemon heartbeat to confirm proper task execution flow.

Frequently Asked Questions about multica-runtimes-and-repos

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

FAQPage Schema
How do I diagnose a Multica runtime that is not running my agent?

To diagnose a Multica runtime not running your agent, check the runtime online/offline state and inspect last_seen_at hints to determine agent activity and surface root causes.

Why does a task stall during the daemon heartbeat and claim chain?

A task stalls during the daemon heartbeat and claim chain when the runtime fails to properly claim the task, requiring you to trace the daemon heartbeat to identify where the execution flow breaks.

How do I verify repository checkout context and local_directory caveats for a workspace session?

Verify repository checkout context by inspecting available workspace repos, project resources, and local_directory caveats to ensure the correct task context is applied during session reuse.

What is the best way to safely debug runtime online/offline state without causing damage?

The best way to safely debug runtime online/offline state is using a guided, non-destructive interrogation workflow that enforces safe diagnostic commands while gathering task context.

When do I need to check runtime status and daemon heartbeat for task execution?

You need to check runtime status and daemon heartbeat when an agent does not run, when workspace or session reuse is required, or when a repository checkout context needs verification.