菜单
Simulate a patent examiner-style review of claims, specification, embodiments, figures, and prior-art risks without relying on local coding-assistant integration or local patent files.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission. Codex designs ablations from a reviewer's perspective, CC reviews feasibility and implements.
Analyze ML experiment results, compute statistics, generate comparison tables and insights. Use when user says "analyze results", "compare", or needs to interpret experimental data.
Draft patent claims for an invention. Use when user says "撰写权利要求", "draft claims", "写权利要求书", "claim drafting", or wants to create patent claims. The core skill of the patent pipeline.
Use Codex locally to update skills/index.json for Personal Skills MCP by reading only new or missing SKILL.md entries while preserving existing index entries.
深度学术研究与事实核查。Use when user says "深入研究", "深入核查", "深入核实", "深入检索", "深度调研", "深度研究", "deep research", "deep dive", "深入了解", "彻底调查", "全面核查", "深挖", or wants thorough multi-source literature investigation with PDF deep reading, cross-model adversarial review, and structured evidence audit. 注意：如果用户只是简单查文献/找论文/查参数，没有说"深入"或"深度"，请改用 quick-lit skill skill。本 skill 是重量级流程：文献检索 → PDF精读 → 交叉验证 → 对抗审阅 → 结构化报告。
Write detailed embodiment descriptions for patent specifications. Use when user says "撰写实施例", "write embodiment", "实施例描述", "detailed description", or wants to describe how to practice an invention.
| name | patent-review |
| title | Web-Safe Patent Review |
| description | Simulate a patent examiner-style review of claims, specification, embodiments, figures, and prior-art risks without relying on local coding-assistant integration or local patent files. |
| triggers | ["patent review","examiner review","office action","patent examiner","claims review","专利审查","审查意见","权利要求审查","新颖性","创造性","说明书"] |
Use this skill when the user wants a patent examiner-style review of patent claims, specification text, embodiments, figure descriptions, prior-art risks, clarity, enablement, or claim support.
This web-safe version does not call local coding-assistant integration, read local patent directories, search proprietary databases, or issue legal advice. It provides a structured drafting and review aid based on the material the user provides. For legal filing decisions, the user should consult a qualified patent professional.
Assess the following areas:
If the user names a jurisdiction, adapt terminology:
If jurisdiction is unknown, use general examiner-style language.
Extract:
If the user only provides an invention idea, first ask whether they want a review of draft claims or a claim-drafting-oriented review.
Create a claim chart:
| Claim element | Meaning | Support in specification | Prior-art risk | Comment |
|---|
For each independent claim, identify mandatory elements and optional elements.
Check:
Check whether the specification supports:
Flag unsupported generalizations.
If prior art is provided, compare claim elements against each reference.
If no prior art is provided, state:
Prior-art assessment is provisional because no prior-art references were provided or searched.
Then identify likely search directions and vulnerable broad features.
Suggest:
For every narrowing amendment, explain the tradeoff.
Use this format for each issue:
### Issue [N]: [Short title]
**Affected text:**
**Problem:**
**Why it matters:**
**Suggested revision:**
**Risk if unresolved:** Low / Medium / High