# Analyze Counterparty Markup Ip Assignment

> Risk-prioritized redline analysis of a counterparty-marked IP assignment agreement against the original draft and internal acquisition playbook, focusing on how to compare the markup against baseline drafting conventions and transaction objectives.

- Skill: `finchipaiorg/analyze-counterparty-markup-ip-assignment` (Agent Skill)
- Install (CLI): `npx skillmds@latest add finchipaiorg/analyze-counterparty-markup-ip-assignment`
- Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/analyze-counterparty-markup-ip-assignment/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/finchipaiorg/analyze-counterparty-markup-ip-assignment

---


# Skill: Analyze Counterparty Markup of IP Assignment Agreement

## 1. Subject-matter triage

- Treat the task as a comparison-and-advice exercise: identify deviations from the original draft and the playbook, assess legal and transactional impact, and present a negotiated position.
- First determine whether there is a single agreement or multiple versions, schedules, exhibits, or ancillary documents in scope; if more than one, separate the analysis by document and by provision before drawing conclusions.
- Distinguish true legal risk from drafting preference, and distinguish negotiated business terms from pure cleanup.
- If the markup is incomplete or the baseline draft is missing, state that as a threshold issue before attempting issue analysis.

## 2. Failure modes the skill is correcting

- Analyzing IP indemnification caps in isolation rather than connecting them to the overall transaction economics and the playbook's minimum acceptable floor.
- Evaluating license-back provisions for their stated field of use without assessing whether the field is broad enough to allow the assignor to compete commercially using the assigned IP.
- Treating non-compete restrictions as boilerplate without mapping duration, geographic scope, covered activities, and affiliate coverage against playbook requirements.
- Missing chain-of-title gaps arising from contractor IP, prior employer assignments, or university research agreements disclosed in diligence materials.
- Summarizing the markup without tying each point to the specific provision changed, the operative consequence, and the recommended response.
- Letting stylistic redlines obscure substantive legal changes when the output is later exported or pasted into another format.

## 3. Legal frameworks / domain conventions that apply

- IP assignment agreements transfer all right, title, and interest in patents, copyrights, trade secrets, and know-how; the scope of the assignment clause controls what is actually conveyed.
- Representations and warranties on ownership, non-infringement, and freedom to assign are the primary contractual risk-allocation mechanism; gaps or qualifications in these reps shift risk to the buyer.
- IP indemnification: market convention ties the indemnification cap to transaction economics; below-market caps are a high-priority negotiating item.
- License-back provisions: an overly broad field of use or unrestricted sublicensing right can functionally recreate competition using the assigned portfolio.
- Non-compete and non-solicitation: enforceability depends on applicable law; many jurisdictions limit or restrict non-competes, while others apply a reasonableness test examining duration, scope, and geographic reach.
- Contractor and employee IP: work-for-hire doctrine does not automatically cover independent contractors; written invention and confidentiality assignments are often required for clean title.
- Change-of-control provisions: assignment restrictions or consent requirements that survive closing can impair the buyer's ability to integrate the acquired IP.
- As to legal propositions, tie conclusions to the controlling doctrine, statute, rule, or market convention that supports the point; do not state a risk without naming the governing authority or conventional baseline.

## 4. Analytical scaffolds

- Start with a provision-by-provision comparison against the original draft, then test each change against the playbook and transaction objective.
- For each issue, identify:
  - the clause or section affected;
  - the counterparty change and how it departs from the baseline;
  - the severity level using a single ordinal scale defined once at the top of the memo;
  - the legal or commercial reason the deviation matters;
  - the recommended counter-position or fallback.
- In each issue discussion, close the loop by tying the point to:
  - the scale of the affected asset base, obligation, restriction, or exposure using the source documents;
  - any other clause, schedule, exhibit, or diligence item that interacts with it;
  - the downstream consequence for ownership certainty, use rights, enforcement, closing risk, integration, or value.
- When multiple IP categories, contributors, or restrictions are implicated, analyze each category separately rather than collapsing them into one generic paragraph.
- Use the playbook as the primary benchmark for acceptable drafting, but identify when the markup creates a broader business or legal risk even if it does not expressly violate the playbook.
- For any proposed compromise, specify whether it is an acceptable fallback, a conditional concession, or a non-starter.

## 5. Vertical / structural / temporal relationships

- Map the chain of title vertically from invention creation to assignment to delivery to post-closing use rights; identify where any link is missing or conditional.
- Track horizontal interactions among assignment, license-back, indemnity, restrictive covenant, confidentiality, and termination provisions.
- Separate pre-closing diligence fixes from post-closing operational restrictions.
- If a provision survives closing or is triggered by later restructuring, flag the temporal effect and whether it impairs future financing, sale, or integration.
- Where the markup changes a definition, ensure downstream defined terms and cross-references remain coherent across the agreement and any attached schedules.

## 6. Output structure conventions

- Use a risk dashboard at the outset with a clear ordinal severity scale defined once and then applied consistently.
- Organize the body as numbered issues, one issue per substantive deviation, with each entry including:
  - provision reference;
  - what changed from the original draft;
  - severity;
  - why it matters under the governing legal or market framework;
  - the interaction with other source documents or provisions;
  - the consequence to the client;
  - the recommended counter-position or fallback language approach.
- If there are multiple provisions affecting the same risk theme, keep them in separate entries but cross-reference them.
- Include a concise section for pre-closing action items where diligence gaps or missing chain-of-title documents must be cured.
- End with an explicit Recommended Actions block that assigns the action, the responsible role, and the timing anchor tied to the transaction milestone.
- For markup output, make every substantive change legible in plain text as well as by styling: use explicit textual change markers so the reader can identify the edit even if formatting is lost.
- Where helpful, include short [Rationale: ...] annotations adjacent to redline suggestions so the basis for the recommendation is clear.