latent-briefing

Compact orchestrator trajectories in worker KV caches using task-guided queries.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/lucasFR2/LogiSync --skill latent-briefing-lucasfr2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: latent-briefing
Source: https://github.com/lucasFR2/LogiSync/tree/main/skills/latent-briefing
Command: npx skills add https://github.com/lucasFR2/LogiSync --skill latent-briefing-lucasfr2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill addresses the issue of hierarchical multi-agent systems paying for the same context twice, and provides a solution for efficient memory sharing between agents.

Core Features & Use Cases

  • Representation-Level Memory Sharing: Shares memory at the representation level rather than the text level, compacting the orchestrator trajectory in the worker model's KV cache.
  • Task-Guided Queries: Uses task-guided query vectors derived from the current worker prompt for scoring and selection.
  • Use Case: Ideal for orchestrator-worker or supervisor-specialist systems where workers need access to prior orchestrator state without replaying the full trajectory as text.

Quick Start

Use the latent-briefing skill to share memory between agents for a specific task.

Frequently Asked Questions about latent-briefing

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

FAQPage Schema
What is KV cache compaction for multi-agent memory sharing?

KV cache compaction for multi-agent memory sharing compresses the orchestrator trajectory directly in the worker model's KV cache, enabling representation-level memory sharing without replaying the full text trajectory.

How do I use task-guided queries to compact a worker model's KV cache?

To compact a worker model's KV cache, use task-guided query vectors derived from the current worker prompt to score and select relevant context, applying shared token masks to handle task-specific context efficiently.

Why does my multi-agent system pay for the same context twice?

Hierarchical multi-agent systems pay for the same context twice because workers typically replay the full orchestrator trajectory as text. Representation-level memory sharing via KV cache compaction avoids this redundant processing cost.

Does latent-briefing work for orchestrator-worker or supervisor-specialist multi-agent systems?

Yes, latent-briefing is specifically designed for orchestrator-worker or supervisor-specialist multi-agent systems where workers need access to prior orchestrator state without incurring the cost of replaying the full trajectory as text.

What is the best way to optimize inference-time memory in hierarchical multi-agent systems?

The best way to optimize inference-time memory in hierarchical multi-agent systems is compacting the orchestrator trajectory in the worker model's KV cache using attention matching and task-guided queries for efficient representation-level sharing.

When should I not use representation-level memory sharing for multi-agent systems?

You should avoid representation-level memory sharing when your multi-agent system lacks attention matching capabilities or requires workers to process task-specific context without relying on derived task-guided query vectors and shared token masks.