# Conflict check summary

> Assemble the entity and relationship picture a conflict decision needs.

- Skill: `vstorm-co/conflict-check-summary` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vstorm-co/conflict-check-summary`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vstorm-co/conflict-check-summary/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: vstorm-co (https://skillmd.com/u/vstorm-co)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vstorm-co/conflict-check-summary

---


# Summarising a conflict check

This gathers facts. Whether a conflict exists, and whether it can be managed, is
a decision for the person who owns it.

## Search on every variant

Registered names, trading names, former names, abbreviations, common
misspellings and transliterations. Individuals: married and maiden names,
initials, and the entities they direct.

## Report

Every match, with the matter it appeared in, the date, which side the firm
acted for, and whether the matter is open or closed · the relationship between
the matched entity and the new one — group company, counterparty, or the same
name coincidentally · anybody at the firm who has acted against the proposed
client.

## Say what the search did not cover

Databases not searched, date ranges not held, entities that could not be
resolved. A conflict check whose limits are not stated will be relied on beyond
them.

## Never

Clear a matter, dismiss a match as coincidence, or narrow the search because the
first pass returned too many results.

