Brain Conflict
How to detect and resolve conflicting beliefs in the INITE Brain knowledge graph — the COMPETING fact status, get_competing_facts, detect_contradiction preflight, and the human-in-the-loop adjudication workflow. Use when the timeline shows two facts disagreeing on the same predicate, or when an agent needs to decide what to record without making the disagreement worse.
Install
/plugin marketplace add inite-ai/inite-brain-serviceThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add inite-ai/inite-brain-service --skill brain-conflictgit clone --depth 1 https://github.com/inite-ai/inite-brain-service.git /tmp/inite-brain-service
mkdir -p ~/.claude/skills
cp -r /tmp/inite-brain-service/plugins/inite-brain/skills/brain-conflict ~/.claude/skills/brain-conflictPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# brain-conflict Brain settles every `record_fact` in two steps, and neither one uses a score. At write time it applies only rules that need no judgement: the same value restated **corroborates**, a strictly later `validFrom` **supersedes** the earlier value of the slot, and a strictly earlier one is filed as **history**. Two different values of one slot at the same valid time are both kept, and **fact resolution** (a judge that names the relation) decides what they are. When the judge says the two cannot both be true, both stay alive in COMPETING status. This skill is how you handle those. ## What COMPETING means `status='competing'` marks a real disagreement: the same attribute of the same subject, at the same time, with two values that cannot both be true and nothing saying one replaced the other. It comes from fact resolution, not from a threshold: - At write time a value that holds from the same moment as another value of the slot is inserted `active` with `reason: 'for_resolution'`. - Fact resolution compares the new fact with similar facts on the entity and names each relation: `same` (a paraphrase: corroborates), `replaces` (successive values: valid time decides which closes), `contradicts` (both go `competing`), `unrelated` (nothing changes). - `single_active` predicates close every overlapping value at write time, so they never reach the judge by overlap. - `bitemporal_event` predicates decide by calendar day at write time, as before.
Details
- Skill name
brain-conflict- Repository
- inite-ai/inite-brain-service
- Path
plugins/inite-brain/skills/brain-conflict/SKILL.md- License
- AGPL-3.0
- Repo updated
- 18 November 2026
FAQ
What does the Brain Conflict skill do?
How to detect and resolve conflicting beliefs in the INITE Brain knowledge graph — the COMPETING fact status, get_competing_facts, detect_contradiction preflight, and the human-in-the-loop adjudication workflow. Use when the timeline shows two facts disagreeing on the same predicate, or when an agent needs to decide what to record without making the disagreement worse.
How do I install the Brain Conflict skill?
Claude Code plugin: /plugin marketplace add inite-ai/inite-brain-service. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Brain Conflict popular?
It lives in inite-ai/inite-brain-service, which has 43 GitHub stars and 5 forks.
Related skills
Brain Bitemporal
43inite-ai/inite-brain-service
How to query the INITE Brain knowledge graph across time — the asOf parameter, validFrom/validUntil semantics, reading retracted facts, and the memory_diff "what changed between two cursors" surface. Use when the user's question has a temporal dimension ("on X date", "before Y", "what's new since last conversation").
Brain MCP Setup
43inite-ai/inite-brain-service
Walk a developer through connecting a fresh MCP client (Claude Desktop, Cursor, Goose v2, Aider, Continue.dev, n8n, or a raw @modelcontextprotocol/sdk client) to the INITE Brain service. Covers obtaining an API key, the per-tenant URL shape, config snippets per client, the scope matrix for the full tool surface (up to 32 built-in tools + 2 resources), and the smoke test. Use when the user says "add brain MCP", "connect brain to Claude", "set up brain for Cursor", or names any MCP-capable client.
Brain Recall
43inite-ai/inite-brain-service
Recall everything brain knows about one specific entity — current profile, full bitemporal timeline, graph neighbours, and unresolved disagreements. Use when the user names a person/company/thing and asks "tell me about them", "what's their history", or "what do we still disagree about?". For a single-shot LLM briefing without three round-trips, reach for summarize_entity instead.
Breadcrumbs
62ElliotJLT/Claude-Skill-Potions
Leaves notes for future Claude sessions in .claude/breadcrumbs.md. At session end or after significant work, records what was tried, what worked, what failed, and context for next time. On session start, reads breadcrumbs to understand history. Session-to-session memory without manual updates.
Cn Morning Note
43ccq1/cn-financial-services-plugins
A 股早盘晨报,综述隔夜全球市场、当日重要事件、板块轮动预判和重点关注标的。当用户请求"晨报"、"早盘综述"、"今天关注什么"、"开盘前看什么"、"morning note"时触发。
Zero Sleep
44Jakeschincariol/unhinged-claude-skills
Holds the thread across a big multi-step build without losing the plot — long-haul endurance and context-keeping; invoke via /zero-sleep when a task spans many steps and hours and you need consistency from start to finish.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.