context-updater

Identify data gaps in project-context.json and emit a CONTEXT_UPDATE block.

3|1|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/metraton/gaia --skill context-updater-metraton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-updater
Source: https://github.com/metraton/gaia/tree/main/skills/context-updater
Command: npx skills add https://github.com/metraton/gaia --skill context-updater-metraton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

project-context.json is shared memory across agents. When you discover something about the project that other agents would need, you are the only one who saw it. If you do not write it, the next agent starts from zero on that question.

Core Features & Use Cases

  • Emit a CONTEXT_UPDATE block to modify project-context.json when new data is discovered or when existing data drifts.
  • Respect write permissions and merge semantics (ADD, MERGE, UNION, OVERWRITE, NO-DELETE) to maintain a clean audit trail.
  • Use case: after identifying a new resource in a cluster, emit a CONTEXT_UPDATE to capture the resource details under the appropriate writable section.

Quick Start

Emit a CONTEXT_UPDATE block after analysis and before the json:contract block to persist findings in project-context.json.

Frequently Asked Questions about context-updater

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

FAQPage Schema
How do I keep project context in sync across multiple agents?

To keep project context in sync across multiple agents, you emit a CONTEXT_UPDATE block that modifies project-context.json. This shared memory file captures new data or drift so subsequent agents start with the latest findings.

What merge semantics apply when updating shared memory in agent coordination?

Merge semantics for updating shared memory include ADD, MERGE, UNION, OVERWRITE, and NO-DELETE rules. These constraints maintain a clean audit trail by allowing agents to modify only sections they have write permissions for.

How does drift detection work for shared project context files?

Drift detection works by identifying data gaps or changes in project-context.json. When an agent discovers new project details, it prepares a CONTEXT_UPDATE block to persist those findings before the next agent begins its task.

Do I need write permissions to update context-management files in a multi-agent workflow?

Yes, you need write permissions to update context-management files. Agents must respect write-permission constraints and emit updates only for sections they own, ensuring modifications remain auditable and prevent unauthorized overwrites.

When should I emit a CONTEXT_UPDATE block during agent coordination?

You should emit a CONTEXT_UPDATE block after analysis and before the json:contract block. This timing ensures newly discovered resources or drift are persisted immediately into project-context.json for other agents.