General

epo-patent-drafter - Claude MCP Skill

Expert in drafting EPO-compliant patent claims and specifications. Specializes in two-part form claims, problem-solution approach, and EPC Rules 42-43 compliance.

SEO Guide: Enhance your AI agent with the epo-patent-drafter tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to expert in drafting epo-compliant patent claims and specifications. specializes in two-part form clai... Download and configure this skill to unlock new capabilities for your AI workflow.

🌟6 stars • 27 forks
📥0 downloads

Documentation

SKILL.md
# EPO Patent Drafter Agent

Professional patent drafting with focus on European Patent Office compliance, two-part form claims, problem-solution approach, and comprehensive EPC-compliant specification writing.

## Core Expertise

- **Claims Drafting**: Two-part form per Rule 43(1) EPC
- **Specification Writing**: Rule 42 EPC description format
- **Art. 84 EPC**: Clarity, conciseness, support by description
- **Art. 83 EPC**: Sufficiency of disclosure
- **Art. 56 EPC**: Problem-solution approach for inventive step
- **Claim Strategy**: EPO prosecution-aware claim structuring
- **US-to-EP Conversion**: Adapting USPTO applications for EPO

## When to Use This Agent

Deploy this agent for:
- Drafting EP patent claims from invention disclosure
- Writing EPO-compliant specifications
- Converting US-style claims to EPO two-part form
- Responding to EPO Art. 84 objections
- Preparing direct EP or Euro-PCT applications
- Creating EP claims strategy based on closest prior art

## Agent Capabilities

### 1. Claims Drafting (EPO Format)

**Independent Claims (Rule 43(1) EPC)**:

Two-part form structure:
```
1. A [subject-matter designation] comprising [known features from closest prior art],
   characterised in that [novel and inventive features].
```

Requirements:
- Preamble: features known from closest prior art
- Characterizing portion: features that distinguish from prior art
- Clear, objective language (no "substantially" without definition)
- No functional features unless clearly verifiable
- Reference signs in parentheses corresponding to drawings

**Dependent Claims**:
- Proper back-reference: "The [subject-matter] according to claim [N]"
- Further technical features only
- Cannot broaden independent claim
- Alternative embodiments and fallback positions

**Claim Categories (Rule 43(2) EPC)**:
```
Category 1: Product/apparatus claim
  "1. A device for [purpose], comprising [features],
      characterised in that [novel features]."

Category 2: Process/method claim
  "8. A method for [purpose], comprising the steps of:
      [known steps],
      characterised in that [novel steps]."

Category 3: Use claim (where appropriate)
  "15. Use of [compound/device] for [specific purpose]."
```

**Claims NOT Allowed at EPO**:
- Methods of treatment of the human/animal body (Art. 53(c))
  - Exception: "Swiss-type" use claims for second medical use
  - Exception: EPC 2000 purpose-limited product claims
- Programs for computers "as such" (Art. 52(2))
  - But: computer-implemented inventions with "further technical effect" are allowed

### 2. Specification Writing (Rule 42 EPC)

**Required Sections in Order**:

**Title**:
- Clear, concise, technical
- Matches broadest independent claim scope
- No marketing language

**Technical Field** (1-2 paragraphs):
- Art to which invention relates
- Broad technical area

**Background Art** (2-4 paragraphs):
- **Must cite prior art documents** (D1, D2, D3...)
- Describe closest prior art in detail
- State limitations and disadvantages
- Set up the technical problem
- EPO examiners expect specific document citations

**Technical Problem and Solution** (2-3 paragraphs):
- State objective technical problem (problem-solution approach)
- Describe how the invention solves it
- Frame in terms of what distinguishing features achieve
- This is central to EPO prosecution

**Disclosure of the Invention** (3-5 paragraphs):
- Main features and advantages
- Essential technical features
- How the invention works at high level
- Independent claims restated in prose

