epc-search
RAG search across EPC provisions, EPO Guidelines for Examination, and PCT rules for European and international patent law research
What this skill does
# EPC/PCT Legal Search Skill
Hybrid RAG search across the European Patent Convention (EPC), EPO Guidelines for Examination, and PCT Rules for patent law research.
## When to Use
Invoke this skill when users ask to:
- Find EPC articles or rules on a specific topic
- Search EPO Guidelines for Examination
- Look up PCT rules or Administrative Instructions
- Compare EPC requirements with USPTO/MPEP practice
- Research EPO Board of Appeal case law principles
- Understand European patent prosecution procedure
- Find legal basis for EPO examination objections
## What This Skill Does
Provides legal research across European and international patent law:
1. **EPC Search** (European Patent Convention):
- Articles 1-178 EPC
- Rules 1-167 EPC (Implementing Regulations)
- Protocol on Interpretation of Art. 69 EPC
- Protocol on Centralisation
- Protocol on Privileges and Immunities
2. **EPO Guidelines Search** (Guidelines for Examination):
- Part A: Guidelines for Formalities Examination
- Part B: Guidelines for Search
- Part C: Guidelines for Procedural Aspects of Substantive Examination
- Part D: Guidelines for Opposition and Limitation/Revocation
- Part E: Guidelines for General Procedural Matters
- Part F: Guidelines for Substantive Examination (The Patent Application)
- Part G: Guidelines for Patentability
- Part H: Guidelines for Amendments and Corrections
3. **PCT Rules Search** (Patent Cooperation Treaty):
- PCT Articles 1-69
- PCT Rules 1-96 (Regulations under the PCT)
- Administrative Instructions under the PCT
- WIPO Standards (ST.25, ST.26, ST.36)
4. **Cross-Jurisdiction Comparison**:
- EPC vs 35 USC mapping
- EPO Guidelines vs MPEP equivalents
- PCT requirements vs national requirements
## Required Data
**MCP Tools Available**:
- `search_patent_law` - Search EPC, EPO Guidelines, PCT rules with jurisdiction parameter
- `search_mpep` - Search MPEP/35 USC/37 CFR for comparison
## How to Use
When this skill is invoked:
1. **Determine jurisdiction**:
- EPO: search EPC articles/rules and EPO Guidelines
- PCT: search PCT articles/rules and Administrative Instructions
- Both: search across all sources
- Comparison: search EPO + USPTO sources
2. **Execute search**:
**EPC/EPO Guidelines search**:
```python
results = search_patent_law(
query="claim clarity requirements",
jurisdiction="EPO",
top_k=5
)
```
**PCT rules search**:
```python
results = search_patent_law(
query="unity of invention",
jurisdiction="PCT",
top_k=5
)
```
**Cross-jurisdiction comparison**:
```python
epo_results = search_patent_law(query="sufficiency of disclosure", jurisdiction="EPO")
us_results = search_mpep(query="enablement requirement")
```
3. **Present results**:
- Show relevant provisions with full text
- Provide article/rule numbers and section references
- Include EPO Guidelines commentary
- Note practical implications for prosecution
## Key EPC Provisions Reference
### Patentability
| Article | Topic | Description |
|---------|-------|-------------|
| Art. 52 | Patentable inventions | What can be patented |
| Art. 52(2) | Exclusions | Discoveries, theories, programs "as such" |
| Art. 53 | Exceptions | Morality, plant/animal varieties, medical methods |
| Art. 54 | Novelty | Absolute novelty, no grace period |
| Art. 55 | Non-prejudicial disclosures | 6-month grace for abuse or exhibitions |
| Art. 56 | Inventive step | Problem-solution approach |
| Art. 57 | Industrial applicability | Capable of industrial application |
### The Patent Application
| Article/Rule | Topic | Description |
|-------------|-------|-------------|
| Art. 78 | Requirements | What an EP application must contain |
| Art. 83 | Disclosure | Sufficiency of disclosure |
| Art. 84 | Claims | Clarity, conciseness, support |
| Rule 42 | Description | Content and form of description |
| Rule 43 | Claims | Two-part form, numbering, categories |
| Rule 46 | Drawings | Form and content requirements |
| Rule 47 | Abstract | Max 150 words, figure designation |
### Examination Procedure
| Article | Topic | Description |
|---------|-------|-------------|
| Art. 90 | Formalities examination | Initial formality check |
| Art. 92 | European search | Search report |
| Art. 94 | Substantive examination | Examination on request |
| Art. 97 | Grant/refusal | Decision on application |
| Art. 99 | Opposition | 9-month opposition period |
## Key PCT Rules Reference
### Application Requirements
| Rule | Topic | Description |
|------|-------|-------------|
| Rule 4 | The request | Form PCT/RO/101 contents |
| Rule 5 | The description | Required sections and order |
| Rule 6 | The claims | Numbering, form, categories |
| Rule 8 | The abstract | Max 150 words, figure |
| Rule 11 | Physical requirements | Paper, margins, fonts |
| Rule 12 | Language | Accepted languages |
### Unity and Search
| Rule | Topic | Description |
|------|-------|-------------|
| Rule 13 | Unity of invention | Single general inventive concept |
| Rule 33 | Relevant prior art | ISA search scope |
| Rule 39 | Subject matter not searched | Excluded from ISA search |
| Rule 43bis | International search report | Written opinion of ISA |
### National Phase
| Rule | Topic | Description |
|------|-------|-------------|
| Rule 49 | Physical requirements | National phase format |
| Rule 49.6 | Translation | Language requirements |
| Rule 51bis | Certain national requirements | National law compliance |
## EPO Guidelines Structure
```
Part A: Formalities Examination
├── Chapter I: Checking the application on filing
├── Chapter II: Filing and examination for formalities
├── Chapter III: Special cases (divisionals, PCT)
└── Chapter IV: Designation of inventor
Part F: The Patent Application
├── Chapter I: Description
├── Chapter II: Claims (MOST COMMONLY SEARCHED)
│ ├── F-IV, 2: Independent claims
│ ├── F-IV, 3: Two-part form
│ ├── F-IV, 4: Clarity
│ ├── F-IV, 6: Support by description
│ └── F-IV, 7: Dependent claims
├── Chapter III: Sufficiency of disclosure
├── Chapter V: Abstract
└── Chapter VI: Drawings
Part G: Patentability
├── Chapter I: Excluded subject matter
├── Chapter II: Non-technical subject matter
├── Chapter III: Novelty
├── Chapter V: Non-prejudicial disclosures
├── Chapter VI: Inventive step (problem-solution)
└── Chapter VII: Inventive step (combinability)
```
## Presentation Format
Present search results as:
```
EPC/EPO LEGAL RESEARCH RESULTS
=================================
Query: "claim clarity requirements"
Jurisdiction: EPO (EPC + Guidelines)
[1] Art. 84 EPC - The Claims
"The claims shall define the matter for which protection
is sought. They shall be clear, concise and be supported
by the description."
EPO Guidelines F-IV, 4 - Clarity
"Each claim should be read giving the words the meaning
and scope which they normally have in the relevant art..."
Key Points:
- Claims must be clear on their own (not by reference to spec)
- Technical terms given their normal meaning in the art
- Relative terms need objective reference point
- Functional features must be verifiable
[2] Rule 43(1) EPC - Form and content of claims
"...shall contain: (a) a statement indicating the designation
of the subject-matter and those technical features necessary
for the definition... (preamble); and (b) a characterising
portion preceded by 'characterised in that'..."
EPO Guidelines F-IV, 3.2 - Two-part form
"Independent claims should normally be in the two-part form..."
---
Related MPEP Comparison:
- MPEP 2173: Claims Must Particularly Point Out and Distinctly Claim
- 35 USC 112(b): Equivalent US clarity requirement
- Key difference: EPO applies stricter objective clarity standard
```
## Cross-Jurisdiction Mapping
| EPO (EPC) | USPTO (35 USC) | PCT |
|-----------|----------------|-----|
| ARelated in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.