conflict-detector
Skill10 starsChanged 6 days agoMITView on GitHub
Cross-checks two or more documents, datasets or extracted fact tables for contradictions and reports each conflict with a severity. Numbers are compared with hard cross-checks, not fuzzy inference.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- JiamingShi-JsPhys/agent-skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- JiamingShi-JsPhys/agent-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/chelate-shell.mdcCursor rule
- 3d-modelerSkill
- ai-trace-removerSkill
- bibtex-normalizerSkill
- capstone-labmateSkill
- data-profilerSkill
- document-evolution-trackerSkill
- formula-validatorSkill
- fulltext-extractorSkill
- latex-exporterSkill
- literature-retrieverSkill
- longitudinal-analysisSkill
- ml-auditorSkill
- multi-dim-managerSkill
- quantitative-validatorSkill
- reference-auditorSkill
- sci-visualizerSkill
- security-guardSkill
- task-organizerSkill
- video-trackerSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Run this exact form — do not read the source tree:
- Distinctive: line 44
Only one document is involved — there is nothing to cross-check.
- Distinctive: line 69
No conflicts found is a success with an empty report.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
conflict-detector
Finds claims that disagree across sources and grades them by level: entity (numeric/boolean), clause (categorical), argument (free text). It reports conflicts; it does not decide which source is right.
- Stage:
gates· Sandbox: no · Dependencies: stdlib only (PyYAMLonly for.yamlconfigs)
Quick Execution
Run this exact form — do not read the source tree:
python run.py --root <WS> --action run -- --config config/examples/two_docs.yamlvalidatefirst: it is fast and writes no report.--format json,csv,mdselects the output formats (default: json).- The gate lands in
<WS>/process/gates/conflict-detector_<ts>.json.
When to use
- Two or more sources must be checked against each other.
- A single claim appears in several places and their agreement matters.
- An extracted fact table must be audited for internal contradictions.
When NOT to use
- Only one document is involved — there is nothing to cross-check.
- You need a correctness judgement rather than a consistency report.
Actions
--action | Does | Extra arguments |
validate | Check the config, no report written | --config <cfg> |
list-docs | List the sources a config resolves to | --config <cfg> |
run | Detect conflicts | --config <cfg> [--format json,csv,md] |
Hard constraints
- Never invent a conflict. An empty report is a valid result.
- Report severity as computed, never re-graded by hand.
Outputs
<WS>/process/gates/conflict-detector_<ts>.json— the gate result.- The conflict report in the requested formats under
process/.
Failure handling
- An invalid config exits non-zero and names the field.
- An unreachable source aborts the run naming that source.
- No conflicts found is a success with an empty report.
Limitations
- Extraction is key-value oriented; free-text paragraphs only participate at the argument level.
- Unit normalisation is table-driven (
unit_map); custom units must be declared.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.