omk-context-broker
Context and memory policy for long-running Kimi coding sessions, DAG workers, and repeated project work.
git clone --depth 1 https://github.com/dmae97/open-multi-agent-kit /tmp/omk-context-broker && cp -r /tmp/omk-context-broker/templates/skills/kimi/omk-context-broker ~/.claude/skills/omk-context-brokerSKILL.md
## Context Broker Policy Use this skill when a task spans many files, many turns, multiple workers, or a long session. ## Local Graph Memory Project-local ontology graph memory is the default source of truth for project/session memory. Use `omk_read_memory`, `omk_write_memory`, `omk_memory_mindmap`, `omk_graph_query`, `omk_read_run_memory`, and `omk_write_run_memory` when the omk-project MCP exposes them. `.omk/memory/` is a local mirror/cache for reviewability. ## Okabe / D-Mail Checkpoints Use Kimi Code Okabe + `SendDMail` for smart context recovery: - send a D-Mail before destructive/risky refactors, multi-agent handoffs, or `/compact`; - include the current goal, branch/changed files, tests run, blockers, and intended next action; - keep D-Mail concise and pair it with project-local graph memory for durable project/session recall. ## Memory Files Use: - `.omk/memory/project.md` - `.omk/memory/decisions.md` - `.omk/memory/commands.md` - `.omk/memory/risks.md` - `.omk/runs/<run-id>/events.jsonl` - `.omk/runs/<run-id>/plan.md` - `.omk/runs/<run-id>/final-report.md` ## Rules - Store stable project facts in project-local graph project memory. - Store temporary run/session facts in project-local graph run memory. - Store decisions with reason, date, and affected files. - Do not store secrets. - Before compacting, summarize active state: - current goal - completed tasks - pending tasks - changed files - failing commands - blockers ## Decision Record Format ```txt Date: Decision: Reason: Alternatives: Affected files: Risk: ```
Persistent memory, recall, session replay, and memory-governance workflow adapted from rohitg00/agentmemory for OMK. Use when setting up agent memory, deciding what to remember, importing/replaying sessions, reducing repeated context, or auditing memory safety.
Minimal, goal-driven, surgical coding workflow adapted from forrestchang/andrej-karpathy-skills for OMK. Use for coding, refactoring, debugging, and review tasks where assumptions, overengineering, or broad edits could cause regressions.
Legal workflow drafting, triage, review, research planning, legal operations, law-student or clinic support, and legal AI governance adapted from Anthropic claude-for-legal. Use for commercial, privacy, product, corporate, employment, regulatory, AI governance, IP, litigation, legal-clinic, and law-student tasks. Draft-only; attorney review and current source verification required.
Real-engineering alignment, shared-language, TDD, diagnosis, and architecture-review workflow adapted from mattpocock/skills for OMK. Use before non-trivial implementation, ambiguous product work, debugging loops, test-first changes, or codebase architecture cleanup.
Managed-agent teamwork, issue assignment, progress tracking, reusable-skill compounding, and handoff workflow adapted from multica-ai/multica for OMK. Use when coordinating multiple agents, converting work into agent-ready tasks, tracking blockers, or turning repeated solutions into skills.
Review AdaptOrch, OMK, and similar DAG multi-agent orchestration frameworks. Use when assessing DAG node responsibility, dependency edges, worker write authority, fallback/retry/timeout/evidence gates, review/merge boundaries, or reproducible decision traces.
Optional read-only OMK web/social/video research workflow inspired by Panniantong/Agent-Reach. Use for web search, current social evidence, YouTube/Bilibili/Reddit/Twitter/X/RSS/GitHub public research, and Agent Reach availability checks without auto-installing or collecting credentials.
Backend API review for NestJS, Express, FastAPI, database access, validation, auth, error handling, and API contracts.