conflict-of-interest-checker
Check for co-authorship and institutional conflicts between authors and suggested reviewers to support peer review integrity. Coauthorship and institutional conflict detection supported.
Install / Use
npx skills add aipoch/medical-research-skills --skill conflict-of-interest-checkerInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Customer SupportSupported Platforms
Our assessment of conflict-of-interest-checker
conflict-of-interest-checker scores 89/100 on our quality scale, 165th of 319 Customer Support skills we index.
Its SKILL.md is 5.5 KB long, well organised into 18 sections with 5 code examples: a solid amount of guidance for an agent.
With 1,916 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so conflict-of-interest-checker is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
conflict-of-interest-checker compared with similar skills
All 4 of these similar skills score higher than conflict-of-interest-checker; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| conflict-of-interest-checker (this skill)by aipoch | 89 | 1.9k | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
| crawl4aiby unclecode | 100 | 87.4k | 3d ago | MCP Server |
Frequently asked questions
- How do I install conflict-of-interest-checker?
- Run
npx skills add aipoch/medical-research-skills --skill conflict-of-interest-checker. The install tabs above show the steps for each supported agent. - Which AI agents does conflict-of-interest-checker work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is conflict-of-interest-checker safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is conflict-of-interest-checker still maintained?
- The repository was last updated about 2 months ago, so conflict-of-interest-checker is actively maintained.
Skill content
View source on GitHubname: conflict-of-interest-checker description: Check for co-authorship and institutional conflicts between authors and suggested reviewers to support peer review integrity. Coauthorship and institutional conflict detection supported. license: MIT author: AIPOCH
Conflict of Interest Checker
Reviewer conflict detection tool for journal submissions and editorial decisions.
Quick Check
python -m py_compile scripts/main.py
Audit-Ready Commands
python -m py_compile scripts/main.py
python scripts/main.py --help
python scripts/main.py --authors "Smith,Jones,Lee" --reviewers "Brown,Davis,Wilson"
When to Use
- Journal submission preparation
- Editorial conflict screening
- Peer review integrity verification
- Compliance verification for grant review panels
Workflow
- Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work.
- Validate that the request matches the documented scope and stop early if the task would require unsupported assumptions.
- Use the packaged script path or the documented reasoning path with only the inputs that are actually available.
- Return a structured result that separates assumptions, deliverables, risks, and unresolved items.
- If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion.
Parameters
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| --authors, -a | string | Yes | Comma-separated author names |
| --reviewers, -r | string | Yes | Comma-separated reviewer names |
| --publications, -p | string | No | CSV file with publication records |
CSV Format
author,reviewer,paper_id
Smith,Brown,paper1
Smith,Jones,paper2
Known limitations: (1)
check_collaboration_conflict()is a stub that always returns an empty list — only coauthorship conflicts (via shared paper IDs) are actively detected. (2)check_institutional_conflict()has a NameError bug at line 59 — use the Claude Direct Path below instead of calling this method directly.
Usage
# Check with demo data
python scripts/main.py --authors "Smith,Jones,Lee" --reviewers "Brown,Davis,Wilson"
# Check with publication records
python scripts/main.py --authors "Smith,Jones" --reviewers "Brown,Davis" --publications pubs.csv
Output
- Conflict flagging (coauthorship)
- Shared publication list
- Recommendation: Accept/Recuse
Example Output
⚠ Found 2 potential conflict(s):
1. COAUTHORSHIP CONFLICT
Reviewer: Brown
Author: Smith
Shared papers: paper1
2. COAUTHORSHIP CONFLICT
Reviewer: Wilson
Author: Smith
Shared papers: paper2
Institutional Conflict — Claude Direct Path
The script's check_institutional_conflict() method has a known NameError bug (the reviewer variable is not defined in the method scope at line 59). When institutional conflict checking is needed, use this Claude Direct path instead:
- Ask the user for: reviewer name, reviewer institution, and a list of author names with their institutions.
- Compare reviewer institution against each author institution (case-insensitive).
- Flag any reviewer-author pair sharing the same institution as an INSTITUTIONAL CONFLICT.
- Report in the same format as coauthorship conflicts, with
conflict_type: "institutional". - Note: "Institutional conflict detected via Claude Direct path — script method has a known bug and was bypassed."
Stress-Case Rules
For complex multi-constraint requests, always include these blocks:
- Assumptions
- Hard Constraints
- Conflict Detection Path
- Residual Risks
- Unresolved Items
Input Validation
This skill accepts requests involving co-authorship conflict detection between manuscript authors and proposed reviewers.
If the user's request does not involve conflict-of-interest checking for peer review — for example, asking to write a review, evaluate manuscript quality, or perform general author searches — do not proceed with the workflow. Instead respond:
"conflict-of-interest-checker is designed to detect co-authorship and institutional conflicts between authors and reviewers. Your request appears to be outside this scope. Please provide author and reviewer name lists, or use a more appropriate tool for your task."
Output Requirements
Every final response must include:
- Objective or requested deliverable
- Inputs used and assumptions introduced
- Workflow or decision path
- Core result, recommendation, or artifact
- Constraints, risks, caveats, or validation needs
- Unresolved items and next-step checks
Error Handling
- If
--authorsor--reviewersare missing, request them before proceeding. - If
--publicationsCSV is malformed or missing expected columns (author,paper_id), report the error and fall back to demo data with a warning. - If institutional conflict checking is requested, use the Claude Direct Path above — do not call
check_institutional_conflict()directly. - If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.
- If
scripts/main.pyfails, report the failure point, summarize what still can be completed safely, and provide a manual fallback. - Do not fabricate files, citations, data, search results, or execution outcomes.
Response Template
- Objective
- Inputs Received
- Assumptions
- Workflow
- Deliverable
- Risks and Limits
- Next Checks
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
crawl4ai
87.4kOfficial Crawl4AI Cloud: a hosted web scraping, extraction, and search API for AI agents. Free API key, 1,000 credits a month, no card. Fully open source: this repo is the Apache-2.0 crawler that powers it, and you can self-host it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
