omk-evidence-contract
Generate task-specific evidence contracts before a done/completed claim. Use for feature, bugfix, refactor, research, release, security, docs, or orchestration tasks that need changed files, non-empty diffs, test/build/typecheck results, citations, uncertainty, conflicting evidence, and final risk notes.
git clone --depth 1 https://github.com/dmae97/open-multi-agent-kit /tmp/omk-evidence-contract && cp -r /tmp/omk-evidence-contract/templates/skills/kimi/omk-evidence-contract ~/.claude/skills/omk-evidence-contractSKILL.md
## Evidence Contract Use this before declaring work complete. Define the claim first, then list the minimum evidence that can prove or falsify it. ## Process 1. Classify the task type: feature, bugfix, refactor, research, release, security, docs, or orchestration. 2. Write the completion claim in one sentence. 3. List required evidence and the command or artifact that proves it. 4. Mark any unavailable evidence as a gap with a concrete reason. 5. Report remaining risk without converting gaps into success. ## Feature / Bugfix / Refactor Evidence - Changed files. - Non-empty relevant git diff, unless the task was explicitly read-only. - Unit or integration test result for changed behavior. - Build, typecheck, lint, or static-analysis result appropriate to the stack. - Regression note covering edge cases and untested paths. ## Research Evidence - Cited sources or local files inspected. - Date checked for external or version-sensitive facts. - Confidence and uncertainty. - Conflicting evidence or missing primary-source coverage. - Recommendation with assumptions separated from verified facts. ## Release / Security Evidence - Secret scan or explicit reason it was not run. - Audit, permission, or destructive-action review when relevant. - Changelog/PR/release checklist evidence. - Rollback or recovery note for risky changes. ## Output ```txt Task type: Completion claim: Required evidence: Evidence gathered: Gaps: Conflicting evidence: Final risk: Done verdict: ```
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.