omk-global-rules
Global open-multi-agent-kit operating rules: avoid repeated instructions, use todos, subagents, relevant skills, MCP tools, quality gates, and concise factual reports.
git clone --depth 1 https://github.com/dmae97/open-multi-agent-kit /tmp/omk-global-rules && cp -r /tmp/omk-global-rules/templates/skills/kimi/omk-global-rules ~/.claude/skills/omk-global-rulesSKILL.md
## Rules Apply these rules silently. 1. Do not make the user repeat common instructions. 2. Use todos for multi-step work. 3. Use subagents for non-trivial tasks. 4. Use relevant skills before implementation. 5. Use MCP tools when configured and useful. 6. Treat project-local graph memory as the default project/session source of truth; use memory tools when available and never store secrets. 7. Prefer Kimi Okabe + SendDMail checkpoints for risky context transitions and rollback recovery. 8. Prefer plan-first execution. 9. Prefer small diffs. 10. Verify before completion. 11. Report exact changed files and commands. 12. Never overclaim test results. ## Final Response ```txt Changed: Files: Commands: Result: 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.