28 skills (repositories by dazzaji) · sorted by popularity
Method for adding agent comments and work to a shared file without overlapping other agents. Creates isolated workspaces per agent with UTC timestamps. Use when told to add comments, reviews, or work to any file.
The English summary is being prepared. Showing the original description.
Check any artifact against an explicit specification and report adherence using the add-comments workspace format. Use when validating plans, scripts, docs, or code changes against a source-of-truth spec.
The English summary is being prepared. Showing the original description.
Join the Antigravity CLI (agy, Gemini 3.5 Flash) to the Interlateral mesh as a native CLI peer with its own tmux session, identity stamping, and the agy.js send helper. Use this instead of the Antigravity desktop-app CDP path.
The English summary is being prepared. Showing the original description.
Agents work in parallel on the same task; judges evaluate and select the winner.
The English summary is being prepared. Showing the original description.
Multiple agents draft a structured document through federated co-authorship and formal voting.
The English summary is being prepared. Showing the original description.
Initialize the standard Interlateral two-agent CLI mesh from a bootstrap agent by running me.sh, launching Claude Opus 4.7 plus Codex 5.5, proving live ACK, and waiting for "Reporting for Duty!". The bootstrap agent is not part of the mesh.
The English summary is being prepared. Showing the original description.
Agents with competing priorities reach consensus through structured trade-offs.
The English summary is being prepared. Showing the original description.
Run an explicitly authorized overnight collaboration with one desktop portal, a durable CLI writer and independent CLI review. Use for unattended work, not routine short tasks.
The English summary is being prepared. Showing the original description.
Coordinate a requested unattended sprint with two explicitly selected desktop control surfaces and independent gated review. Requires proven re-entry on both and a current-run human opt-in.
The English summary is being prepared. Showing the original description.
Run a two-agent independent review/redteam followed by peer collaboration to produce a consensus superset of findings and enumerated revision requests. Use when Codex 5.5 and Claude Opus 4.7 should first critique a matter independently, then exchange work, synthesize the best combined analysis, and finish with a single agreed revision list.
The English summary is being prepared. Showing the original description.
Combine independent work from two or more selected agents into one decision-ready research report, design, or proposal. Preserve useful complementary findings, develop stronger combined options, and present material alternatives only when they exist. Use when multiple perspectives should improve the product without forcing consensus or staging disagreement.
The English summary is being prepared. Showing the original description.
Boot a four-agent visible-terminal team, get all four to "Ready to Rock!", lock live session names to roles, and launch a Lead/Reviewer/Breaker/Verifier sprint without mandate drift.
The English summary is being prepared. Showing the original description.
Periodically inspect a sprint manager and worker sessions against a sprint spec, classify progress, nudge only for real stalls, and always append a checkpoint log beside the sprint file.
The English summary is being prepared. Showing the original description.
Join Claude Code and Codex CLI to the Interlateral mesh in Warp panes by attaching Warp to the standard tmux socket; Warp is the visible terminal surface, tmux remains the transport.
The English summary is being prepared. Showing the original description.
Join Claude Desktop or Codex Desktop to the Interlateral mesh as a desktop peer with its own tmux inbox session, identity, direct ACK, and ledger mirror. This is separate from the standard CLI init flow.
The English summary is being prepared. Showing the original description.
Role-based collaboration pattern (Drafter, Reviewer, Breaker). Assigns roles to available agents via prompt parameters. Use when starting multi-agent dev work.
The English summary is being prepared. Showing the original description.
Boss delegates tasks to workers, reviews their output, and approves or requests changes.
The English summary is being prepared. Showing the original description.
Operate or troubleshoot Interlateral CLI mesh transport: tmux socket discovery, direct-send helpers, comms.md ledger, identity stamping, idle checks, ACK proof, and safe prompt injection. This is comms mechanics only, not a collaboration workflow.
The English summary is being prepared. Showing the original description.
Boot the explicitly selected CLI(s) as the human's concierge: a project-aware side channel that sits ABOVE the running agent system in a shared writable terminal. It answers status questions and handles the human's ad hoc tasking while the working agents collaborate on the mesh — it is not a worker, manager, or gatekeeper, and team progress never waits for it.
The English summary is being prepared. Showing the original description.
All agents have equal voice; decisions made by majority vote.
The English summary is being prepared. Showing the original description.
Coordinate material messages between explicitly selected desktop-backed agents, including Claude, Codex and bb. Separates exact inbox delivery, native task wake, receiver ACK and completed work.
The English summary is being prepared. Showing the original description.
Coordination guidance for the narrow case of multiple desktop-backed agents active concurrently in the same desktop-backed coordination context. Use ONLY when two or more desktop peers are running at the same time; normal CLI agents and single desktop peers should ignore this skill. Read this BEFORE concurrent desktop-to-desktop handoffs to keep sender labels unique, identity routing cooperative, and material handoffs proven.
The English summary is being prepared. Showing the original description.
Blind dual-implementation pattern where two agents independently create artifacts, then a third agent judges which is better and synthesizes learnings.
The English summary is being prepared. Showing the original description.
Run a two-agent proxy approval council for autonomous sprint gates. Use when a sprint needs delegated approval for human gates such as deploy, live mutation, push, cleanup, skip, or shortened watch decisions, while requiring two independent agents to reach consensus that the human principal would approve under written policy and preferences.
The English summary is being prepared. Showing the original description.