Paper to Chinese Patent Drafter
Yuan1z0825/nature-skills
Drafts Chinese invention patent applications and technical disclosures from research papers or inventor materials, tying each claim feature to source evidence.
Automated analysis of patent applications for EPO compliance with Art.
Install Epo Patent Analyzer
$ npx skills add RobThePCGuy/Claude-Patent-Creator --skill epo-patent-analyzer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install RobThePCGuy/Claude-Patent-Creator epo-patent-analyzer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/epo-patent-analyzer .claude/skills/epo-patent-analyzer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "epo-patent-analyzer" agent skill from https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/epo-patent-analyzer into .claude/skills/epo-patent-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epo-patent-analyzer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/epo-patent-analyzerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add RobThePCGuy/Claude-Patent-Creator --skill epo-patent-analyzer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install RobThePCGuy/Claude-Patent-Creator epo-patent-analyzer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/epo-patent-analyzer .agents/skills/epo-patent-analyzer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "epo-patent-analyzer" agent skill from https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/epo-patent-analyzer into .agents/skills/epo-patent-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epo-patent-analyzer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add RobThePCGuy/Claude-Patent-Creator --skill epo-patent-analyzer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install RobThePCGuy/Claude-Patent-Creator epo-patent-analyzer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/epo-patent-analyzer .cursor/skills/epo-patent-analyzer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "epo-patent-analyzer" agent skill from https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/epo-patent-analyzer into .cursor/skills/epo-patent-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epo-patent-analyzer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/RobThePCGuy/Claude-Patent-Creator.git --path skills/epo-patent-analyzer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add RobThePCGuy/Claude-Patent-Creator --skill epo-patent-analyzer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install RobThePCGuy/Claude-Patent-Creator epo-patent-analyzer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/epo-patent-analyzer .gemini/skills/epo-patent-analyzer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "epo-patent-analyzer" agent skill from https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/epo-patent-analyzer into .gemini/skills/epo-patent-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epo-patent-analyzer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install RobThePCGuy/Claude-Patent-Creator epo-patent-analyzerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add RobThePCGuy/Claude-Patent-Creator --skill epo-patent-analyzer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/epo-patent-analyzer .github/skills/epo-patent-analyzer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "epo-patent-analyzer" agent skill from https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/epo-patent-analyzer into .github/skills/epo-patent-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epo-patent-analyzer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add RobThePCGuy/Claude-Patent-Creator --skill epo-patent-analyzer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install RobThePCGuy/Claude-Patent-Creator epo-patent-analyzer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/epo-patent-analyzer .opencode/skills/epo-patent-analyzer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "epo-patent-analyzer" agent skill from https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/epo-patent-analyzer into .opencode/skills/epo-patent-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epo-patent-analyzer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
epo-patent-analyzer- GitHub stars
- 196
- Token cost
- ~2k tokens
- SKILL.md length
- 655 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Automated analysis of patent applications for EPO compliance with Art.
- Works in 4 steps: Claims Analysis (Art. 84 EPC) → Sufficiency of Disclosure (Art. 83 EPC) → Formalities (Rules 42-49 EPC) → …
- Tasks that involve Intellectual property
- SKILL.md covers When to Use, What This Skill Does, Required Data and How to Use, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Epo Patent Analyzer is an agent skill from RobThePCGuy/Claude-Patent-Creator. 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)
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Legal & Compliance, covering Intellectual property. The repository describes itself as: USPTO patent creation system with MCP server + Claude Code plugin. Hybrid RAG search over MPEP/USC/CFR, BigQuery access to 76M+ patents, automated 35 USC 112 compliance checks… The licence is MIT.
When your agent uses it
- Tasks that involve Intellectual property
Example prompts
- “/epo-patent-analyzer”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Claims Analysis (Art. 84 EPC)
- Sufficiency of Disclosure (Art. 83 EPC)
- Formalities (Rules 42-49 EPC)
- Issue Categorization
What it can do on your machine
Read from SKILL.md and the folder at commit a089731. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Epo Patent Analyzer loads about 2k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 655 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from RobThePCGuy/Claude-Patent-Creator at commit a089731, republished under its MIT licence (© RobThePCGuy). 655 words, ~1,997 tokens.
Download SKILL.mdSave it as
.claude/skills/epo-patent-analyzer/SKILL.md (or your agent's skills folder).- name
- epo-patent-analyzer
- description
- 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)
- tools
- Bash, Read, Write
- model
- sonnet
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"
}
]
}Show full SKILL.md (280 more words)Show less
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
© RobThePCGuy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/epo-patent-analyzer of RobThePCGuy/Claude-Patent-Creator.
Open the folder on GitHubat commit a089731
Compare with similar skills
Epo Patent Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Epo Patent Analyzer this skillRobThePCGuy/Claude-Patent-Creator | 196 | — | ~2k | Automated safety check: Pass | MIT | |
| Paper to Chinese Patent DrafterYuan1z0825/nature-skills | 47k | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Paper To Cn Patentsnipp-zha/Paper-to-patent-Skill | 106 | 1 repos | ~959 | Automated safety check: Pass | None | |
| Patent Examinegfodor/legal-skills | 393 | — | ~4.8k | Automated safety check: Pass | GPL-3.0 | |
| Patent Auditgfodor/legal-skills | 393 | — | ~2.9k | Automated safety check: Pass | GPL-3.0 | |
| Replica BrandJakeschincariol/replica-skill | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Paper To Cn Patent
snipp-zha/Paper-to-patent-Skill
Convert scientific papers, theses, technical reports, source code, figures, or research manuscripts into evidence-grounded Chinese invention patent drafts.
Patent Examine
gfodor/legal-skills
Iteratively examine and revise a draft U.S. An agent skill from gfodor/legal-skills.
Patent Audit
gfodor/legal-skills
Audit a draft U.S. An agent skill from gfodor/legal-skills.
Replica Brand
Jakeschincariol/replica-skill
Names and rebrands an app clone so it is the user's own: name candidates with the trademark, domain, store and handle checks to run, a new palette checked for contrast, a logo brief, a voice guide…
Patent Workaround
gfodor/legal-skills
Adversarially pressure-test a draft or pending U.S. An agent skill from gfodor/legal-skills.
More from RobThePCGuy/Claude-Patent-Creator
All 17 skills in this repoBigquery 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
Development Assistant
RobThePCGuy/Claude-Patent-Creator
Guides through adding new features, MCP tools, analyzers, and extending the patent creator system.
Epc Search
RobThePCGuy/Claude-Patent-Creator
RAG search across EPC provisions, EPO Guidelines for Examination, and PCT rules for European and international patent law research
Epo Patent Search
RobThePCGuy/Claude-Patent-Creator
Search European patents using EPO OPS API (full-text, legal status, families) and BigQuery (100M+ patents, EP filter) for prior art, competitive intelligence, and freedom-to-operate analysis
Index Manager
RobThePCGuy/Claude-Patent-Creator
Manages MPEP index lifecycle including downloads, building, maintenance, and optimization.
Mpep Search
RobThePCGuy/Claude-Patent-Creator
Expert system for searching USPTO MPEP, 35 USC statutes, 37 CFR regulations, and post-Jan 2024 updates.
Related
Categories
Questions about Epo Patent Analyzer
What does Epo Patent Analyzer do?
Automated analysis of patent applications for EPO compliance with Art. Epo Patent Analyzer is an agent skill from RobThePCGuy/Claude-Patent-Creator. Automated analysis of patent applications for EPO compliance with Art.
When should I use Epo Patent Analyzer?
Epo Patent Analyzer fits situations like: tasks that involve Intellectual property.
How do I install Epo Patent Analyzer in Claude Code?
Run `npx skills add RobThePCGuy/Claude-Patent-Creator --skill epo-patent-analyzer -a claude-code`. Or copy the skill folder (skills/epo-patent-analyzer in RobThePCGuy/Claude-Patent-Creator) into .claude/skills/epo-patent-analyzer in your project. Claude Code loads it when a task matches its description.
How do I install Epo Patent Analyzer in Codex?
Run `npx skills add RobThePCGuy/Claude-Patent-Creator --skill epo-patent-analyzer -a codex`. Or copy the skill folder (skills/epo-patent-analyzer in RobThePCGuy/Claude-Patent-Creator) into .agents/skills/epo-patent-analyzer in your project. Codex loads it when a task matches its description.
Can I use Epo Patent Analyzer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add RobThePCGuy/Claude-Patent-Creator --skill epo-patent-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/epo-patent-analyzer, .gemini/skills/epo-patent-analyzer, .github/skills/epo-patent-analyzer and .opencode/skills/epo-patent-analyzer in your project.
What does Epo Patent Analyzer need to run?
SKILL.md names no scripts, command-line tools or credentials: Epo Patent Analyzer is instructions for the agent only. Our summary lists: Python 3.
Does Epo Patent Analyzer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Epo Patent Analyzer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Epo Patent Analyzer use?
Epo Patent Analyzer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Epo Patent Analyzer use?
About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Epo Patent Analyzer?
Skills that share tags, products or a category with Epo Patent Analyzer: Paper to Chinese Patent Drafter (Yuan1z0825/nature-skills, 47k stars), Paper To Cn Patent (snipp-zha/Paper-to-patent-Skill, 106 stars), Patent Examine (gfodor/legal-skills, 393 stars) and Patent Audit (gfodor/legal-skills, 393 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Epo Patent Analyzer?
RobThePCGuy (a GitHub user) maintains it in RobThePCGuy/Claude-Patent-Creator, which has 196 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.
Source: RobThePCGuy/Claude-Patent-Creator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.