latent-briefing

Compact orchestrator KV cache state for task-conditioned worker memory sharing.

2|Updated May 30, 2026
One-click install
npx skills add https://github.com/virahitvin8/crafty-gis --skill latent-briefing-virahitvin8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: latent-briefing
Source: https://github.com/virahitvin8/crafty-gis/tree/main/GIT_STAR/assignment-generator/antigravity-skills-main/antigravity-skills-main/skills/latent-briefing
Command: npx skills add https://github.com/virahitvin8/crafty-gis --skill latent-briefing-virahitvin8

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 with Attention Matching. ## Core Features & Use Cases - Task-Guided KV Compaction: Score trajectory positions using queries from the current worker prompt and retain only the positions the worker actually attends 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 state-transfer mechanism for your stack. - Use Case: In a recursive orchestrator-worker system answering long-document questions, compact the growing trajectory before each worker call to cut worker tokens while preserving answer accuracy. ## Quick Start Ask the assistant to design a KV cache compaction strategy for an orchestrator-worker system where workers need task-relevant slices of the orchestrator trajectory.

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. Attention Matching scores trajectory positions against the current task prompt and keeps only the positions the worker attends to, avoiding lossy text summaries.

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 across heads, and MAD-based thresholding.

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 retrieval instead.

Latent Briefing vs RAG for multi-agent context sharing?

RAG retrieves documents from an external corpus but does not preserve the orchestrator's evolving reasoning state. Latent Briefing transfers task-relevant slices of the existing trajectory directly in latent space, making it complementary to retrieval rather than a replacement.

Why does aggressive KV compaction hurt accuracy?

Higher threshold values drop more trajectory positions, and retention needs vary across document lengths and question difficulty. Accuracy cliffs appear when compaction removes evidence the worker needs, so tune tau on validation data tracking quality and tokens together.