Closes gaps in damages methodology critique with corrected calculation, foreclosure percentage computation, statute of limitations date analysis, and market concentration correction.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill identify-antitrust-issues-in-counterparty-complaint --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Identify Antitrust Issues In Counterparty Complaint?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-identify-antitrust-issues-in-counterparty-complain)More formats (shields.io, HTML) on the badges page.
---
name: identify-antitrust-issues-in-counterparty-complaint
task_id: antitrust-competition/identify-antitrust-issues-in-counterparty-complaint
description: Closes gaps in damages methodology critique with corrected calculation, foreclosure percentage computation, statute of limitations date analysis, and market concentration correction.
activates_for: [planner, solver, checker]
---
# Skill: Defense-Side Antitrust Complaint Issue Memorandum
## 2. Failure modes the skill is correcting
- Treating the complaint at face value instead of testing each claim for pleading sufficiency, doctrinal fit, and likely defense leverage
- Stopping at description of flaws without tying each issue to the governing antitrust rule, the source-record facts, and the litigation consequence
- Failing to separate counts or theories that require different standards, markets, timing rules, or effect analyses
- Missing that antitrust complaints often mix horizontal, vertical, exclusionary, and monopolization theories that must be evaluated under different authorities
- Offering conclusory viability judgments without identifying the specific pleading defect, the corrective legal framework, and the practical defense response
- Ignoring timing defenses, including accrual, limitations cutoffs, and whether alleged conduct is an ongoing violation or a time-barred completed act
- Overlooking market-definition problems that distort power, concentration, foreclosure, and effects analysis
- Accepting plaintiff damages, share, or concentration assertions without independently checking the source data and the denominator they used
## 3. Legal frameworks / domain conventions that apply
- Sherman Act § 1: require an agreement, concerted action, and an anticompetitive restraint; distinguish per se theories from rule-of-reason analysis under cases such as *Leegin Creative Leather Products, Inc. v. PSKS, Inc.* and *Continental T.V., Inc. v. GTE Sylvania Inc.*
- Sherman Act § 2: evaluate monopoly power, willful acquisition or maintenance, exclusionary conduct, and causation under authorities such as *United States v. Grinnell Corp.* and *Aspen Skiing Co. v. Aspen Highlands Skiing Corp.*
- Clayton Act § 3 / rule-of-reason exclusive dealing analysis: assess whether the challenged arrangement forecloses a substantial share of the relevant market, using the correct market denominator and duration
- Private antitrust damages: distinguish liability from damages; test whether the pleaded injury is plausible, properly measured, and attributable to the challenged conduct under *Brunswick Corp. v. Pueblo Bowl-O-Mat, Inc.* and related proximate-cause principles
- Statute of limitations: apply the controlling federal limitations period for private antitrust claims, identify the filing cutoff, and analyze accrual and continuing-violation doctrine using the governing complaint filing date and last overt act principles
- Market definition: challenge overnarrow product or geographic markets; apply practical-indicia and interchangeability concepts; recalculate concentration only after the market is properly defined
- Pleading standards: use *Bell Atlantic Corp. v. Twombly* and *Ashcroft v. Iqbal* to assess whether the complaint plausibly alleges agreement, power, exclusionary effect, and causation rather than labels and conclusions
- Vertical restraints and resale pricing: analyze under the applicable rule-of-reason framework and test whether cited documents actually show an anticompetitive object, mechanism, or effect
## 4. Analytical scaffolds
1. Start by enumerating every claim or count, then analyze each count on its own legal standard; do not merge distinct theories into one pass
2. For each count, identify the authority, the required elements, the facts the complaint pleads, the missing facts, and the defense angle most likely to defeat or narrow the claim
3. For each issue, close the analysis with three moves: tie it to a figure, threshold, date, or market boundary in the record; cross-reference the source document that interacts with it; and state the downstream effect on exposure, leverage, or motion practice
4. If the complaint relies on economics, perform an independent check of the plaintiff’s denominator, market boundary, timing base, or injury theory before stating the corrected conclusion
5. If the complaint alleges foreclosure, compute the share foreclosed from the pleaded data, state the relevant market assumption, and explain why the result does or does not approach substantial foreclosure under rule-of-reason precedent
6. If the complaint alleges price restraint or vertical control, identify the actual restraint alleged, the applicable standard, and whether the cited internal material supports an anticompetitive inference or merely ordinary commercial monitoring
7. For limitations issues, compute the cutoff date from the filing date, then classify each alleged act as before-cutoff, after-cutoff, or potentially continuing; analyze whether there is a plausible overt-act bridge
8. For damages issues, separate liability from quantification, identify the plaintiff’s methodology error, and state the corrected exposure narrative using the proper inputs and denominator
9. For market-definition issues, test whether the proposed market is arbitrary or overnarrow, then recalculate concentration or power using the broader, better-supported market if warranted
10. Assign an ordinal severity level to every issue and use it consistently across the memo; explain the rating in one line with litigation consequence
11. End each issue with a concrete defense recommendation that names who should act and what should happen next
## 5. Vertical / structural / temporal relationships (only if applicable)
- Map each allegation to the relevant layer of the conduct: agreement formation, market definition, competitive effects, injury, damages, and timing
- Distinguish upstream contracting, midstream restraint, and downstream market effect when the complaint blurs those stages
- Track whether the alleged conduct is discrete, repeated, or ongoing; limitations analysis depends on that structure
- If multiple products, territories, customer classes, or periods are implicated, state the full set first and then evaluate each separately
- Where the complaint compares periods, ensure the baseline period, challenged period, and post-conduct period are not mixed in a way that inflates injury or concentration
- If the alleged restraint operates through contracts or relationship chains, identify which document or relationship actually carries the alleged anticompetitive effect
## 6. Output structure conventions
- Use an issue register organized by count, theory, or claim cluster, not a free-form narrative
- Begin with a short severity key using an ordinal scale such as Critical / High / Medium / Low
- For each entry, use the same subheadings in substance: controlling authority, pleading sufficiency, record-based analysis, quantitative or temporal check if relevant, severity, and defense recommendation
- When a claim involves multiple acts, markets, or time periods, list them explicitly before the analysis and then evaluate them one by one
- Include a standalone statute-of-limitations section with the filing cutoff date and a per-conduct assessment
- Include a standalone market-definition / concentration section when the complaint turns on power, foreclosure, or concentration
- Include a standalone damages section only if the complaint or documents provide a quantifiable theory; otherwise say the record does not support a reliable damages model yet
- End with a Recommended Actions block that gives concrete next steps in imperative form, identifies the responsible role, and ties each step to the litigation timeline
- Keep the tone defense-side, issue-oriented, and motion-practice ready; avoid academic exposition and avoid repeating the complaint’s rhetoric
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!