latent-briefing

Compact KV caches to share task-specific orchestrator state with workers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Replaying the full orchestrator reasoning trajectory to every worker inflates token usage and introduces latency, while summarization loses critical context needed for downstream tasks.

Core Features & Use Cases

  • Representation‑level sharing: Retains only the KV positions most relevant to the current worker task, avoiding full‑text handoff.
  • Task‑guided attention scoring: Uses the worker’s task prompt to score trajectory tokens and build a shared global mask.
  • Robust MAD thresholding: Applies median‑plus‑MAD to decide which KV entries to keep, adaptable to different workloads.
  • Use Cases: Hierarchical multi‑agent pipelines, recursive language model orchestration, and any system where workers require selective slices of the orchestrator’s latent state without costly text replay.

Quick Start

Ask the agent to compact the orchestrator’s KV cache for the upcoming worker task.

Frequently Asked Questions about latent-briefing

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

FAQPage Schema
How do I share orchestrator state with worker agents without inflating token usage?

Share orchestrator state by compacting the KV cache into task-specific slices. This retains only the KV positions most relevant to the current worker task, avoiding full-text handoff and reducing token replay latency.

How does task-guided attention scoring work for selective KV cache retention?

Task-guided attention scoring uses the worker's task prompt to score trajectory tokens and build a shared global mask. It applies median-plus-MAD thresholding to decide which KV entries to keep for downstream tasks.

Do I need access to worker model KV tensors to compact orchestrator state?

Yes, compacting orchestrator state requires direct access to the worker model's KV tensors. You also need the ability to compute task-guided attention scores to selectively retain the necessary latent reasoning trajectory.

What is the best way to pass context in hierarchical multi-agent pipelines without text replay?

Use representation-level sharing to pass context in hierarchical multi-agent pipelines. This method transfers selective slices of the orchestrator's latent state directly, preventing the latency and context loss of summarization.

Why does summarizing orchestrator reasoning lose critical context for downstream tasks?

Summarizing orchestrator reasoning loses critical context because it drops intermediate reasoning steps. Compact KV cache sharing avoids this by retaining exact latent state positions needed for downstream tasks.

When should I not use KV cache compaction for multi-agent orchestration?

You should not use KV cache compaction if your system lacks access to worker model KV tensors. It is also unsuitable if your workload cannot leverage task-guided attention scoring for selective retention.