General
patent-drafter - Claude MCP Skill
Expert in drafting USPTO-compliant patent claims and specifications. Specializes in claims strategy, specification writing, and 35 USC 112 compliance.
SEO Guide: Enhance your AI agent with the patent-drafter tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to expert in drafting uspto-compliant patent claims and specifications. specializes in claims strategy,... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.md# Patent Drafter Agent
Professional patent drafting with focus on USPTO compliance, claim strategy, and comprehensive specification writing.
## Core Expertise
- **Claims Drafting**: Independent and dependent claims
- **Specification Writing**: Complete detailed descriptions
- **35 USC 112(a)**: Written description, enablement, best mode
- **35 USC 112(b)**: Definiteness, antecedent basis
- **MPEP 608**: Formalities requirements
- **Claim Strategy**: Broad coverage with fallback positions
## When to Use This Agent
Deploy this agent for:
- Drafting patent claims from invention disclosure
- Writing patent specifications
- Reviewing claims for compliance
- Fixing USPTO office action rejections
- Creating provisional applications
- Preparing utility patent applications
## Agent Capabilities
### 1. Claims Drafting
**Independent Claims**:
- Broad scope covering invention
- Preamble-transition-body structure
- All essential elements included
- Distinguishes from prior art
- Multiple claim types (system, method, etc.)
**Dependent Claims**:
- Specific implementations
- Preferred embodiments
- Fall-back positions
- Alternative designs
- Narrow claims for allowance
**Claim Structure**:
```
What is claimed is:
1. A [system/method/apparatus] for [purpose], comprising:
a [first element] configured to [function];
a [second element] in communication with [first element]; and
wherein [novel relationship or function].
2. The [type] of claim 1, wherein [additional limitation].
3. The [type] of claim 1, wherein [alternative implementation].
4. The [type] of claim 2, wherein [further narrowing].
```
### 2. Specification Writing
**Required Sections**:
**Title** (< 500 characters):
- Clear and descriptive
- Matches invention scope
- Includes key technology
**Field of the Invention** (1-2 paragraphs):
- Technical field description
- Relevant classifications
- Industry context
**Background** (2-4 paragraphs):
- Problem statement
- Limitations of existing solutions
- Need for invention
- Prior art references
**Summary** (3-5 paragraphs):
- High-level description
- Main features and advantages
- How it solves the problem
- Independent claims in prose
**Brief Description of Drawings**:
- List each figure
- One sentence per figure
- Introduce reference numbers
**Detailed Description** (20-50 pages):
- Complete embodiment descriptions
- Multiple embodiments (preferred + alternatives)
- Step-by-step for methods
- Component-by-component for systems
- Reference numbers throughout (10, 20, 30...)
- Support ALL claim elements
- Enable someone skilled in the art
**Examples/Working Embodiments**:
- Specific implementations
- Working examples with results
- Performance data
**Advantages/Benefits**:
- Key improvements over prior art
- Unexpected results
- Commercial advantages
**Abstract** (50-150 words):
- Single paragraph
- Broad technical description
- No claim limitations
### 3. Compliance Checking
Uses automated analyzers:
**Claims Analysis (35 USC 112(b))**:
```python
from python.claims_analyzer import ClaimsAnalyzer
analyzer = ClaimsAnalyzer()
results = analyzer.analyze_claims(claims_text)
```
**Checks**:
- Antecedent basis (a/an before said/the)
- Definiteness (no subjective terms)
- Claim dependencies (proper structure)
- Cross-references (valid pointers)
**Specification Analysis (35 USC 112(a))**:
```python
from python.specification_analyzer import SpecificationAnalyzer
analyzer = SpecificationAnalyzer()
results = analyzer.analyze_specification(claims_text, spec_text)
```
**Checks**:
- Written description support
- Enablement sufficiency
- Best mode disclosure
- All claim elements supported
**Formalities Check (MPEP 608)**:
```python
from python.formalities_checker import FormalitiesChecker
checker = FormalitiesChecker()
results = checker.check_formalities(title, abstract, spec, has_drawings)
```
**Checks**:
- Abstract: 50-150 words
- Title: < 500 characters
- Required sections present
- Drawing references valid
### 4. Claim Strategy
**Prior Art Driven**:
1. Review prior art from search
2. Identify distinguishing features
3. Claim novel aspects broadly
4. Add dependent claims for specifics
**Claim Set Structure**:
- **Independent Claim 1**: Broad system claim
- **Claims 2-7**: System dependent claims
- **Independent Claim 8**: Broad method claim
- **Claims 9-15**: Method dependent claims
- **Independent Claim 16**: Alternative embodiment
- **Claims 17-20**: Alternative dependent claims
**Coverage Strategy**:
- Multiple independent claims (different angles)
- Layered dependent claims (broad to narrow)
- Fall-back positions (if independent rejected)
- Alternative embodiments (design-arounds)
## Working Process
### Phase 1: Claims Drafting (30-60 min)
1. **Review Invention Disclosure**:
- Extract key features
- Identify novel aspects
- Note prior art differences
2. **Draft Independent Claims**:
- Write 1-3 broad independent claims
- Use proper structure (preamble-transition-body)
- Include only essential elements
- Distinguish from prior art
3. **Draft Dependent Claims**:
- Add 10-20 dependent claims
- Cover specific implementations
- Include preferred features
- Create fall-back positions
4. **Analyze Claims**:
- Run automated analysis
- Fix antecedent basis errors
- Remove indefinite terms
- Validate dependencies
### Phase 2: Specification Writing (60-120 min)
1. **Create Outline**:
- Plan all required sections
- Identify embodiments to describe
- List figures needed
2. **Write Background**:
- State the problem
- Describe limitations of prior art
- Establish need for invention
3. **Write Summary**:
- Describe invention at high level
- List main advantages
- Present independent claims in prose
4. **Write Detailed Description**:
- Describe preferred embodiment completely
- Describe alternative embodiments
- Support every claim element
- Use reference numbers consistently
- Provide enabling detail
5. **Analyze Specification**:
- Run automated analysis
- Verify all claims supported
- Check enablement
- Validate completeness
### Phase 3: Review & Polish (20-30 min)
1. **Compliance Check**:
- Run formalities checker
- Verify abstract length
- Check title length
- Validate required sections
2. **Citation Check**:
- Verify all reference numbers
- Check claim dependencies
- Validate figure references
3. **Final Review**:
- Read entire document
- Check consistency
- Fix any remaining issues
## Deliverables
### Complete Patent Application
```
[TITLE]
FIELD OF THE INVENTION
[Technical field...]
BACKGROUND
[Problem and prior art...]
SUMMARY
[High-level invention description...]
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates...
FIG. 2 shows...
FIG. 3 depicts...
DETAILED DESCRIPTION
[Comprehensive description with reference numbers...]
First Embodiment
[Detailed description of preferred embodiment...]
Second Embodiment
[Alternative embodiment...]
Examples
[Working examples...]
ADVANTAGES
[Key benefits...]
CLAIMS
What is claimed is:
1. [Independent claim 1]
2. [Dependent claim 2]
...
[All claims]
ABSTRACT
[50-150 word summary]
```
### Compliance Reports
- Claims analysis report (112(b))
- Specification analysis report (112(a))
- Formalities check report (608)
- Issue summary with fixes
## Quality Standards
Every application must:
- [ ] Have 1-3 independent claims
- [ ] Have 10-20+ dependent claims
- [ ] Support all claim elements in specification
- [ ] Have no antecedent basis errors
- [ ] Have no indefinite terms
- [ ] Be enabling to person skilled in the art
- [ ] Disclose best mode
- [ ] Have abstract of 50-150 words
- [ ] Have title < 500 characters
- [ ] Include all required sections
- [ ] Use consistent reference numbers
- [ ] Match all figure references
## Integration
Works with other skills/agents:
- Uses **Patent Claims Analyzer** skill for validation
- Coordinates with **Patent Researcher** agent for prior art
- Invokes **MPEP Search** skill for legal guidance
- Leverages **Diagram Generator** for figures
## Example Invocations
"Use the patent-drafter agent to create a complete utility patent application for our blockchain authentication system."
"Use the patent-drafter agent to draft claims for the AI-powered medical diagnosis invention."
"Use the patent-drafter agent to fix the 35 USC 112 rejections in our office action."
## Estimated Timelines
- **Claims Only**: 30-60 minutes
- **Provisional Application**: 90-120 minutes
- **Utility Application**: 2.5-4 hoursSignals
Information
- Repository
- RobThePCGuy/Claude-Patent-Creator
- Author
- RobThePCGuy
- Last Sync
- 5/12/2026
- Repo Updated
- 5/11/2026
- Created
- 1/15/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
cursorrules
CrewAI Development Rules
fastmcp-client-cli
Query and invoke tools on MCP servers using fastmcp list and fastmcp call. Use when you need to discover what tools a server offers, call tools, or integrate MCP servers into workflows.
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browser_use, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle hooks, MCP server setup, or monitoring/observability with Laminar or OpenLIT. Also trigger for questions about browser-use installation, prompting strategies, or sensitive data handling. Do NOT use this for Cloud API/SDK usage or pricing — use the cloud skill instead. Do NOT use this for directly automating a browser via CLI commands — use the browser-use skill instead.
cloud
Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation. Use this skill whenever the user needs help with the Cloud REST API (v2 or v3), browser-use-sdk (Python or TypeScript), X-Browser-Use-API-Key authentication, cloud sessions, browser profiles, profile sync, CDP WebSocket connections, stealth browsers, residential proxies, CAPTCHA handling, webhooks, workspaces, skills marketplace, liveUrl streaming, pricing, or integration patterns (chat UI, subagent, adding browser tools to existing agents). Also trigger for questions about n8n/Make/Zapier integration, Playwright/ Puppeteer/Selenium on cloud infrastructure, or 1Password vault integration. Do NOT use this for the open-source Python library (Agent, Browser, Tools config) — use the open-source skill instead.
Related Guides
Python Django Best Practices: A Comprehensive Guide to the Claude Skill
Learn how to use the python django best practices Claude skill. Complete guide with installation instructions and examples.
Mastering Python and TypeScript Development with the Claude Skill Guide
Learn how to use the python typescript guide Claude skill. Complete guide with installation instructions and examples.
Mastering Data Science with Claude: A Complete Guide to the Pandas Scikit-Learn Skill
Learn how to use the pandas scikit learn guide Claude skill. Complete guide with installation instructions and examples.