information-sharing-clean-team-review

Solid

Use when actual or potential competitors propose to exchange competitively sensitive data — M&A diligence requests, JV data flows, benchmarking submissions, a negotiation asking for cost or capacity data — to produce a draft information-item matrix with per-item sensitivity flags, clean-team design notes, and spillover/carryover flags for attorney review, without authorizing any exchange or concluding lawfulness.

Code & Development 15 stars 3 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
40
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Information Sharing Clean Team Review ## Purpose Review a proposed exchange of competitively sensitive information between actual or potential competitors — in M&A diligence, a JV, benchmarking, a trade association, or a supply negotiation — item by item. Each information item is inventoried with its granularity, age, frequency, recipients, and purpose; flagged high/medium/low sensitivity with a descriptive rationale; and tested against the clean-team design, control gaps, and carryover/spillover risks. The output is a **draft for attorney review**: the skill never authorizes any exchange and never concludes an exchange is lawful. ## Use When - An M&A counterparty's diligence request list asks for current pricing, customer-level, or capacity data and the deal team wants to know what can go into the data room. - A clean-team agreement is being set up — or is already operating — and its membership, NDA scope, segregation, and carryover restrictions need testing. - A proposed JV or collaboration includes data-sharing annexes that would put competitor data into the parties' hands. - A benchmarking exercise, industry survey, or shared vendor/consultant would pool competitively sensitive inputs from competing companies. - A supplier-customer negotiation between parties who also compete drifts into requests for cost, capacity, or wage data. - Counsel asks which proposed data items are high-sensitivity and what controls the exchange currently lacks. ## Required Inputs - **Jur...

Details

Author
zgbrenner
Repository
zgbrenner/agentcounsel
Created
2 months ago
Last Updated
4 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

competitor-collaboration-review

Use when a proposed JV, co-development, co-marketing, joint purchasing, joint bidding, benchmarking, or standard-setting arrangement between actual or potential competitors needs antitrust screening, to produce a draft hardcore-restraint flag list, information-flow matrix, ancillarity questions, and per-jurisdiction safe-harbor questions for attorney review, without applying a safe harbor or approving the collaboration.

15 Updated 4 days ago
zgbrenner
AI & Automation Solid

gun-jumping-clean-team-checklist

Use when merger parties between signing and closing are planning integration, sharing information, or proposing joint conduct — aligning pricing, joint customer calls, a co-branded announcement before the waiting period ends — to produce a draft covenant inventory, conduct-vs-covenant deviation log, information-sharing log, and integration guardrail list for attorney review, without approving any pre-closing conduct or concluding HSR/Article 7 compliance.

15 Updated 4 days ago
zgbrenner
AI & Automation Solid

antitrust-risk-intake

Use when facts with possible competition-law exposure first arrive — a sales email about a competitor contact, a proposed collaboration, a pricing move, a hotline report, or an agency inquiry — to produce a draft conduct inventory and triage matrix that buckets each item, flags any time-critical track, and routes each item to the matched antitrust deep-dive skill for attorney review, without classifying conduct or assessing legality.

15 Updated 4 days ago
zgbrenner