field-of-use-restriction-clause
Drafts enforceable Field of Use restriction clauses for U.S. IP licensing agreements (patent, software, trade secret, know-how). Covers permitted and restricted applications, sublicense limits, derivative-use treatment, audit and compliance mechanics, and remedy framework. Use when narrowing licensee exploitation rights, setting enforcement triggers, or preserving licensor rights outside scope during negotiation or formation. Triggers: field of use, permitted use, restricted use, sublicensing, derivative works, audit rights, IP licence scope, patent software licensing.
Best use case
field-of-use-restriction-clause is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Drafts enforceable Field of Use restriction clauses for U.S. IP licensing agreements (patent, software, trade secret, know-how). Covers permitted and restricted applications, sublicense limits, derivative-use treatment, audit and compliance mechanics, and remedy framework. Use when narrowing licensee exploitation rights, setting enforcement triggers, or preserving licensor rights outside scope during negotiation or formation. Triggers: field of use, permitted use, restricted use, sublicensing, derivative works, audit rights, IP licence scope, patent software licensing.
Teams using field-of-use-restriction-clause should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/field-of-use-restriction-clause/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How field-of-use-restriction-clause Compares
| Feature / Agent | field-of-use-restriction-clause | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Drafts enforceable Field of Use restriction clauses for U.S. IP licensing agreements (patent, software, trade secret, know-how). Covers permitted and restricted applications, sublicense limits, derivative-use treatment, audit and compliance mechanics, and remedy framework. Use when narrowing licensee exploitation rights, setting enforcement triggers, or preserving licensor rights outside scope during negotiation or formation. Triggers: field of use, permitted use, restricted use, sublicensing, derivative works, audit rights, IP licence scope, patent software licensing.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Field of Use Restriction Clause Drafts a narrow, enforceable licensing clause that limits exploitation rights to a defined field while preserving licensor control outside that field. U.S.-focused; cross-border enforcement may require localization. [VERIFY] ## Prerequisites Before drafting, confirm: 1. **Grant model defined** — IP type, exclusive/non-exclusive, term, royalty logic, territory. 2. **Portfolio data collected** — patent IDs, software modules/versions, know-how, related IP. 3. **Business boundaries set** — industries, customer types, channels, geographies, prohibited markets. 4. **Source documents available** — draft agreement, SOW, schedules, prior licenses. 5. **Enforcement preferences** — audit cadence, reporting format, cure policy, remedy priorities. 6. **Jurisdiction selected** — governing law, venue/forum, injunctive relief requirements. ## Quick Start Gather inputs across five dimensions, then assemble clause sections in order: | Input | Capture | Drives | |---|---|---| | Field scope | Industry, use case, geography, customer type, channel | `Field of Use` definition and negative examples | | IP scope | Patent IDs, software versions, process assets | Covered subject-matter precision | | Commercial rights | Grant type, exclusivity, sublicensing | Reservation-of-rights language | | Compliance controls | Reporting cadence, records, audit access | Audit and reporting mechanics | | Enforcement posture | Cure tolerance, injunction needs, termination triggers | Remedies and transition provisions | ## Clause Assembly Draft sections in this order: 1. **Definitions** — `Licensed Property`, `Field of Use`, `Permitted Applications`, `Restricted Fields`, plus technology-specific terms from patents/specs. 2. **Grant** — Confer rights only within `Field of Use`; reserve all rights outside; tie term/milestones to any scope evolution. 3. **Sublicense/assignment** — Scope limits, mandatory field-of-use flow-down notices, licensor approval where required. 4. **Use controls** — Prohibit direct/indirect exploitation outside scope; explicit anti-circumvention for affiliates, contractors, distributors. 5. **Derivatives** — Restrict derivative use consistent with field intent; address improvements and new IP ownership. 6. **Compliance** — Licensee records by product/application/customer; periodic reports; audit rights with access scope and notice. 7. **Remedies** — Cure rules (if any), material breach termination, injunction, enhanced royalties/profits, IP clawback where lawful. 8. **Post-termination** — Immediate cessation, return/destruction of materials, ongoing confidentiality and field restrictions. 9. **Governing law and disputes** — Chosen forum plus carve-out for expedited injunctive relief. 10. **Survival** — Confidentiality, indemnity, continuing restraint obligations. ## Validation Checklist Before finalizing: - [ ] No operative verb (`sell`, `use`, `offer`, `distribute`, `import`) permits off-scope commercial activity - [ ] All cross-references resolve; terminology uniform across definitions and obligations - [ ] Reporting fields tie to royalty and audit triggers - [ ] Survival clause covers confidentiality, indemnity, and continuing restraints - [ ] Grant language and exclusion language are consistent (no contradictions) ## Pitfalls - **Ambiguous scope** — Prefer objective controls over subjective standards; ambiguity defeats enforcement. - **Software licenses** — Split field definitions by platform, module, deployment model, and customer class. - **Liquidated damages** — Use only if demonstrably tied to anticipated loss and proportionate. - **Anti-circumvention gaps** — Cover affiliates, contractors, distributors, and value-chain intermediaries explicitly.