latent-briefing

Compact orchestrator trajectories into worker KV caches using Attention Matching for multi-agent memory sharing.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Sambhav242005/Major-Project --skill latent-briefing-sambhav242005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: latent-briefing
Source: https://github.com/Sambhav242005/Major-Project/tree/main/.agents/skills/latent-briefing
Command: npx skills add https://github.com/Sambhav242005/Major-Project --skill latent-briefing-sambhav242005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Hierarchical multi-agent systems waste tokens by replaying the full orchestrator trajectory into every worker call, while summarization adds latency and loses information. This Skill explains how to transfer orchestrator state to workers at the representation level by compacting the worker model's KV cache instead of re-serializing text. ## Core Features & Use Cases - Task-guided KV compaction: Score trajectory positions using queries from the current worker prompt, keeping only what the worker will actually attend to. - Shared global mask with MAD thresholding: Aggregate attention scores across layers and heads into one mask, using a robust median + tau * MAD threshold instead of per-head top-k. - Decision framework: Compare Latent Briefing against prefix caching, summarization, and RAG to pick the right mechanism for your bottleneck. - Use Case: In a recursive orchestrator-worker system doing long-document QA, compact the growing orchestrator trajectory before each worker call to cut worker tokens while preserving task-relevant reasoning state. ## Quick Start Ask the AI to design a KV cache compaction strategy for your orchestrator-worker agent system using task-guided Attention Matching.

Frequently Asked Questions about latent-briefing

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

FAQPage Schema
How do I share memory between agents without summarization?

Share memory at the representation level by compacting the orchestrator trajectory directly in the worker model's KV cache. Task-guided queries from the current worker prompt score which trajectory positions to retain, avoiding the latency and information loss of text summarization.

What is Attention Matching KV cache compaction?

Attention Matching seeks a smaller KV cache whose attention outputs approximate the full cache, using compacted keys, bias corrections, and reconstructed values. Latent Briefing adapts it with task-guided query vectors and a shared global mask across heads for batched inference.

Can I use KV cache compaction with API-only LLM providers?

No, Latent Briefing requires runtime access to inspect and rewrite worker KV tensors, which hosted text-generation APIs do not expose. For API-only stacks, use structured text handoffs, context compression, or external memory systems instead.

KV cache compaction vs prefix caching: which should I use?

Prefix caching reuses identical prompt prefixes and is the cheapest first optimization with no information loss. KV cache compaction adds task-conditioned selective retention inside a reused trajectory, which pays off when workers need specific slices of evolving orchestrator state.

Why does aggressive KV compaction hurt worker accuracy?

A high threshold drops trajectory positions the worker actually needs, causing accuracy cliffs. The optimal retention rate depends on document length, question difficulty, and trajectory quality, so tune the threshold on validation data rather than using one global value.