latent-briefing

Compact orchestrator trajectories into worker KV caches using task-guided Attention Matching.

Updated May 18, 2026
One-click install
npx skills add https://github.com/fts-pro/FTS-MMIS-AFRIKA --skill latent-briefing-fts-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: latent-briefing
Source: https://github.com/fts-pro/FTS-MMIS-AFRIKA/tree/main/.agent/skills/latent-briefing
Command: npx skills add https://github.com/fts-pro/FTS-MMIS-AFRIKA --skill latent-briefing-fts-pro

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 by attention from the current worker task prompt, keeping only relevant tokens via a shared global mask and MAD-based thresholding. - Decision framework: Compare Latent Briefing against prefix caching, summarization, and RAG to pick the right cross-agent memory 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 explain how to share orchestrator memory with workers via KV cache compaction 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 inside the worker model's KV cache. Task-guided queries from the current worker prompt score trajectory positions, and a shared mask keeps only the most relevant tokens.

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 queries, a shared global mask, and MAD thresholding instead of per-head top-k selection.

KV cache compaction vs summarization vs RAG for multi-agent systems?▼

Prefix caching suits identical repeated prefixes, summarization gives human-readable auditable state, and RAG handles sparse lookup over large corpora. KV compaction fits when workers need task-specific slices of orchestrator state and the runtime allows KV manipulation.

Can I use KV cache compaction with closed API models?▼

No, Latent Briefing requires infrastructure access to inspect and rewrite worker KV state, which API-only stacks do not expose. It also assumes orchestrator and worker share the same model space, tokenizer, and attention layout.

Why does aggressive KV compaction hurt accuracy?▼

A higher threshold tau drops more trajectory positions, and accuracy falls off a cliff once task-relevant evidence is removed. The optimal threshold is workload-dependent, so tune on validation data tracking accuracy, worker tokens, and retention rate together.