agy-conductor

Connects Antigravity agents to Limen's peer-conductor protocol for bounded task execution.

Updated May 31, 2026
One-click install
npx skills add https://github.com/4444J99/limen --skill agy-conductor-4444j99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agy-conductor
Source: https://github.com/4444J99/limen/tree/main/.agents/skills/agy_conductor
Command: npx skills add https://github.com/4444J99/limen --skill agy-conductor-4444j99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating AI agents across repositories breaks down when task assignment, budget authority, and completion evidence live in separate tools. This Skill connects Antigravity (Agy) to Limen's symmetric peer-conductor protocol so agents can conduct, execute, review, split, observe, and harvest bounded work packets through a single authenticated CLI or MCP surface. ## Core Features & Use Cases - Session Registration: Register the real Agy session with native run identity, capabilities, worktree, and protection status via limen conduct register. - Bounded Work Execution: Submit or accept validated WorkPacketV1 packets, mutate only under an active lease covering repo, head, branch, path, and scratch resources, then report schema-valid RunReceiptV1 receipts. - Controlled Fanout: Reserve bounded child runs with limen conduct split, where every child attenuates parent authority, scope, spend, deadline, retry, depth, and fanout. - Use Case: An Agy agent picks up a cross-repo refactoring task, heartbeats its lease while working, runs the packet predicate, and reports a durable receipt that the broker can independently verify. ## Quick Start Ask the agent to run the agy-clock script, check conduct capabilities, and register an Agy session with Limen before accepting a work packet.

Frequently Asked Questions about agy-conductor

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

FAQPage Schema
How do I connect an Antigravity agent to Limen task orchestration?▼

Run the agy-clock script, verify access with limen conduct capabilities, then register the session using limen conduct register with your run identity, capabilities, worktree, and protection status. After registration you can submit or accept WorkPacketV1 tasks.

How do I split a Limen work packet into child tasks?▼

Use limen conduct split with the parent run ID and a child packet file before invoking any subagent. Every child must attenuate the parent's authority, scope, spend, deadline, retry, depth, and fanout; hidden fanout is rejected by the broker.

What happens when the Limen broker is unavailable?▼

The skill fails closed for new work when live budget or broker access is unavailable. Claims cannot proceed without the authenticated broker, which prevents duplicated authority and budget accounting across agents.

Can Agy modify the tasks.yaml projection directly?▼

No. The tasks.yaml file is a read-only projection owned by the TABVLARIVS keeper. Agents must mutate state only through the conduct CLI under an active lease covering the repo, exact head, branch, path, and worktree.

How are completed Limen tasks verified and reported?▼

The agent heartbeats its lease during work, runs the packet's executable predicate, rechecks remote heads before pushing, and reports a schema-valid RunReceiptV1 through limen conduct report. Child receipts are collected with limen conduct harvest.