IP Assignment Agreement
IP ownership is the most expensive dispute in freelance and contractor work — and the default legal position in most jurisdictions is that the creator owns it, even if someone else paid for it, unless there's a written assignment. The IP Assignment Agreement drafts the clean, present-tense, payment-tied transfer that actually holds up.
What this skill does
IP ownership is the single most litigated issue in freelance, agency, and contractor relationships. The default legal position varies wildly — in the UK, copyright in commissioned work belongs to the creator unless there's a written, signed assignment. In the US, "work for hire" only applies to employees and nine specific statutory categories; for everything else, you need an explicit assignment. A missing or vague IP clause routinely means a business doesn't actually own its own website, logo, codebase, or content, and discovers it years later when the cost to fix is ten to a hundred times the cost of getting it right upfront.
The skill starts by mapping the IP landscape. What's being created (software, design, written content, audio/video, brand elements, inventions)? What already exists that the creator is bringing in (pre-existing tools, libraries, templates, methodologies, open-source components, third-party assets)? What's in between (work-in-progress if the project ends early, derivative works, AI-generated content where copyrightability is unclear in some jurisdictions)? Each category gets handled explicitly rather than assumed.
Then it picks an assignment structure. Full assignment, assignment with licence-back, licence only (creator retains ownership, client gets defined usage rights), work-for-hire where it legally applies, or chain assignment for agency models where subcontractor creates work that flows to the end client and both links have to be solid.
The draft uses present-tense assignment language — "Creator hereby assigns" — because "agrees to assign" creates only a promise, not an assignment, and that distinction has cost companies real money in court. Assignment is tied to full payment, which is the creator's only meaningful bargaining position. Pre-existing IP is listed specifically, not gestured at — "Creator's pre-existing IP" with no schedule is a dispute waiting to happen. Moral rights are waived where legally permitted (they often can't be fully waived in EU jurisdictions, and the draft addresses that reality rather than pretending). Portfolio rights are stated explicitly so both parties don't end up with different assumptions.
The output includes the IP Landscape Map, the full agreement, Risk Flags (pre-existing IP contamination, jurisdiction gaps, moral rights issues, open-source licence implications, AI tooling), and Action Items beyond signing — copyright registration, licence record updates, evidence preservation. Retrospective assignments for work already completed get a heightened warning because they require fresh consideration in many jurisdictions to be enforceable.
This produces a drafted agreement, not legal advice. IP law varies sharply between jurisdictions — what works under UK CDPA may not work under US copyright law or EU moral-rights regimes — and the cost of an unenforceable assignment is usually the value of the underlying IP itself. Have a qualified IP lawyer review the draft before signing. The skill is a starting point for professional review, not a substitute for one.
When this triggers
- ·You're hiring a contractor and need to make sure you actually own the work
- ·You're a freelancer and the client's contract has a vague 'all IP belongs to client' clause
- ·You bring pre-existing tools, code libraries, or templates into client work and need them carved out
- ·Work was done a year ago without an IP clause and you need a retrospective assignment
- ·You're running an agency model where subcontractors create work for end clients and both links need to be solid
Example
Trigger
User: 'Hiring a contractor to build a custom dashboard. Want full IP ownership but they're saying they reuse a charting library they wrote. Also they use Copilot. How do I handle this?'
Output
IP Landscape Map | Type | Created by | Owner under default law | Resolution | |---|---|---|---| | Custom dashboard code | Contractor | Contractor (UK default) | Full assignment on final payment | | Pre-existing charting library | Contractor | Contractor | Listed in carve-out; perpetual non-exclusive licence to you | | AI-assisted code segments | Contractor + AI | Unclear in many jurisdictions | Disclosure required; warranty that ToS was complied with | | Open-source dependencies | Third parties | Licence terms govern | Identified in schedule; licence compliance is contractor's responsibility | The Agreement (9 sections): 1. Definitions (Work Product, Pre-Existing IP, Third-Party Materials) 2. Assignment — "Contractor hereby assigns…" (present tense, not "agrees to assign"), worldwide, perpetual, effective on full payment 3. Pre-Existing IP carve-out — charting library listed, perpetual royalty-free licence granted to you for use in the dashboard 4. Third-Party Materials — schedule of open-source libraries with licences 5. Moral rights waived to extent permitted by UK law 6. Further assurance + power of attorney 7. Warranties (originality, non-infringement, AI ToS compliance) 8. Portfolio rights — contractor may show post-launch, anonymised if requested 9. Remedies and indemnification Risk Flags: AI-generated portions may not be copyrightable in some jurisdictions; the library carve-out means you do NOT own that code, only a licence to use it — confirm that's acceptable.
Get this skill + 6 more
Included in the The Freelancer Stack — win clients, deliver work, get paid. Save $100+ vs buying individually.
Get The Freelancer Stack — $99What you get
- 145-line SKILL.md, ready to drop into ~/.claude/skills/
- Tested through 3 Karpathy-loop iterations (versions v1.0.0 → v1.3.0)
- Triggers automatically when relevant — no command to remember
- Lifetime updates as the skill is refined further
More from Legal & Compliance
Produces letters that are firm enough to be taken seriously, specific enough to be legally meaningful, and professional enough that they don't escalate the situation unnecessarily
Produces the actual words to say or write — not generic advice like "stay calm and be professional. Takes the specific conflict, identify the underlying interests, and draft a communication strategy…
Takes a loose description of a working relationship — who's involved, what's being delivered, how payment works — and produce a structured, enforceable contract that protects both parties
Doesn't produce a generic 50-point checklist — it assesses what a specific business does with data, identify the gaps, prioritise them by risk, and give concrete steps to close each gap
Doesn't produce a generic wall of text — it produces a policy that accurately describes what THIS business does with data, which laws apply, and what rights users have
Produces T&Cs that protect the business from real risks — not a generic template that covers everything and protects nothing
Browse the full library
297 skills across 31 categories. One purchase, lifetime updates.
See all bundles