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.
Patent prior-art and landscape intelligence skill — not generic patent help.
Install Patent
$ npx skills add alirezarezvani/claude-skills --skill patent -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills patent --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/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/research/patent/skills/patent .claude/skills/patent && 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 "patent" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/research/patent/skills/patent into .claude/skills/patent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent", 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/alirezarezvani/claude-skills/tree/main/research/patent/skills/patentType 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 alirezarezvani/claude-skills --skill patent -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills patent --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/research/patent/skills/patent .agents/skills/patent && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "patent" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/research/patent/skills/patent into .agents/skills/patent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent", 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 alirezarezvani/claude-skills --skill patent -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills patent --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/research/patent/skills/patent .cursor/skills/patent && 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 "patent" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/research/patent/skills/patent into .cursor/skills/patent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent", 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/alirezarezvani/claude-skills.git --path research/patent/skills/patent--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 alirezarezvani/claude-skills --skill patent -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills patent --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/research/patent/skills/patent .gemini/skills/patent && 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 "patent" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/research/patent/skills/patent into .gemini/skills/patent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent", 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 alirezarezvani/claude-skills patentInstalls 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 alirezarezvani/claude-skills --skill patent -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/research/patent/skills/patent .github/skills/patent && 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 "patent" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/research/patent/skills/patent into .github/skills/patent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent", 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 alirezarezvani/claude-skills --skill patent -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-skills patent --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/research/patent/skills/patent .opencode/skills/patent && 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 "patent" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/research/patent/skills/patent into .opencode/skills/patent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent", 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
patent- GitHub stars
- 28k
- Token cost
- ~4.1k tokens
- SKILL.md length
- 1,823 words
- Files
- 7 (incl. scripts, references)
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Patent prior-art and landscape intelligence skill — not generic patent help.
- Works in 7 steps: Grill-Me Intake (6 forcing questions,… → Search Strategy Selection → Multi-Source Search (Sequential) → …
- The user asks for patent searching
- SKILL.md covers Non-Generic Framing — The…, Agent Integrity Rules…, Phase 1: Grill-Me Intake (6… and Phase 2: Search Strategy…, plus 11 more sections
- Runs Python scripts from its folder; calls python and python3; reaches patents.google.com and worldwide.espacenet.com
What it does
Patent is an agent skill from alirezarezvani/claude-skills. Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits…
Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `references/cpc_classification_canon.md`, `references/legal_disclaimer_discipline.md` and `references/sub_use_case_routing.md`).
It sits in Legal & Compliance, covering Intellectual property. It works with Microsoft Word. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.
When your agent uses it
- The user asks for patent searching
- Prior art search for [invention]
- Freedom to operate analysis for [product])
Example prompts
- “prior art search for [invention]”
- “freedom to operate analysis for [product]”
- “/patent”
Requirements
- Python 3
- Node.js
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 19392f7. 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
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
patents.google.comworldwide.espacenet.compatents.uspto.gov
Also links to:
ppubs.uspto.govlens.org
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
Patent loads about 4.1k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 238 tokens; SKILL.md has 1,823 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); the scripts in this folder are not scanned.
SKILL.md
The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 1,823 words, ~4,109 tokens.
Download SKILL.mdSave it as
.claude/skills/patent/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- patent
- description
- Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
- license
- MIT
- metadata.source_spec
- megaprompts/11-patent-megaprompt.md
- metadata.build_pattern
- Path B (direct conversion)
- metadata.research_pack_convention
- Agent Integrity Rules verbatim per PR #657 audit; sub-use-case routing variant
- metadata.version
- 1.0.0
Patent — Prior-Art + Landscape Intelligence
Portability: Requires
web_fetch(Google Patents, Espacenet, USPTO),WebSearch(adjacent academic art), Node.js withdocxpackage, and optionally Lens.org API key for citation-graph signals. Works in Claude Code CLI natively. In Claude.ai with web tools + Code Execution + BYOK Lens.org, the workflow is supported.
Out of scope: trademark, copyright, trade-secret. These are flagged at intake. Use a different skill or qualified counsel.
Legal disclaimer: This skill produces search signal, not legal advice. Verdicts are technical assessments. Always consult a patent attorney before filing or licensing decisions.
Non-Generic Framing — The Differentiator
This skill is prior-art + landscape intelligence. It refuses to be a bucket. Every invocation commits to one of five sub-use-cases via the grill-me intake before any search runs. The chosen sub-use-case dictates the entire search strategy, ranking heuristics, and DOCX emphasis.
| Sub-use-case | Search strategy | DOCX emphasis |
|---|---|---|
| Novelty search | Narrow + claims-text focused; pre-filing date irrelevant | Closest art + claim-differentiation |
| Freedom-to-operate | Broad + active patents only; jurisdiction-filtered | FTO flags + claim-by-claim risk |
| Competitive landscape | Breadth + filer tally + CPC trends | Filer map + investment hotspots |
| Acquisition diligence | Specific assignee + portfolio scope + assignment chain | Portfolio table + ownership verification |
| Litigation prior-art | Specific target patent + adjacent art before priority date | Knock-out candidates ranked by relevance |
See references/sub_use_case_routing.md for the canon.
Agent Integrity Rules (Research-Pack Convention)
Locked verbatim per PR #657 audit.
- Execution discipline. Sequential search calls only. 1 query/sec rate limit. Confirm response received before next call.
- Source discipline. Cite only patents returned by THIS session's tool calls. Training knowledge labeled
[Not from search — reference information]and excluded from counts. - Three-count tracking. Queries sent / patents received (shown) / patents cited. Surfaced in audit log.
- Retry policy. On failure → wait 3s → retry once → log. After 3 consecutive failures across tools: stop, alert user, explain what's missing.
- Plan-tier detection. Lens.org free tier = 1000 queries/month. Google Patents has no auth but rate-limits per IP. Detect and surface caps.
Phase 1: Grill-Me Intake (6 forcing questions, one at a time)
Q1 (root) — Invention description
Describe the invention in 2–3 sentences. What does it do, and what's new about it?
Why I'm asking: Concept and keyword extraction depends entirely on a precise description. Vague descriptions ("AI for healthcare", "a better widget") will be rejected — push back and ask the user to specify what the invention does and what differentiates it from existing approaches.
Refuse mush. If answer is generic, ask once more: "What does it do that existing systems don't?" Then commit (with caveat in DOCX).
Q2 (depends on Q1) — Sub-use-case commitment
What's the purpose of this search? Pick one:
- Novelty search (am I novel enough to file)
- Freedom-to-operate (will I get sued if I ship)
- Competitive landscape (who else plays here)
- Acquisition diligence (does target really own X)
- Litigation prior-art hunting (kill a specific patent)
Why I'm asking: Each path uses a fundamentally different search strategy. I'll refuse to start without you picking one.
Forcing format. If user says "all of them", push for the primary purpose — secondary purposes can run as follow-up searches.
Q3 (asked only if Q2 ∈ {FTO, landscape, diligence}) — Jurisdictions
Which jurisdictions matter? Pick all that apply: US / EP / CN / JP / KR / PCT / worldwide.
Why I'm asking: FTO only matters where you'll sell. Landscape changes radically by region. Diligence requires checking all jurisdictions where the target operates.
Skip for novelty (priority date is jurisdictionally portable) and litigation (jurisdiction is set by the target patent).
Q4 (depends on Q1) — Known prior art
Have you already seen prior art close to this? Cite a patent number or paper.
Why I'm asking: If you know one piece of art, I can search adjacent to it — much more precise than starting cold. If you don't, that's fine — just confirm.
Anchoring. Accept "none" but ask if the user has seen any related work even informally.
Q5 (depends on Q2) — Risk tolerance
Risk tolerance for this search: strict (one close hit means abandon the path) or signal-gathering (you want the lay of the land regardless)?
Why I'm asking: Strict mode ranks aggressively and surfaces verdict-grade hits; signal mode prioritizes breadth and visualizations.
Asked for novelty and FTO; skipped for pure landscape (always signal-gathering by definition).
Q6 (asked only if Q2 ∈ {novelty, FTO}) — Attorney status
Have you spoken to a patent attorney? This skill produces search signal, not legal advice. Confirm you understand this is for technical assessment only.
Why I'm asking: Novelty and FTO have legal consequences. The skill's verdict is signal-grade; legal positions require qualified counsel.
Triggers the legal-disclaimer footer in the DOCX. Skipped for landscape and diligence (lower legal exposure).
Stop condition: After Q6 (or earlier if dependency skips applied), commit and start Phase 2. Never re-open intake after Phase 2 begins.
Phase 2: Search Strategy Selection
Deterministic from intake answers. Use scripts/sub_use_case_router.py:
python scripts/sub_use_case_router.py \
--sub-use-case novelty \
--jurisdictions "" \
--risk strict \
--known-art "US10000000B2"Returns: query plan (5-8 queries) + ranking heuristic + DOCX emphasis flags.
Phase 3: Multi-Source Search (Sequential)
Source priority
- Google Patents (https://patents.google.com) — workhorse, no auth required, broad coverage
- Espacenet (https://worldwide.espacenet.com) — global coverage, good for non-US art
- USPTO PPS (https://ppubs.uspto.gov) — US deep dive
- Lens.org (https://www.lens.org) — citation graph, BYOK API key required
Per-sub-use-case query patterns
Novelty:
- 3 narrow queries on invention-specific terminology (Google Patents)
- 2 broad concept queries with synonyms (Google Patents + Espacenet)
- 1 CPC-class-restricted query if class identified from initial hits
FTO:
- Jurisdiction-filtered: only active patents (not expired, not abandoned)
- Date filter: priority < today
- Active-claim text extraction for each hit
Competitive landscape:
- Broader queries on the technology space
- CPC class identification → tally top filers in that class
- 10-year filing trend by year per top-5 filer
Acquisition diligence:
- Specific assignee searches (target company + subsidiaries + named inventors)
- Assignment chain check (USPTO assignment recordation)
- Family resolution for deduplication
Litigation prior-art:
- Target patent input required (number)
- Priority date extraction
- Search for art before priority date in same CPC classes
- Adjacent-claim-language search
Sequential discipline
1 q/sec across ALL sources combined. Tracked via scripts/citation_tracker.py with timestamp-enforced gap.
Phase 4: Claim Extraction + Relevance Scoring
For each closest-art hit:
- Pull independent claim 1 (the broadest claim — primary anticipation/obviousness vehicle)
- Pull key dependent claims (claims that add the inventive step)
- Score relevance against invention description (overlap of claim language with Q1 terminology)
Rank by score. Verdict per sub-use-case (NOVEL / POTENTIALLY NOVEL / NOT NOVEL for novelty; CLEAR / FLAGGED / HIGH RISK per jurisdiction for FTO).
Phase 5: Citation Graph + Family Resolution
Citation graph (Lens.org BYOK)
If user provides Lens.org API key:
- Foundational-patent identification (cited-by count > threshold, typically 50+)
- Recent high-cite signals (citations in last 24 months as proxy for current activity)
- Forward citations from target patent (litigation prior-art) or from closest art (novelty)
If no Lens.org key: skip; note in audit log; recommend manual citation review on Google Patents.
Show full SKILL.md (730 more words)Show less
Family resolution
Same invention often filed in multiple jurisdictions (US + EP + JP + CN). Group by family ID or priority number to avoid double-counting. Use scripts/family_resolver.py:
python scripts/family_resolver.py --hits-file hits.json
# Returns: deduplicated family list + family-member jurisdictionsCPC/IPC Classification Awareness
Critical: keyword search alone misses adjacent art. After initial search, extract the CPC/IPC classes from top 5 hits and run one class-restricted query. This consistently surfaces art that keyword search misses.
See references/cpc_classification_canon.md for the canon.
Phase 6: DOCX Generation (8 Sections)
Sub-use-case-dependent emphasis. Via Node.js + docx library.
- Executive Summary + Verdict — Sub-use-case banner + one-line verdict (NOVEL / FLAGGED / etc.) + 3-4 key findings + legal disclaimer footer
- Closest Prior Art — 5-10 patents in ranked order. Per hit: hyperlinked title + assignee + filing/priority dates + independent claim 1 text (italicized) + relevance score + relevance rationale (1-2 sentences)
- Patent Landscape — Top filers table (top 10 by count) + 10-year filing trend description + CPC class distribution table. Only for landscape and diligence; abbreviated otherwise.
- Citation Graph Signals — Foundational patents (if Lens-enabled) + recent high-cite activity. If Lens unavailable, note "manual review recommended" and skip table.
- Geographic Coverage — Filings by jurisdiction for top 10 hits. Only for FTO, landscape, diligence; skipped for novelty and litigation.
- FTO Flags (FTO only) — Active patents posing infringement risk. Per flag: hyperlinked patent + jurisdiction + relevant claims + risk level (HIGH/MEDIUM/LOW) + mitigation note.
- Strategy + Recommendations — Sub-use-case-specific:
- Novelty → claim differentiation suggestions
- FTO → design-around hints + jurisdiction strategy
- Landscape → who-to-watch list
- Diligence → red flags in portfolio
- Litigation → ranked knock-out candidates
- Mandatory disclaimer to consult patent attorney for any filing/licensing decision.
- Audit Log — Searches table (#, query, source, results, status), counts (sent/shown/cited), tool constraints (plan-tier notes), failed steps, attorney-consultation reminder
Styling
Arial 12pt body, navy headings (#1a3a5c), light blue table headers (#e8f0f8), red FTO-flag callout. ExternalHyperlink patterns:
- Google Patents:
https://patents.google.com/patent/[number] - Espacenet:
https://worldwide.espacenet.com/patent/... - USPTO:
https://patents.uspto.gov/patent/...
Date Discipline
Distinguish at every hit:
- Filing date — when the application was first submitted
- Priority date — earliest claim of priority (often earlier than filing)
- Publication date — when the application became public (typically 18 months after priority)
- Grant date — when the patent was granted (later than publication)
Surface the legally-relevant date per sub-use-case:
- Novelty → priority date (vs invention's anticipated filing date)
- FTO → grant date + status (active vs expired)
- Landscape → publication date (when public knowledge began)
- Diligence → grant date + assignment date
- Litigation → priority date of target patent (sets the prior-art cutoff)
Phase 7: Deliver
- Save:
<output-dir>/patent_<invention-slug>_<sub-use-case>_<YYYY-MM-DD>.docx - Chat summary: file path + sub-use-case + verdict + audit counts + plan-tier
- Validate: check zip integrity with
python3 -c "import zipfile,sys; zipfile.ZipFile(sys.argv[1]).testzip()" <docx>(no output = intact), then confirm the required sections are present - Reminder: "Consult patent attorney before filing/licensing"
Tooling
| Script | Role |
|---|---|
scripts/citation_tracker.py | Multi-source three-count audit (Google Patents + Espacenet + USPTO + Lens.org) at ~/.patent_sessions/<session>.json |
scripts/family_resolver.py | Group same-invention filings across jurisdictions by family ID / priority number |
scripts/sub_use_case_router.py | Deterministic search-strategy selection from intake answers |
References
references/sub_use_case_routing.md— 5-sub-use-case canon (7+ sources)references/cpc_classification_canon.md— CPC/IPC class follow-up rationale (7+ sources)references/legal_disclaimer_discipline.md— when + why disclaimer mandatory (7+ sources)
Error Handling
| Failure | Behavior |
|---|---|
| User refuses to commit to sub-use-case | Refuse to proceed. Re-ask Q2 with examples. |
| Invention description is generic | Reject answer. Re-ask Q1 with "what does it do that existing systems don't?" |
| Google Patents rate-limits | Wait 3s, retry once. Fall back to Espacenet for that query. Log in audit. |
| Lens.org key missing | Skip citation graph section, note "manual review recommended" in DOCX. |
| Claim text extraction fails | Fall back to abstract; flag as "abstract-only" in relevance rationale. |
| Family resolution incomplete | Note in audit; same-invention duplicates may appear; suggest manual deduplication. |
| All searches return <3 hits | Surface explicitly as "either niche art or genuine gap"; never fabricate. |
| 3 consecutive tool failures | Stop, alert user, explain what's missing. |
| DOCX generation fails | Save raw data as JSON fallback so user doesn't lose work. |
| Target patent number invalid (litigation) | Validate format before search; ask user to confirm. |
Anti-Patterns To Reject
- Starting any search before user commits to a sub-use-case (refuses generic "patent help")
- Batching all intake questions instead of one at a time
- Accepting vague invention descriptions ("AI for healthcare")
- Keyword-only search without CPC/IPC class follow-up
- Treating family members as separate hits (must be deduplicated)
- Confusing filing date with priority date with publication date
- Skipping the legal disclaimer when sub-use-case has legal consequences
- Reporting a verdict without claim-text evidence
- Fabricating Lens.org citation data when key is absent
- Suggesting design-arounds without acknowledging attorney review is required
- Skipping the audit log
Version: 1.0.0
Source spec: megaprompts/11-patent-megaprompt.md (maintainer-local draft spec — gitignored, not present in the public repository)
Build pattern: Path B (direct conversion). Research-pack sibling, sub-use-case routing variant.
© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (scripts, references) in research/patent/skills/patent of alirezarezvani/claude-skills.
- SKILL.md
- references/cpc_classification_canon.md
- references/legal_disclaimer_discipline.md
- references/sub_use_case_routing.md
- scripts/citation_tracker.py
- scripts/family_resolver.py
- scripts/sub_use_case_router.py
Open the folder on GitHubat commit 19392f7
Compare with similar skills
Patent 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 |
|---|---|---|---|---|---|---|
| Patent this skillalirezarezvani/claude-skills | 28k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Paper to Chinese Patent DrafterYuan1z0825/nature-skills | 46k | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Paper To Cn Patentsnipp-zha/Paper-to-patent-Skill | 105 | 1 repos | ~959 | Automated safety check: Pass | None | |
| Patent Disclosure Skilltrsoliu/mini-wiki | 116 | — | ~1.7k | Automated safety check: Notes | MIT | |
| Patent Disclosure Skillqzzqzzb/OpenClaudeScience | 106 | — | ~1.6k | Automated safety check: Notes | MIT | |
| Jurisdiction FormatAI4Scientist/nano-scientist | 128 | 2 repos | ~1.6k | Automated safety check: Notes | None |
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 Disclosure Skill
trsoliu/mini-wiki
中国专利：从项目文档挖掘专利点并生成可交付技术交底书（查新、脱敏成文、自检与迭代）；或将已有专利解读为通俗笔记与 Obsidian 知识图谱（叙事故事线、公开线索辅助）。| China patents: draft technical disclosures from project docs, or read existing patents into plain-language…
Patent Disclosure Skill
qzzqzzb/OpenClaudeScience
通用中国专利挖掘发现与交底书生成全流程：扫描项目文档挖掘专利点、讨论融合、基于脱敏模版生成技术交底书、联网查新、生成后自检含逻辑闭环与公式参数一致性。| Patent mining, disclosure drafting, prior-art search, and consistency self-check.
Jurisdiction Format
AI4Scientist/nano-scientist
Compile patent application into jurisdiction-specific filing format.
Paper2patent
7toCR/paper2patent
Turn an academic paper (PDF, LaTeX, pasted text, thesis chapter or technical disclosure) into a Chinese invention patent application draft — 说明书摘要、摘要附图、权利要求书、说明书、说明书附图 — delivered as DOCX/PDF with…
More from alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Works with
Categories
Questions about Patent
What does Patent do?
Patent prior-art and landscape intelligence skill — not generic patent help. Patent is an agent skill from alirezarezvani/claude-skills. Patent prior-art and landscape intelligence skill — not generic patent help.
When should I use Patent?
Patent fits situations like: the user asks for patent searching; prior art search for [invention]; freedom to operate analysis for [product]).
How do I install Patent in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill patent -a claude-code`. Or copy the skill folder (research/patent/skills/patent in alirezarezvani/claude-skills) into .claude/skills/patent in your project. Claude Code loads it when a task matches its description.
How do I install Patent in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill patent -a codex`. Or copy the skill folder (research/patent/skills/patent in alirezarezvani/claude-skills) into .agents/skills/patent in your project. Codex loads it when a task matches its description.
Can I use Patent 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 alirezarezvani/claude-skills --skill patent -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/patent, .gemini/skills/patent, .github/skills/patent and .opencode/skills/patent in your project.
What does Patent need to run?
Going by SKILL.md and its folder, Patent needs Python for the scripts in its folder and the command-line tools its instructions call (python and python3). Our summary lists: Python 3; Node.js.
Does Patent access the network?
SKILL.md names 5 domains. In commands or code: patents.google.com, worldwide.espacenet.com and patents.uspto.gov; the agent is likely to contact these when it follows the instructions. As links in the text: ppubs.uspto.gov and lens.org. This is read from the text; nothing was executed.
Is Patent 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Patent use?
Patent is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Patent use?
About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.9k tokens, read only when the agent opens those files.
What are the alternatives to Patent?
Skills that share tags, products or a category with Patent: Paper to Chinese Patent Drafter (Yuan1z0825/nature-skills, 46k stars), Paper To Cn Patent (snipp-zha/Paper-to-patent-Skill, 105 stars), Patent Disclosure Skill (trsoliu/mini-wiki, 116 stars) and Patent Disclosure Skill (qzzqzzb/OpenClaudeScience, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Patent?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,829 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.