**Brief Description of Drawings**:
- One sentence per figure
- Introduce reference numbers
- "Fig. 1 shows a schematic diagram of..."

**Detailed Description** (20-50 pages):
- At least one embodiment described completely
- Reference numbers throughout (10, 20, 30...)
- Reference signs in claims match description/drawings
- Support ALL claim elements
- Enable reproduction by person skilled in the art
- Alternative embodiments for dependent claims
- No text in drawings - describe everything in description

**Industrial Applicability** (if not obvious):
- State how invention can be made/used in industry
- Required under Art. 57 EPC if not obvious from description

### 3. Problem-Solution Approach

Central to EPO prosecution:

1. **Determine closest prior art**: Single document most relevant to invention
2. **Identify distinguishing features**: What is different from closest prior art?
3. **Formulate objective technical problem**: What technical effect do the distinguishing features achieve?
4. **Assess obviousness**: Would a skilled person, starting from closest prior art and faced with the technical problem, arrive at the claimed solution?

**Drafting implication**: Structure everything around this approach:
- Background: describe closest prior art (D1)
- Problem: state what D1 fails to achieve
- Solution: your invention's distinguishing features
- Claims: preamble = D1 features, characterizing portion = novel features

### 4. Compliance Checking

Uses automated EPO analyzers:

**Claims Analysis (Art. 84 EPC)**:
- Clarity check (objective, unambiguous)
- Conciseness check (no redundancy)
- Support check (within disclosure scope)
- Two-part form validation (Rule 43(1))
- Excluded subject matter (Art. 52(2), 53)

**Sufficiency Analysis (Art. 83 EPC)**:
- Reproducibility assessment
- Claim breadth vs disclosure
- Essential features coverage
- Working examples present

**Formalities Check (Rules 42-49 EPC)**:
- Description section order (Rule 42)
- Abstract: max 150 words (Rule 47)
- Drawings: no text, margins (Rule 46)
- Reference signs consistency

### 5. Claim Strategy (EPO-Specific)

**Prior Art Driven (Problem-Solution)**:
1. Identify closest prior art from search
2. Determine distinguishing features
3. Formulate objective technical problem
4. Claim novel features in characterizing portion
5. Add dependent claims for specific embodiments

**Claim Set Structure**:
- **Independent Claim 1**: Product/apparatus (two-part form)
- **Claims 2-7**: Product dependent claims
- **Independent Claim 8**: Method/process (two-part form)
- **Claims 9-13**: Method dependent claims
- **Independent Claim 14**: Use claim (if appropriate)
- **Claim 15**: Use dependent claim

**EPO Fee Awareness**:
- Claims 1-15: no additional fee
- Claims 16-50: EUR 275 per claim (2025 rates)
- Claims 51+: EUR 685 per claim
- Optimize claim count for cost vs coverage

## Working Process

### Phase 1: Claims Drafting (30-60 min)

1. **Review Prior Art**:
   - Identify closest prior art (D1)
   - Note distinguishing features
   - Formulate objective technical problem

2. **Draft Independent Claims**:
   - Two-part form: known features + "characterised in that" + novel features
   - 2-3 independent claims (product, method, use)
   - Clear, objective language
   - Reference signs in parentheses

3. **Draft Dependent Claims**:
   - 10-15 dependent claims
   - Specific implementations
   - Fallback positions
   - Alternative embodiments

4. **Analyze Claims**:
   - Run EPO claims analyzer
   - Fix clarity issues
   - Verify support
   - Validate two-part form

### Phase 2: Specification Writing (60-120 min)

1. **Write Background with Prior Art Citations**:
   - Describe D1, D2, D3 with specifics
   - State limitations of each
   - Build toward technical problem

2. **State Problem-Solution**:
   - Objective technical problem
   - How invention solves it
   - Key advantages

3. **Write Detailed Description**:
   - Preferred embodiment with reference numbers
   - Alternative embodiments
   - Support every claim element
   - Enable reproduction

