patent-reviewer
Expert system for reviewing utility patent applications against USPTO MPEP guidelines.
What this skill does
# Patent Creator Skill
Comprehensive patent creation system with USPTO MPEP, prior art databases, and USPTO API for complete patent application analysis.
## When to Use
Review patent applications for USPTO compliance, analyze claims/specifications/formalities, integrate prior art, get USPTO guidance, assist with patent drafting.
## Quick Review Commands
```bash
/full-review # Complete parallel review
/review-claims # 35 USC 112b compliance
/review-specification # 35 USC 112a compliance
/review-formalities # MPEP 608 compliance
/create-patent # New patent application
```
## Available MCP Tools
### MPEP & Regulations
- `search_mpep` - Search MPEP, 35 USC, 37 CFR
- `get_mpep_section` - Get complete MPEP section by number
### Patent Search
- `search_patents_bigquery` - Search 100M+ patents
- `get_patent_bigquery` - Get full patent details
- `search_patents_by_cpc_bigquery` - Search by CPC classification
### Patent Analysis
- `review_patent_claims` - Analyze claims for 35 USC 112(b)
- `review_specification` - Check specification support (112a)
- `check_formalities` - Verify MPEP 608 compliance
### Diagram Generation
- `render_diagram` - Create diagrams from DOT code
- `create_flowchart` - Generate patent-style flowcharts
- `create_block_diagram` - Create system block diagrams
- `add_diagram_references` - Add reference numbers
## Review Workflows
### Complete Patent Creation Review (/full-review)
Runs all analyzers in **parallel** for comprehensive analysis:
**Output:**
- All compliance issues across components
- Severity ratings (critical/important/minor)
- Specific MPEP citations
- Actionable fix recommendations
- Prioritized remediation plan
### Claims-Only Review (/review-claims)
**35 USC 112(b) Compliance:**
- Antecedent basis
- Definiteness
- Claim structure
- Subjective terms
- Means-plus-function compliance
### Specification Review (/review-specification)
**35 USC 112(a) Requirements:**
- Written description
- Enablement
- Best mode
- Claim support
### Formalities Check (/review-formalities)
**MPEP 608 Compliance:**
- Abstract (50-150 words)
- Title (<=500 characters)
- Drawing references
- Required sections
## Patent Creation Workflow (/create-patent)
Complete 6-phase patent drafting (55-80 minutes):
1. **Discovery (10-15 min)** - Gather invention details
2. **Technology Analysis (5 min)** - Assess patentability (101, 102, 103)
3. **Specification Drafting (15-20 min)** - Background, summary, detailed description
4. **Claims Drafting (10-15 min)** - Independent + dependent claims
5. **Diagrams & Abstract (10-15 min)** - Block diagrams, flowcharts, abstract
6. **Automatic Validation (5-10 min)** - Runs /full-review, provides fixes
**Output:** USPTO-ready filing package with diagrams
## MPEP Research
```python
# General search
search_mpep("claim definiteness 112(b)", top_k=5)
# Filtered by source
search_mpep("enablement", source_filter="35_USC")
search_mpep("abstract", source_filter="MPEP")
# Get specific section
get_mpep_section("2173") # Claim definiteness
```
### Common MPEP Sections
| Section | Topic |
|---------|-------|
| 608 | Formalities (abstract, title, drawings) |
| 2100 | Patentability requirements |
| 2163 | Guidelines for 35 USC 112(a) |
| 2173 | Claim definiteness (35 USC 112(b)) |
## Prior Art Integration
```python
# BigQuery search (100M+ patents)
search_patents_bigquery(
query="neural network training",
country="US",
start_year=2020,
limit=20
)
# CPC classification search
search_patents_by_cpc_bigquery(cpc_code="G06N3", limit=50)
```
**Integrate findings:**
1. Cite in Background section
2. Emphasize distinctions in Summary
3. Explain advantages in Detailed Description
4. Draft claims to avoid/distinguish
5. List in IDS
## Best Practices
**Before Review:**
- Prepare complete application
- Run /full-review
- Address critical issues first
**During Review:**
- Focus on critical issues (antecedent basis, claim support, definiteness)
- Use MPEP citations
- Iterate until compliant
**After Review:**
- Document compliance
- Final /full-review validation
- Prepare filing package
## Common Review Findings
**Critical (Must Fix):**
- Missing antecedent basis
- Claim elements unsupported
- Abstract exceeds 150 words
- Indefinite language
**Important (Should Fix):**
- Subjective terms without criteria
- Weak enablement
- Inconsistent terminology
**Minor (Optional):**
- Add example embodiments
- Strengthen best mode
- Improve claim scope
## Quick Reference
### Key Compliance Checks
| Requirement | Citation | Tool |
|-------------|----------|------|
| Antecedent basis | 35 USC 112(b) | review_patent_claims |
| Written description | 35 USC 112(a) | review_specification |
| Enablement | 35 USC 112(a) | review_specification |
| Abstract length | MPEP 608.01(b) | check_formalities |
| Title format | MPEP 606 | check_formalities |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.