
epo-patent-analyzer
Automated analysis of patent applications for EPO compliance with Art. 84 EPC (claims clarity/support), Art. 83 EPC (sufficiency of disclosure), and Rules 42-49 EPC (formalities)
- Installs
- 49
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/robthepcguy/claude-patent-creator --skill epo-patent-analyzer- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads epo-patent-analyzer automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
EPO Patent Analyzer Skill
Automated analysis of patent applications for European Patent Office compliance under the European Patent Convention (EPC).
When to Use
Invoke this skill when users ask to:
- Review patent claims for EPO Art. 84 compliance
- Check sufficiency of disclosure under Art. 83 EPC
- Analyze EPO formalities under Rules 42-49 EPC
- Convert USPTO-style claims to EPO two-part form
- Prepare for EPO examination or respond to EPO communications
- Validate applications before EP filing or Euro-PCT entry
What This Skill Does
Performs comprehensive EPO-focused analysis:
-
Claims Analysis (Art. 84 EPC):
- Clarity: identifies unclear or ambiguous terms
- Conciseness: detects redundant or overlapping claims
- Support: verifies all claims are supported by description
- Two-part form (Rule 43(1) EPC): checks preamble + "characterised in that"
- Claim categories: product, process, apparatus, use
- Excluded subject matter: Art. 52(2) and Art. 53 EPC
-
Sufficiency of Disclosure (Art. 83 EPC):
- Reproducibility: can a person skilled in the art reproduce the invention?
- Breadth of claims vs disclosure: is the full scope enabled?
- Essential technical features: all present and described?
- Working examples: at least one concrete embodiment?
-
Formalities (Rules 42-49 EPC):
- Description format (Rule 42): required sections in correct order
- Claims form (Rule 43): two-part form, numbering, references
- Drawings (Rule 46): margins, no text, reference signs
- Abstract (Rule 47): max 150 words, figure designation
- Physical requirements: A4, margins, fonts
-
Issue Categorization:
- Critical: Will cause objection under EPC
- Important: May cause objection or limit scope
- Minor: Best practice per EPO Guidelines
Required Data
This skill uses the EPO compliance analyzers and the EPC/EPO Guidelines search:
MCP Tools Available:
review_epo_claims- Art. 84 EPC compliance checkingreview_epo_specification- Art. 83 EPC sufficiency analysischeck_epo_formalities- Rules 42-49 EPC formalitiessearch_patent_law- Search EPC, EPO Guidelines, PCT rules
How to Use
When this skill is invoked:
-
Determine analysis scope:
- Full application review (claims + description + formalities)
- Claims-only review (Art. 84 EPC)
- Sufficiency-only review (Art. 83 EPC)
- Formalities-only review (Rules 42-49 EPC)
-
Run appropriate analyzers:
- For claims: check clarity, conciseness, support, two-part form
- For sufficiency: check reproducibility, scope vs disclosure, examples
- For formalities: check all Rules 42-49 requirements
-
Present analysis:
- Show compliance score (0-100)
- List issues by severity (critical, important, minor)
- Provide EPC article/rule citations for each issue
- Reference EPO Guidelines sections
- Suggest specific fixes
Analysis Output Structure
{
"jurisdiction": "EPO",
"claim_count": 15,
"independent_count": 2,
"dependent_count": 13,
"compliance_score": 72,
"total_issues": 8,
"critical_issues": 2,
"important_issues": 4,
"minor_issues": 2,
"issues": [
{
"category": "clarity",
"severity": "critical",
"claim_number": 1,
"term": "substantially",
"description": "Term 'substantially' lacks objective definition under Art. 84 EPC",
"epc_cite": "Art. 84 EPC",
"guidelines_cite": "EPO Guidelines F-IV, 4.6",
"suggestion": "Replace with objective criterion or remove"
},
{
"category": "two_part_form",
"severity": "important",
"claim_number": 1,
"description": "Independent claim not in two-part form per Rule 43(1) EPC",
"epc_cite": "Rule 43(1) EPC",
"guidelines_cite": "EPO Guidelines F-IV, 3.2",
"suggestion": "Restructure: preamble + 'characterised in that' + novel features"
}
]
}
Common EPO Issues Detected
-
Clarity Issues (Art. 84 EPC):
- Relative terms without objective reference
- Inconsistent terminology between claims and description
- Functional features not clearly defined
- "Means for" language without clear structural support
-
Support Issues (Art. 84 EPC):
- Claims broader than description discloses
- Unsupported generalizations from specific examples
- Missing essential technical features
- Claim scope exceeding experimental evidence
-
Sufficiency Issues (Art. 83 EPC):
- Insufficient detail for reproduction
- Claims too broad relative to examples
- Missing critical parameters or conditions
- Undue burden on skilled person
-
Formality Issues (Rules 42-49 EPC):
- Missing required description sections
- Abstract exceeding 150 words
- Text in drawings
- Claims not in two-part form
Presentation Format
Present analysis as:
EPO COMPLIANCE ANALYSIS REPORT
================================
Jurisdiction: European Patent Office (EPC)
Analysis Date: [Date]
Summary:
- Total Claims: 15 (2 independent, 13 dependent)
- Compliance Score: 72/100
- Issues Found: 8 (2 critical, 4 important, 2 minor)
CLAIMS ANALYSIS (Art. 84 EPC):
Clarity:
[Claim 1] CRITICAL - "substantially uniform" lacks objective definition
Art. 84 EPC / EPO Guidelines F-IV, 4.6
Fix: Define with measurable criterion (e.g., "within 5% deviation")
Support:
[Claim 3] IMPORTANT - "any wireless protocol" exceeds disclosure
Art. 84 EPC / EPO Guidelines F-IV, 6.2
Fix: Limit to disclosed protocols (Bluetooth, Wi-Fi, NFC)
Two-Part Form:
[Claim 1] IMPORTANT - Not in two-part form
Rule 43(1) EPC / EPO Guidelines F-IV, 3.2
Fix: Identify closest prior art, split into known + novel features
SUFFICIENCY ANALYSIS (Art. 83 EPC):
[PASS] At least one embodiment fully described
[WARN] Claims 8-10 cover embodiment not exemplified
Art. 83 EPC / EPO Guidelines F-III, 3
Consider: Add working example for thermal processing variant
FORMALITIES (Rules 42-49 EPC):
[PASS] Description sections in correct order (Rule 42)
[FAIL] Abstract: 167 words (max 150) (Rule 47)
[PASS] Drawings: no text, proper margins (Rule 46)
[FAIL] No figure designated for abstract (Rule 47(2)(b))
Key EPO vs USPTO Differences
| Aspect | USPTO (35 USC) | EPO (EPC) |
|---|---|---|
| Claim clarity | Reasonable certainty (112(b)) | Strict objective clarity (Art. 84) |
| Claim form | Open format | Two-part form preferred (Rule 43) |
| Support | Written description (112(a)) | Supported by description (Art. 84) |
| Enablement | Enable POSITA (112(a)) | Sufficiency of disclosure (Art. 83) |
| Best mode | Required (112(a)) | Not required |
| Terms of degree | Allowed with spec support | Must have objective reference |
| Software | Patent-eligible if technical | Must show "further technical effect" |
| Medical methods | Allowed | Excluded (Art. 53(c)) |
| Novelty | 102 (1-year grace period) | Art. 54 (absolute novelty, no grace period) |
| Obviousness | 103 (obvious to POSITA) | Art. 56 (inventive step, problem-solution) |
Integration with EPC Search
For each issue, the skill can:
- Search EPC provisions and EPO Guidelines for relevant guidance
- Provide specific article, rule, and Guidelines section citations
- Show EPO Board of Appeal case law on similar issues
- Suggest fixes based on EPO prosecution practice
Tools Available
- Read: To load application from files
- Bash: To run EPO compliance analyzers
- Write: To save analysis reports
FAQ
What does the epo-patent-analyzer skill do?
Automated analysis of patent applications for EPO compliance with Art. 84 EPC (claims clarity/support), Art. 83 EPC (sufficiency of disclosure), and Rules 42-49 EPC (formalities)
How do I install epo-patent-analyzer?
Run npx skills add https://github.com/robthepcguy/claude-patent-creator --skill epo-patent-analyzer in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/epo-patent-analyzer/ (personal) or .claude/skills/epo-patent-analyzer/ (project).
Which AI agents can use epo-patent-analyzer?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is epo-patent-analyzer safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains epo-patent-analyzer?
It is published by robthepcguy in robthepcguy/claude-patent-creator. It has 49 recorded installs.
More from robthepcguy/claude-patent-creator
patent-application-creator
robthepcguy/claude-patent-creator
End-to-end patent campaign from ANY raw material ("here is some information; make a patent") to a filing-ready provisional package - invention mining, worth-it economics (design-around cost, detectability), exhaustive adversarial prior art, claims-first drafting, machine-verified compliance, hostile-examiner attack pass, and an honest no-go when nothing clears the bar or the fence is not worth the money
patent-claims-analyzer
robthepcguy/claude-patent-creator
Automated analysis of patent claims for USPTO compliance with 35 USC 112(b) requirements - antecedent basis, definiteness, claim structure
patent-diagram-generator
robthepcguy/claude-patent-creator
Create patent-style technical diagrams including flowcharts, block diagrams, and system architectures using Graphviz with reference numbering
prior-art-search
robthepcguy/claude-patent-creator
Systematic 7-step methodology for comprehensive patent prior art searches and patentability assessments using BigQuery and CPC classification
bigquery-patent-search
robthepcguy/claude-patent-creator
Fast, cloud-based patent searching across 100 million+ worldwide patents using Google BigQuery - keyword search, CPC classification, patent details retrieval
patent-reviewer
robthepcguy/claude-patent-creator
Expert system for reviewing utility patent applications against USPTO MPEP guidelines.
Popular media & creative skills
hyperframes
heygen-com/hyperframes
Read first to make, edit, animate or render any video with HyperFrames (HTML rendered to video), including launch films, explainers, music videos, charts, maps, vertical clips, title cards, captions and overlays. Holds the render contract, the work loop and what each kind of video needs.
media-use
heygen-com/hyperframes
Get or make any media for a HyperFrames video - music, sound effects, images, icons, logos, voiceover, avatar and generated video, transcripts, cutouts, colour grades and looks - with HeyGen or free local tools, and mix placed audio. Also for footage that looks dark, flat or dull, or should be stylized or hidden.
hyperframes-registry
heygen-com/hyperframes
About 450 ready-made HyperFrames blocks and components installed as editable source - transitions, overlays, titles, kinetic type, captions, charts, map overlays, 3D, camera moves. Use it before hand-building any named visual (CRT scanlines, glitch, film grain, a chart); also for hyperframes add and catalog.
hyperframes-creative
heygen-com/hyperframes
Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use hyperframes-animation.
ai-video-generation
101-skills/superpowers
Generate AI videos with Google Veo, Seedance 2.0, HappyHorse, Wan, Grok and 40+ models via inference.sh CLI. Models: Veo 3.1, Veo 3, Seedance 2.0, HappyHorse 1.0, Wan 2.5, Grok Imagine Video, OmniHuman, Fabric, HunyuanVideo. Capabilities: text-to-video, image-to-video, reference-to-video, video editing, lipsync, avatar animation, video upscaling, foley sound. Use for: social media videos, marketing content, explainer videos, product demos, AI avatars. Triggers: video generation, ai video, text to video, image to video, veo, animate image, video from image, ai animation, video generator, generate video, t2v, i2v, ai video maker, create video with ai, runway alternative, pika alternative, sora alternative, kling alternative, seedance, happyhorse
ai-image-generation
101-skills/superpowers
Generate AI images with GPT-Image-2, FLUX, Gemini, Grok, Seedream, Reve and 50+ models via inference.sh CLI. Models: GPT-Image-2, FLUX Dev LoRA, FLUX.2 Klein LoRA, Gemini 3 Pro Image, Grok Imagine, Seedream 4.5, Reve, ImagineArt. Capabilities: text-to-image, image-to-image, inpainting, LoRA, image editing, upscaling, text rendering. Use for: AI art, product mockups, concept art, social media graphics, marketing visuals, illustrations. Triggers: flux, image generation, ai image, text to image, stable diffusion, generate image, ai art, midjourney alternative, dall-e alternative, text2img, t2i, image generator, ai picture, create image with ai, generative ai, ai illustration, grok image, gemini image, gpt image, openai image, chatgpt image