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

Trademark Coexistence

ASecurity

Drafts U.S. trademark coexistence agreements defining permitted use boundaries, differentiation requirements, and confusion-prevention protocols for parties with similar marks. Use when drafting coexistence or consent agreements, concurrent use arrangements, or resolving likelihood-of-confusion disputes without litigation.

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

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill trademark-coexistence --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Trademark Coexistence?

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

Security grade badge for Trademark Coexistence
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-trademark-coexistence/badge)](https://www.skillsdirectory.com/skills/lev-os-trademark-coexistence)

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

Download Zip
Files
SKILL.md
---
name: trademark-coexistence
description: Drafts U.S. trademark coexistence agreements defining permitted use boundaries, differentiation requirements, and confusion-prevention protocols for parties with similar marks. Use when drafting coexistence or consent agreements, concurrent use arrangements, or resolving likelihood-of-confusion disputes without litigation.
tags:
  - agreement
  - drafting
  - transactional
---

# Trademark Coexistence Agreement

Drafts a binding agreement defining permitted use boundaries for parties with similar marks, preventing consumer confusion while preserving both parties' trademark rights.

## Prerequisites

Collect before drafting:

1. **Mark details per party** — exact marks (word/design/composite), registration numbers, filing dates, first-use dates
2. **Goods/services** — Nice Classification or detailed descriptions per party
3. **Geographic scope** — current territories and planned expansion per party
4. **Priority** — which party holds senior rights (first use, first registration, or concurrent)
5. **Trade channels** — distribution methods, customer segments, marketing channels per party
6. **Prior disputes** — cease-and-desist letters, opposition proceedings, negotiations

## Quick Start

1. Gather prerequisites and confirm priority determination
2. Draft agreement following the section order below
3. Verify all `[VERIFY]` flags against current law
4. Attach exhibits (mark specimens, goods/services lists, territory maps, disclaimer language)

## Agreement Sections

### 1. Header & Parties

- Title: "Trademark Coexistence Agreement"
- Effective date, full legal names, entity type, jurisdiction, principal place of business
- Consistent designations throughout: "Senior User"/"Junior User" or "Party A"/"Party B"

### 2. Recitals

Draft in this order:

1. **Party A's mark** — mark, registration status, first-use date, goods/services, geographic scope, goodwill
2. **Party B's mark** — same detail; business rationale for adoption; how use differs
3. **Conflict assessment** — visual/phonetic/conceptual similarity; goods/services relatedness; trade channel overlap; likelihood-of-confusion factors under *Polaroid*/*Sleekcraft* `[VERIFY]`
4. **Mutual intent** — avoid confusion, prevent litigation, establish coexistence in good faith

### 3. Core Coexistence Terms

**Per-party permitted use:**
- Permitted goods/services (enumerate specifically)
- Geographic territories
- Trade channels (online, wholesale, retail categories)
- Non-challenge covenant (no opposition/cancellation/infringement claims within permitted scope)
- Expansion rights with conditions and notice requirements

**Differentiation requirements** (typically on junior user):
- Required house mark, logo, or co-branding element
- Prohibited design elements, color schemes, stylistic presentations
- Mandatory disclaimers or clarifying statements
- Packaging/labeling distinctions

### 4. Ongoing Obligations

**Quality control:**
- Each party maintains quality standards for marked goods/services
- No disparagement, dilution, or tarnishment
- Self-monitoring with corrective action

**Confusion prevention protocol:**

| Step | Action | Timeline |
|------|--------|----------|
| 1 | Notify other party of confusion incident | Prompt written notice |
| 2 | Good-faith consultation on remedies | 15 business days |
| 3 | Implement agreed remedies | 30 days |
| 4 | Verify compliance | Ongoing |

**Third-party enforcement:** Information sharing, coordinated enforcement where appropriate, neither party's enforcement undermines the other's rights.

### 5. Registration Rights

- Permitted jurisdictions and classes for future applications
- Mutual non-opposition covenant for compliant applications
- Consent letter procedures for overcoming PTO likelihood-of-confusion refusals
- Maintenance/renewal obligations (timely filings, declarations of use)
- Abandonment notice if either party discontinues use or abandons registration

### 6. Term & Termination

**Duration:** Perpetual or fixed term with renewal.

**Material breach triggers:** unauthorized expansion, failure to differentiate, actual marketplace confusion, quality violations.

**Cure framework:**

| Phase | Detail |
|-------|--------|
| Notice | Written, specifying breach with particularity |
| Cure period | 30–60 days (specify) |
| Uncured | Non-breaching party may terminate and pursue all remedies |

**Post-termination:** Termination does not invalidate underlying rights. Include wind-down period and handling of existing inventory/materials.

### 7. Reps, Warranties & Indemnification

**Mutual representations:** authority to bind, accuracy of ownership/usage info, no pending litigation affecting performance, no third-party infringement beyond the addressed conflict.

**Mutual indemnification for:** breach, third-party IP claims from indemnifying party's mark use, law violations. Include notice-of-claims, tender-of-defense, and defense/settlement control procedures.

### 8. General Provisions

| Provision | Notes |
|-----------|-------|
| Assignment | Prior written consent; address change-of-control |
| Amendment | Written, signed by authorized representatives |
| Governing law | Jurisdiction with developed TM law and party nexus |
| Dispute resolution | Mediation → arbitration/litigation; preserve injunctive relief |
| Notices | Certified mail / courier / email with confirmation |
| Entire agreement | Supersedes prior negotiations; severability |

### 9. Execution

- Signature blocks with name, title, date for both parties
- Counterpart execution permitted
- Electronic signatures per E-SIGN Act / UETA `[VERIFY]`

## Pitfalls & Checks

- Differentiation requirements must be specific, measurable, and enforceable — not aspirational
- Non-challenge covenants must be expressly limited to agreed parameters; preserve challenge rights for out-of-scope use
- Address both current use and future expansion — expansion ambiguity is the top coexistence dispute source
- Consent letter provisions must satisfy TMEP §1207.01(d)(viii) `[VERIFY]`
- If one party has clearly senior rights, reflect that asymmetry in restriction burden
- Include quality control sufficient to avoid naked-license / abandonment arguments
- Flag goods/services overlap where confusion risk remains high despite differentiation
- For international registrations, address Madrid Protocol and EU trademark system considerations

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

Responsive Design

Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies. Use when building adaptive interfaces, implementing fluid layouts, or creating component-level responsive behavior.

393432 votes

Mermaid Diagrams

Creating and refining Mermaid diagrams with live reload. Use when users want flowcharts, sequence diagrams, class diagrams, ER diagrams, state diagrams, or any other Mermaid visualization. Provides best practices for syntax, styling, and the iterative workflow using mermaid_preview and mermaid_save tools.

2032 votes

sleek-design-mobile-apps

Use when the user wants to design a mobile app, create screens, build UI, or interact with their Sleek projects. Covers high-level requests ("design an app that does X") and specific ones ("list my projects", "create a new project", "screenshot that screen").

5711 votes

swiftui-design-skill

SwiftUI frontend visual design skill. Creates beautiful, distinctive iOS/macOS interfaces that avoid generic AI slop patterns. Covers design direction, layout systems, typography, color, spacing, brand integration, and design review. Use when designing new SwiftUI views, reviewing UI quality, creating iOS prototypes, choosing visual styles, improving app aesthetics, or when the UI looks generic or AI-generated.

1801 votes

Ios Hig

Use when designing iOS interfaces, implementing accessibility (VoiceOver, Dynamic Type), handling dark mode, ensuring adequate touch targets, providing animation/haptic feedback, or requesting user permissions. Apple Human Interface Guidelines for iOS compliance.

761 votes
View all in design →