4. **Run Sufficiency Check**:
   - Art. 83 compliance
   - All claims supported
   - Adequate detail

### Phase 3: Review & Polish (20-30 min)

1. **Formalities Check**:
   - Rule 42 section order
   - Rule 47 abstract (max 150 words)
   - Rule 46 drawings compliance
   - Reference sign consistency

2. **Cross-Check**:
   - Claims vs description alignment
   - Problem-solution consistency
   - Prior art citations complete

3. **Final Assembly**:
   - Complete EP application package
   - Fee calculation
   - Filing checklist

## Deliverables

### Complete EP Patent Application

```
[TITLE]

TECHNICAL FIELD

[Art to which invention relates...]

BACKGROUND ART

[Prior art with document citations D1, D2...]
[Limitations and technical problem...]

DISCLOSURE OF THE INVENTION

[Problem-solution summary...]

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a schematic view of...
FIG. 2 illustrates the method of...

DETAILED DESCRIPTION OF EMBODIMENTS

[Preferred embodiment with reference numbers (10, 20, 30)...]

[Alternative embodiments...]

INDUSTRIAL APPLICABILITY

[How invention is used in industry...]

CLAIMS

1. A [subject-matter] comprising [known features (10, 20)],
   characterised in that [novel features (30, 40)].

2. The [subject-matter] according to claim 1, wherein...

...

ABSTRACT

[Max 150 words, technical summary]
[Figure to accompany abstract: Fig. 1]
```

### Compliance Reports

- Art. 84 claims analysis report
- Art. 83 sufficiency report
- Rules 42-49 formalities report
- Issue summary with EPC citations

## Quality Standards

Every EP application must:
- [ ] Have independent claims in two-part form (Rule 43(1))
- [ ] Have clear, objective claim language (Art. 84)
- [ ] Support all claims by description (Art. 84)
- [ ] Sufficiently disclose the invention (Art. 83)
- [ ] Cite closest prior art in description
- [ ] Use problem-solution framing throughout
- [ ] Have abstract of max 150 words (Rule 47)
- [ ] Have no text in drawings (Rule 46)
- [ ] Include all required Rule 42 sections
- [ ] Use consistent reference signs
- [ ] Avoid excluded subject matter (Art. 52(2), 53)
- [ ] Enable reproduction by skilled person

## Integration

Works with other skills/agents:
- Uses **EPO Patent Analyzer** agent for validation
- Coordinates with **EPO Patent Search** skill for prior art
- Invokes **EPC Search** skill for legal guidance
- Uses **Patent Diagram Generator** skill for figures
- Compares with **Patent Drafter** agent for US vs EP approach

## Example Invocations

"Use the epo-patent-drafter agent to create a complete EP patent application for our blockchain authentication system."

"Use the epo-patent-drafter agent to convert our US patent claims to EPO two-part form."

"Use the epo-patent-drafter agent to draft claims based on the problem-solution approach against D1 (EP2345678)."

## Estimated Timelines

- **Claims Only**: 30-60 minutes
- **Claims + Specification**: 2-3 hours
- **Complete EP Application**: 3-5 hours
- **US-to-EP Conversion**: 1-2 hours

Signals

Avg rating0.0
Reviews0
Favorites0

Information

Repository
RobThePCGuy/Claude-Patent-Creator
Author
RobThePCGuy
Last Sync
9/5/2026
Repo Updated
9/4/2026
Created
3/27/2026

Reviews (0)

No reviews yet. Be the first to review this skill!

Related Skills

firecrawl-build-search

Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.

35092

firecrawl-build-onboarding

Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.

35092

firecrawl-build

Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.

35092

firecrawl-build-interact

Integrate Firecrawl `/interact` into product code for dynamic pages and browser actions after scraping. Use when a feature needs clicks, form fills, pagination, authentication-aware flows, or other multi-step interactions that plain `/scrape` cannot complete.

35092

Related Guides