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 Professional Agents 一个专业的多代理专利撰写与优化技能套件,覆盖专利申请全流程。
$ npx skills add LeoYeAI/openclaw-master-skills --skill patent-professional-agents -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills patent-professional-agents --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/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/patent-professional-agents .claude/skills/patent-professional-agents && 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-professional-agents" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/patent-professional-agents into .claude/skills/patent-professional-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent-professional-agents", 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/LeoYeAI/openclaw-master-skills/tree/main/skills/patent-professional-agentsType 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 LeoYeAI/openclaw-master-skills --skill patent-professional-agents -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills patent-professional-agents --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/patent-professional-agents .agents/skills/patent-professional-agents && 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-professional-agents" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/patent-professional-agents into .agents/skills/patent-professional-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent-professional-agents", 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 LeoYeAI/openclaw-master-skills --skill patent-professional-agents -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills patent-professional-agents --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/patent-professional-agents .cursor/skills/patent-professional-agents && 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-professional-agents" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/patent-professional-agents into .cursor/skills/patent-professional-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent-professional-agents", 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/LeoYeAI/openclaw-master-skills.git --path skills/patent-professional-agents--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 LeoYeAI/openclaw-master-skills --skill patent-professional-agents -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills patent-professional-agents --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/patent-professional-agents .gemini/skills/patent-professional-agents && 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-professional-agents" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/patent-professional-agents into .gemini/skills/patent-professional-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent-professional-agents", 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 LeoYeAI/openclaw-master-skills patent-professional-agentsInstalls 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 LeoYeAI/openclaw-master-skills --skill patent-professional-agents -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/patent-professional-agents .github/skills/patent-professional-agents && 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-professional-agents" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/patent-professional-agents into .github/skills/patent-professional-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent-professional-agents", 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 LeoYeAI/openclaw-master-skills --skill patent-professional-agents -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills patent-professional-agents --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/patent-professional-agents .opencode/skills/patent-professional-agents && 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-professional-agents" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/patent-professional-agents into .opencode/skills/patent-professional-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent-professional-agents", 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.
patent-professional-agents📜 专利专业代理 - Patent Professional Agents 一个专业的多代理专利撰写与优化技能套件,覆盖专利申请全流程。
Patent Professional Agents is an agent skill from LeoYeAI/openclaw-master-skills. 📜 专利专业代理 - Patent Professional Agents 一个专业的多代理专利撰写与优化技能套件,覆盖专利申请全流程。 🎯 核心功能: • 场景一:用户想法 → 技术挖掘 → 检索分析 → 专利撰写 → 质量审核 • 场景二:用户初稿 → 问题分析 → 优化建议 → 强化权利要求 • 场景三:代理机构反馈 → 风险评估 → 优化/取消建议 🤖 9个专业代理: tech-miner (技术挖掘)、prior-art-researcher (现有技术检索)、inventiveness-evaluator (创造性评估)、patent-drafter (专利撰写)、claims-architect (权利要求架构)、patent-analyst (专利分析)、patent-auditor (专利审核)、patent-value-appraiser (价值评估)、patent-converter (文档转换) ✨ 特色: • 中英文双语支持 • 7章节标准专利模板 • 授权率预判 • 自动Word文档转换 • 持续学习能力 🔍 搜索关键词:专利, patent, 专利撰写, 专利优化, 现有技术检索…
Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 22 other files (for example `_meta.json`, `agents/claims-architect/SOUL.md` and `agents/inventiveness-evaluator/SOUL.md`).
It sits in Legal & Compliance, covering Intellectual property. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
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.
Ships script files (Python, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
pipFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use pip, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Patent Professional Agents loads about 5k tokens when it runs. Until then it costs about 162 tokens; SKILL.md has 1,291 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.
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.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,291 words, ~4,998 tokens.
.claude/skills/patent-professional-agents/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.MIT License
Copyright (c) 2026 BigPiPiHua
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
| Scenario | Input | Output | Goal |
|---|---|---|---|
| Scenario 1 | User idea (vague description) | Complete patent document + Search report | Grant rate + Inventiveness |
| Scenario 2 | User draft (existing document) | Optimized patent document | Grant rate + Inventiveness |
| Scenario 3 | Agency feedback (search report/prior art) | Optimization suggestions / Cancellation advice | Decision support |
Boundary: Does not handle Office Action (OA) responses - leave that to professional patent agencies.
| Skill | Purpose | Install Command |
|---|---|---|
tavily-search | AI-optimized search | clawhub install tavily-search |
aminer-open-academic | Academic paper search | clawhub install aminer-open-academic |
pip install requests python-docx| Agent | Role | Core Capability | Priority |
|---|---|---|---|
| tech-miner | Technology Mining Expert | Idea analysis, innovation extraction, technical disclosure framework | ⭐⭐⭐⭐⭐ |
| prior-art-researcher | Prior Art Search Expert | Keyword strategy + Multi-source search + Analysis | ⭐⭐⭐⭐⭐ |
| inventiveness-evaluator | Inventiveness Evaluation Expert | Inventiveness analysis, risk scoring, grant rate prediction | ⭐⭐⭐⭐⭐ |
| patent-drafter | Patent Drafting Expert | 7-section drafting, Mermaid diagrams, document conversion | ⭐⭐⭐⭐⭐ |
| claims-architect | Claims Architect | Claims design, scope optimization | ⭐⭐⭐⭐ |
| patent-analyst | Patent Analyst | Draft analysis, issue identification, optimization suggestions | ⭐⭐⭐⭐ |
| patent-auditor | Patent Audit Expert | Quality review, grant rate prediction, revision suggestions | ⭐⭐⭐⭐⭐ |
| patent-value-appraiser | Patent Value Appraiser | 5-dimension value assessment, market value estimation | ⭐⭐⭐⭐ |
| patent-converter | Document Conversion Expert | Markdown→Word, Mermaid diagram embedding | ⭐⭐⭐⭐ |
flowchart TB
subgraph S1[Phase 1: Tech Mining]
M1[tech-miner<br/>Understand idea] ~~~ M2[Extract innovations] ~~~ M3[Disclosure framework]
end
subgraph S2[Phase 2: Search]
R1[prior-art-researcher<br/>Keyword strategy] ~~~ R2[Multi-source search] ~~~ R3[Analyze results]
end
subgraph S3[Phase 3: Evaluation]
E1[inventiveness-evaluator<br/>Inventiveness analysis] ~~~ E2[Risk scoring] ~~~ E3[Differentiation advice]
end
subgraph S4[Phase 4: Drafting]
D1[patent-drafter<br/>Draft specification] ~~~ C1[claims-architect<br/>Design claims]
end
subgraph S5[Phase 5: Review]
A1[patent-auditor<br/>Full review] ~~~ A2[Grant rate prediction]
end
S1 --> S2 --> S3 --> S4 --> S5Trigger:
"Help me write a patent: [technical idea]"
"I have an idea and want to apply for a patent"Output Files:
TECH_DISCLOSURE.md - Technical disclosure frameworkKEYWORD_STRATEGY.md - Keyword strategyPATENT_SEARCH_REPORT.md - Search reportINVENTIVENESS_REPORT.md - Inventiveness evaluation reportPatent-*.md - Complete patent document (7-section standard format)PATENT_AUDIT_REPORT.md - Audit report (with grant rate prediction)Patent-*.docx - Word document (auto-converted)flowchart TB
subgraph P1[Phase 1: Analysis]
A1[patent-analyst<br/>Parse draft] ~~~ A2[Identify issues] ~~~ A3[Extract keywords]
end
subgraph P2[Phase 2: Search]
R1[prior-art-researcher<br/>Targeted search] ~~~ R2[Analyze results]
end
subgraph P3[Phase 3: Evaluation]
E1[inventiveness-evaluator<br/>Inventiveness risk] ~~~ E2[Enhancement suggestions]
end
subgraph P4[Phase 4: Optimization]
D1[patent-drafter<br/>Optimize specification] ~~~ C1[claims-architect<br/>Strengthen claims]
end
subgraph P5[Phase 5: Review]
Q1[patent-auditor<br/>Full review] ~~~ Q2[Grant rate prediction]
end
P1 --> P2 --> P3 --> P4 --> P5Trigger:
"Help me optimize this patent: /path/to/patent.md"
"Review this patent and provide optimization suggestions"Output Files:
PATENT_ANALYSIS_REPORT.md - Analysis reportPATENT_SEARCH_REPORT.md - Search reportINVENTIVENESS_REPORT.md - Inventiveness evaluation reportPATENT_OPTIMIZATION_SUGGESTIONS.md - Optimization suggestionsPatent-*.md - Optimized patent documentPATENT_AUDIT_REPORT.md - Audit reportUse Case: User has submitted to a patent agency, received a search report or prior art, needs to evaluate whether to continue optimizing or cancel the application.
flowchart TB
subgraph F1[Phase 1: Read Feedback]
R1[Read search report] ~~~ R2[Read prior art] ~~~ R3[Read original draft]
end
subgraph F2[Phase 2: Comparative Analysis]
A1[inventiveness-evaluator<br/>Comparison] ~~~ A2[Identify conflicts] ~~~ A3[Assess differentiation space]
end
subgraph F3[Phase 3: Decision]
D1{Inventiveness space?}
D2[🟢 Sufficient<br/>Recommend optimization]
D3[🟡 Limited<br/>User confirmation needed]
D4[🔴 No space<br/>Recommend cancellation]
D1 --> D2
D1 --> D3
D1 --> D4
end
subgraph F4[Phase 4: Optimization]
O1[patent-drafter<br/>Targeted optimization] ~~~ O2[Strengthen differences] ~~~ O3[patent-auditor<br/>Final review]
end
F1 --> F2 --> F3
D2 --> F4
D3 -->|User confirms| F4
D4 --> X[Output cancellation report]Trigger:
"The agency gave me a search report, help me see if I can optimize: /path/to/report.pdf"
"Here's the prior art, help me evaluate if I need to modify the patent"
"The agency says there's risk, should I continue or cancel?"Output Files:
AGENCY_FEEDBACK_ANALYSIS.md - Agency feedback analysisDECISION_RECOMMENDATION.md - Decision recommendation (continue/cancel)PATENT_OPTIMIZATION_SUGGESTIONS.md - Targeted optimization suggestionsDecision Criteria:
| Inventiveness Space | Basis | Recommendation |
|---|---|---|
| 🟢 Sufficient | Core features not disclosed, clear differentiation points | Continue optimization, strengthen differences |
| 🟡 Limited | Some features disclosed, need repositioning | User confirmation required |
| 🔴 No space | Core features already disclosed, cannot circumvent | Recommend cancellation or redesign |
Identity: Dr. Li, 15 years of technology assessment and innovation mining experience
Trigger: When user provides vague idea
Output: Technical disclosure framework
Use tech-miner to analyze the technical idea:
[User description]Identity: Dr. Chen, 15 years of patent search experience
Trigger: When search is needed
Output: Search report + analysis
Use prior-art-researcher to search:
Keywords: [keywords]
Technical field: [field]Search Channels (Default):
| Priority | Channel | Tool | Purpose |
|---|---|---|---|
| 1 | Tavily | tavily-search | Quick search, technical overview |
| 2 | AMiner | aminer-open-academic | Academic papers + patent database |
| 3 | Google Patents | web_fetch | Global patent full text |
| 4 | GitHub | tavily site: | Open source projects |
| 5 | Tech blogs | tavily site: | Technical articles |
⚠️ Patent Database APIs Recommended:
Default channels may not be sufficient for accurate patent prior art search. For professional patent search, recommend users to connect patent database APIs:
| Database | API Type | Coverage | Best For |
|---|---|---|---|
| Google Patents | Public API | 100+ offices | Global search |
| USPTO | Public API | US patents | US details |
| EPO (Espacenet) | Public API | European patents | EP search |
| CNIPA | Public API | Chinese patents | CN search |
| WIPO | Public API | PCT applications | International |
| Lens.org | Free API | Global patents | Academic research |
ClawHub Skill Discovery:
# Always check ClawHub for patent search skills
clawhub search patent
clawhub search "prior art"Identity: Dr. Zhao, former examiner, 12 years of evaluation experience
Trigger: After search completion
Output: Inventiveness evaluation report (with risk score)
Use inventiveness-evaluator to evaluate inventiveness:
Patent document: /path/to/patent.md
Search report: PATENT_SEARCH_REPORT.mdIdentity: Patricia, 12 years of drafting experience, 92% grant rate
Trigger: After inventiveness evaluation passes
Output: Complete patent document (7 sections)
Use patent-drafter to draft patent:
Patent title: [title]
Technical disclosure: TECH_DISCLOSURE.md
Search report: PATENT_SEARCH_REPORT.md
Inventiveness evaluation: INVENTIVENESS_REPORT.mdIdentity: Claude, 1000+ claims experience
Trigger: Parallel participation during drafting phase
Output: Claims document
Use claims-architect to design claims:
Patent document: /path/to/patent.md
Core inventive points: [points]Identity: Dr. Zhang, 12 years of patent analysis experience
Trigger: First step in optimization scenario
Output: Analysis report + optimization suggestions
Use patent-analyst to analyze patent:
Patent document: /path/to/patent.mdIdentity: Judge Wu, former examiner, reviewed 3000+ applications
Trigger: After drafting/optimization completion
Output: Audit report (with grant rate prediction)
Use patent-auditor to audit patent:
Patent document: /path/to/patent.mdIdentity: Ms. Lin, 10 years of patent valuation experience, certified IP asset appraiser
Trigger: User needs to evaluate existing patent value (transfer, pledge, financing)
Output: Patent value assessment report (5-dimension radar chart + market value range)
Use patent-value-appraiser to evaluate patent value:
Patent title: [title]
Or patent number: [number]
Purpose: pledge financing / licensing negotiation / technology transfer / M&A transaction5 Evaluation Dimensions:
| Dimension | Weight | Content |
|---|---|---|
| Technical Value | 25% | Innovation degree, technical complexity, substitution difficulty |
| Legal Value | 25% | Claim breadth, stability, invalidation resistance |
| Market Value | 25% | Application scenarios, market size, competitive alternatives |
| Economic Value | 15% | Cost savings, revenue potential, licensing income |
| Strategic Value | 10% | Supply chain position, barrier strength, negotiation leverage |
Identity: Alex, document conversion expert, proficient in Markdown → Word conversion
Trigger: Auto-triggered after patent-auditor review passes
Output: Word document (.docx), with embedded Mermaid diagrams
Conversion Flow:
Dependencies:
| Tool | Purpose |
|---|---|
| Pandoc | Markdown → Word conversion |
| mmdc (mermaid-cli) | Mermaid → PNG rendering |
| python-docx | Word document operations |
# [Patent Title]
## 1. Related Prior Art and Their Defects or Deficiencies
### 1.1 Description of Prior Art
### 1.2 Defects or Deficiencies of Prior Art
## 2. Technical Improvements to Overcome the Above Defects
## 3. Alternative Solutions for Technical Improvements
## 4. Detailed Embodiments of the Technical Solution
### 4.1 System Architecture
### 4.2 Signal Logic Relationships
### 4.3 Implemented Functions
### 4.4 Specific Implementation Steps
### 4.5 Embodiment 1
(Describe included components/modules and their connections, signal logic; implemented functions and specific implementation steps)
## 5. Advantages of This Proposal Over Prior Art
(Achieved technical effects)
## 6. Related Drawings
(Structure diagrams with labeled component/module names; flowcharts with clear steps and process directions)
## 7. Claims
(Optional)The agents automatically detect and use the user's language for output.
| User Input Language | Output Language | Template Format |
|---|---|---|
| English | English | 7-Section Standard (English) |
| 中文 | 中文 | 7章节标准模板(中文) |
| Other languages | User's language | 7-Section Standard (translated) |
# [专利名称]
## 一、相关的现有技术及现有技术的缺陷或不足
### 1.1 现有技术描述
### 1.2 现有技术的缺陷或不足
## 二、为克服上述缺陷本提案的技术改进点
## 三、技术改进点的其他替代方案
## 四、详细的技术方案具体实施例
### 4.1 系统架构
### 4.2 信号逻辑关系
### 4.3 实现功能
### 4.4 具体实现步骤
### 4.5 实施例一
## 五、本提案相对现有技术的优点
## 六、相关附图
## 七、权利要求书| File | Content | Phase |
|---|---|---|
TECH_DISCLOSURE.md | Technical disclosure framework | Tech mining |
KEYWORD_STRATEGY.md | Keyword strategy | Search |
PATENT_SEARCH_REPORT.md | Search report | Search |
INVENTIVENESS_REPORT.md | Inventiveness evaluation report | Evaluation |
Patent-*.md | Complete patent document | Drafting |
PATENT_AUDIT_REPORT.md | Audit report (with grant rate) | Review |
| File | Content | Phase |
|---|---|---|
PATENT_ANALYSIS_REPORT.md | Analysis report | Analysis |
PATENT_SEARCH_REPORT.md | Search report | Search |
INVENTIVENESS_REPORT.md | Inventiveness evaluation report | Evaluation |
PATENT_OPTIMIZATION_SUGGESTIONS.md | Optimization suggestions | Optimization |
PATENT_AUDIT_REPORT.md | Audit report (with grant rate) | Review |
| File | Content | Phase |
|---|---|---|
AGENCY_FEEDBACK_ANALYSIS.md | Feedback analysis | Analysis |
DECISION_RECOMMENDATION.md | Decision recommendation | Decision |
PATENT_OPTIMIZATION_SUGGESTIONS.md | Optimization suggestions (if chosen) | Optimization |
| File | Content |
|---|---|
PATENT_VALUE_REPORT.md | 5-dimension value assessment + market value range |
skills/
└── professional-patent-agents/
├── SKILL.md
├── agents/
│ ├── tech-miner/
│ ├── prior-art-researcher/
│ ├── inventiveness-evaluator/
│ ├── patent-drafter/
│ ├── claims-architect/
│ ├── patent-analyst/
│ ├── patent-auditor/
│ ├── patent-value-appraiser/
│ └── patent-converter/
└── skills/
└── continuous-learning/Auto-invoke patent-converter to convert Markdown to Word when:
| Condition | Requirement |
|---|---|
| patent-auditor review result | Passed |
| Grant rate prediction | ≥ 60% (low/medium risk) |
| User confirmation | High risk (< 60%) requires user confirmation |
flowchart TB
A[patent-auditor<br/>Review complete] --> B{Grant rate ≥ 60%?}
B -->|Yes| C[Auto-invoke<br/>patent-converter]
B -->|No| D[Prompt user confirmation]
D -->|Confirm convert| C
D -->|Don't convert| E[Output Markdown only]
C --> F[Output .docx file]
F --> G[Notify user<br/>Ready for agency submission]Source directory/
├── Patent-1-xxx.md # Source Markdown
├── Patent-1-xxx.docx # Converted output (same directory)
├── Patent-2-xxx.md
├── Patent-2-xxx.docx
└── ...memory/
├── 2026-03-16.md # Daily work records
├── 2026-03-17.md
├── 2026-03-18.md
└── ...📢 Innovation Mining Report
📊 X potential innovations discovered this week:
1. 【Highly Recommended】A method for XXX
- Grant rate prediction: 70-80%
- Risk level: Low
- Innovation: XXX
2. 【Recommended】A system for XXX
- Grant rate prediction: 65-75%
- Risk level: Medium
- Innovation: XXX
📁 Detailed documents: /patent/weekly/
💡 Suggestion: Prioritize applying for patent #1Professional Patent Agents Suite v1.0 Author: BigPiPiHua Mail: 775262592@qq.com License: MIT Updated: 2026-03-19
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 13 other files in skills/patent-professional-agents of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Patent Professional Agents 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 Professional Agents this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~5k | 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 | 107 | 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.4k | — | ~1.1k | Automated safety check: Pass | MIT |
Yuan1z0825/nature-skills
Drafts Chinese invention patent applications and technical disclosures from research papers or inventor materials, tying each claim feature to source evidence.
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.
gfodor/legal-skills
Iteratively examine and revise a draft U.S. An agent skill from gfodor/legal-skills.
gfodor/legal-skills
Audit a draft U.S. An agent skill from gfodor/legal-skills.
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…
gfodor/legal-skills
Adversarially pressure-test a draft or pending U.S. An agent skill from gfodor/legal-skills.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Categories
📜 专利专业代理 - Patent Professional Agents 一个专业的多代理专利撰写与优化技能套件,覆盖专利申请全流程。. Patent Professional Agents is an agent skill from LeoYeAI/openclaw-master-skills.
Patent Professional Agents fits situations like: tasks that involve Intellectual property.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill patent-professional-agents -a claude-code`. Or copy the skill folder (skills/patent-professional-agents in LeoYeAI/openclaw-master-skills) into .claude/skills/patent-professional-agents in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill patent-professional-agents -a codex`. Or copy the skill folder (skills/patent-professional-agents in LeoYeAI/openclaw-master-skills) into .agents/skills/patent-professional-agents in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill patent-professional-agents -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-professional-agents, .gemini/skills/patent-professional-agents, .github/skills/patent-professional-agents and .opencode/skills/patent-professional-agents in your project.
Going by SKILL.md and its folder, Patent Professional Agents needs Python for the scripts in its folder and the command-line tools its instructions call (pip). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Patent Professional Agents is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Patent Professional Agents: Paper to Chinese Patent Drafter (Yuan1z0825/nature-skills, 47k stars), Paper To Cn Patent (snipp-zha/Paper-to-patent-Skill, 107 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.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.