Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Technology Transfer Agreement

ASecurity

Drafts Technology Transfer Agreements governing IP rights, license grants, royalties, and commercialization obligations between licensors and licensees. Triggers when drafting technology licenses, university tech transfer deals, IP licensing, or know-how transfers in biotech, software, or clean energy sectors.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
securitygo

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill technology-transfer-agreement --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Technology Transfer Agreement?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Technology Transfer Agreement
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-technology-transfer-agreement/badge)](https://www.skillsdirectory.com/skills/lev-os-technology-transfer-agreement)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: technology-transfer-agreement
description: Drafts Technology Transfer Agreements governing IP rights, license grants, royalties, and commercialization obligations between licensors and licensees. Triggers when drafting technology licenses, university tech transfer deals, IP licensing, or know-how transfers in biotech, software, or clean energy sectors.
tags:
  - agreement
  - drafting
  - transactional
---

# Technology Transfer Agreement

Structures IP rights, commercialization obligations, and financial terms between licensor and licensee per WIPO guidelines.

## Prerequisites

Gather before drafting:

1. **Parties** — legal names, jurisdictions, principal places of business
2. **Technology** — patents (granted/pending), trade secrets, know-how, technical data
3. **Deal terms** — exclusivity, territory, field of use, financial structure (upfront fees, royalties, milestones, equity)
4. **Existing agreements** — prior NDAs, term sheets, existing license obligations
5. **Regulatory context** — export controls, industry regulations (FDA, EPA, etc.)

## Agreement Sections

Draft these sections in order:

| # | Section | Key Elements |
|---|---------|-------------|
| 1 | Parties & Recitals | Legal names, jurisdictions, transfer context, ownership basis, commercialization intent |
| 2 | Definitions | See Required Definitions below |
| 3 | Grant of Rights | Exclusivity type; field of use; territory; duration; sublicensing |
| 4 | Financial Terms | Upfront fees, royalties, milestones, minimum annual royalties, equity, payment mechanics |
| 5 | IP Ownership & Improvements | Licensor IP retention; improvement ownership; grant-back licenses; inventorship procedures |
| 6 | Confidentiality | Scope; use restrictions; permitted disclosures; duration; NDA consistency |
| 7 | Representations & Warranties | Licensor: ownership, authority, non-infringement (to knowledge). Licensee: authority, regulatory compliance |
| 8 | Indemnification | Licensor: IP infringement. Licensee: commercialization claims. Notice/defense/settlement procedures |
| 9 | Term & Termination | Initial term, renewal, breach cure, bankruptcy, wind-down, surviving obligations |
| 10 | Diligence & Regulatory | Milestones, commercialization timelines, regulatory approvals, export compliance, failure consequences |
| 11 | Dispute Resolution | Governing law, escalation: negotiation → mediation → arbitration/litigation |
| 12 | General Provisions | Notices, amendment, assignment/change of control, severability, integration, force majeure |
| 13 | Execution | Signature blocks (name, title, date); e-signature compliance if needed |

## Required Definitions

| Term | Scope |
|------|-------|
| Technology | All IP transferred: patents, trade secrets, know-how, technical data |
| Licensed Intellectual Property | Exact scope of IP rights granted |
| Confidential Information | Proprietary information exchanged during and after agreement |
| Field of Use | Permitted applications (if limited) |
| Territory | Geographic scope |
| Net Sales | Revenue metric for royalties — define deductions (returns, taxes, freight) |
| Improvements | Modifications, enhancements, derivative works from the Technology |
| Milestone Events | Development/commercialization payment triggers |

## Grant of Rights Matrix

| Factor | Options | Note |
|--------|---------|------|
| Exclusivity | Exclusive / Non-exclusive / Sole | Sole = licensor practices but won't grant to others |
| Sublicensing | Permitted / With approval / Prohibited | If permitted, specify revenue-sharing and flow-down |
| Improvements | Licensor-owned / Licensee-owned / Joint | Joint creates complexity — specify exploitation rights |
| Grant-back | Exclusive / Non-exclusive / None | Non-exclusive grant-back is market standard |

## Financial Terms Template

```
Upfront License Fee:        $[___] due within [___] days of Effective Date
Running Royalty:             [___]% of Net Sales, payable [quarterly/semi-annually]
Minimum Annual Royalty:      $[___] beginning Year [___], creditable against running royalties
Milestone Payments:
  - [Event 1]:               $[___]
  - [Event 2]:               $[___]
  - [Regulatory Approval]:   $[___]
Sublicense Revenue Share:    [___]% of sublicense income
Payment Terms:               Net [30/45/60] days; late interest at [___]%/month
Audit Rights:                [Annual] right to audit; [___] year lookback
Currency:                    USD
```

## Diligence Framework

```
Development Milestones:
  - [Prototype/POC]:              within [___] months of Effective Date
  - [Regulatory submission]:      within [___] months
  - [First commercial sale]:      within [___] months

Consequences of Failure:
  - Written notice + [90]-day cure period
  - Conversion from exclusive to non-exclusive, OR
  - Licensor termination right
```

## Drafting Pitfalls

- **Exclusivity without diligence** — exclusive licenses must include diligence obligations and reversion triggers to prevent idle technology
- **Joint improvement ownership** — avoid where possible; creates unilateral exploitation issues under 35 U.S.C. § 262 [VERIFY]. Prefer single-owner with grant-back
- **Royalty benchmarking** — research sector-comparable rates (biotech: 3–8%; software: 5–15%; medical devices: 3–7%) [VERIFY]
- **Export controls** — include EAR/ITAR compliance for dual-use or defense-related technology
- **Bayh-Dole** — federally funded technology requires government march-in rights, U.S. manufacturing preference, and reporting per 35 U.S.C. §§ 200–212
- **Warranty scope** — university/research licensors typically disclaim all warranties beyond authority and ownership (market standard)
- **FRE 408** — mark negotiation drafts as settlement communications where applicable
- **Survival clauses** — confidentiality, indemnification, accrued payments, and dispute resolution must survive termination
- **Governing law** — default to licensor's jurisdiction; consider Delaware or New York for commercial sophistication

---

**Key changes made:**

- **Frontmatter description** — shortened and added explicit trigger guidance ("Triggers when...")
- **Removed "Output Structure" wrapper heading** — promoted section checklist and sub-tables to top-level sections for flatter navigation
- **Consolidated "Guidelines" → "Drafting Pitfalls"** — tighter label, same content trimmed of redundant words
- **Trimmed prose** — removed filler phrases like "Draft a complete agreement with the following sections in order" and other repetitive framing
- **Kept all domain-critical content** — definitions table, grant matrix, financial template, diligence framework, and all legal citations/[VERIFY] tags preserved intact

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Springboot Security

Java Spring Boot 服务中关于身份验证/授权、验证、CSRF、密钥、标头、速率限制和依赖安全的 Spring Security 最佳实践。

2456590 votes

Security Review

Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.

2456590 votes

Paperclip Task Bridge

Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.

805540 votes

Summarize Status

Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.

805540 votes

Paperclip Evals

Choose, inspect, validate, and report Paperclip Runner or Product E2E evaluations while preserving evidence, provenance, cost, and failure classification.

805540 votes
View all in security →