Patent Review

Web-side execution adapter

• This skill is workflow guidance for the ChatGPT web-side connector.
• Loading this SKILL.md is only the setup step; it does not mean the task is complete.
• After loading, continue to execute the workflow, constraints, and output format below before answering.
• Mentions of local automation, local file operations, local command execution, or external integrations are descriptive only. Use capabilities available in the current ChatGPT session, or ask the user for needed files/links.
• For literature search, current facts, factual verification, source tracing, numeric values, material properties, legal/medical/financial/current information, or any evidence-heavy claim: use available search/browsing tools first and cite verifiable sources. Do not answer such tasks only from memory.
• Preserve the original workflow and scope unless the user explicitly asks for changes.

Web-Safe Patent Review

Purpose

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.

Operating Rules

1. Do not present the output as legal advice or a formal patentability opinion.
2. Base the review on user-provided claims, specification, embodiments, figures, and cited prior art.
3. If prior art is not provided and no web search is performed, mark novelty/inventive-step conclusions as provisional.
4. Separate claim-language issues from patentability issues.
5. Identify exact claim terms that are unclear, unsupported, overly broad, or potentially anticipated.
6. Suggest amendments carefully; do not narrow claims unnecessarily without explaining the tradeoff.

Review Scope

Assess the following areas:

• claim clarity and definiteness
• antecedent basis
• support in the specification
• enablement / sufficient disclosure
• written description
• unity / single inventive concept
• novelty risk
• inventive step / obviousness risk
• claim scope strategy
• dependent claim fallback positions
• figure and reference numeral consistency

Jurisdiction Modes

If the user names a jurisdiction, adapt terminology:

• US: §101, §102, §103, §112
• EPO: novelty, inventive step, clarity, sufficiency
• CNIPA: novelty, inventiveness, practical applicability, sufficient disclosure
• General: use jurisdiction-neutral wording

If jurisdiction is unknown, use general examiner-style language.

Workflow

Step 1: Parse the application material

Extract:

• independent claims
• dependent claims
• technical field
• problem to be solved
• core inventive concept
• key technical features
• embodiments
• figure references
• known prior art
• target jurisdiction if provided

If the user only provides an invention idea, first ask whether they want a review of draft claims or a claim-drafting-oriented review.

Step 2: Claim chart

Create a claim chart:

For each independent claim, identify mandatory elements and optional elements.

Step 3: Clarity review

Check:

• unclear terms
• relative terms without criteria
• functional language without structure
• inconsistent terminology
• missing antecedent basis
• overly long claim sentences
• ambiguous dependencies
• unclear relationships among components

Step 4: Support and enablement review

Check whether the specification supports:

• the full breadth of each claim
• alternatives and variants
• functional results
• ranges, parameters, and thresholds
• software/algorithmic steps
• hardware modules
• training/data-processing procedures if relevant

Flag unsupported generalizations.

Step 5: Novelty and inventive-step risk

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.

Step 6: Amendment strategy

Suggest:

• terms to define in the specification
• claim elements that need support
• possible dependent claims
• fallback features
• clarity amendments
• scope-preserving rewrites
• optional narrowing amendments

For every narrowing amendment, explain the tradeoff.

Output Structure

1. Non-legal-advice note
2. Application summary
3. Independent claim review
4. Claim chart
5. Clarity / definiteness issues
6. Support / enablement issues
7. Novelty and inventive-step risk
8. Figure and terminology consistency
9. Suggested amendments
10. Priority action list

Examiner-Style Issue Template

Use this format for each issue:

### Issue [N]: [Short title]

**Affected text:**  
**Problem:**  
**Why it matters:**  
**Suggested revision:**  
**Risk if unresolved:** Low / Medium / High

Style Guidance

• Be precise and conservative.
• Do not overstate patentability without prior-art evidence.
• Preserve claim scope when possible.
• Use examiner-style reasoning, but keep explanations understandable.
• For Chinese patent drafting, distinguish “技术特征”, “技术问题”, “技术效果”, and “技术方案”.