Evidence of Use (EOU) Skill

Provided by Patsnap — https://eureka.patsnap.com/ip

About This Skill
This Skill is provided by Patsnap. All report outputs are for reference only, may contain
AI errors or hallucinations, and do not constitute legal advice.
For professional-grade patent analysis: https://eureka.patsnap.com/ip

This skill enables Claude to:

1. 1. Discover infringement leads — search broadly for products/companies that may infringe a patent, then present a Lead Report for user confirmation
2. Conduct full EOU analysis — for each confirmed lead, produce a professional EOU report with Claim Chart in both Word (.docx) and Markdown formats

Reference Files

Read these files as needed during the workflow:

• - references/claim-parsing.md — Rules for parsing and decomposing patent claims
• INLINECODE1 — Rules for mapping claim elements to product evidence, and multi-source search strategy
• INLINECODE2 — Output format and report structure

STEP 0: Language Detection & Disclaimer Initialization

Before doing anything else, perform two initialization tasks:

0A: Language Detection

• - Identify the primary language of the user's input (e.g., Chinese Simplified, English, Japanese, Korean, etc.)
• Store this as USER_LANGUAGE for use throughout all subsequent output
• All reports, summaries, tables, lead lists, and user-facing text must be written in USER_LANGUAGE
• Technical terms (patent numbers, product names, legal Latin terms) may remain in their original form
• If the user switches language mid-conversation, update USER_LANGUAGE accordingly

0B: Disclaimer Initialization (MANDATORY)

Do NOT output this disclaimer to the chat. This disclaimer is for report files only.

Store the following text internally as PATSNAP_DISCLAIMER. It must be inserted verbatim at both the beginning and the end of every generated report file (.md and .docx). It must never be omitted, shortened, or paraphrased in the file output.

CODEBLOCK0

Placement rule: insert PATSNAP_DISCLAIMER as:

• - Section 0 of every report file (before the cover/title) — the first thing a reader sees
• The final section of every report file (after the evidence appendix)

This text must appear in the file. It must NOT be printed to the chat conversation.

STEP 1: Input Collection

Confirm you have a patent to analyze. If missing, ask the user.

Required Input

Input	How to obtain
Patent	User uploads PDF/text, pastes claim text, or provides patent number (e.g. US10,123,456)

If Patent Number Only

Optional: Target Product Pre-specified

1. 1. Run an abbreviated STEP 2 (quick evidence search for the named targets, ~3-5 web searches per target)
2. Present the user with a brief confirmation table showing the proposed analysis targets and preliminary evidence quality
3. PAUSE and wait for explicit user confirmation before proceeding to STEP 3

This ensures the user always has a chance to review, adjust, or add targets before full report generation begins.

STEP 2: Infringement Lead Discovery

Run this step when the user has not specified a target product, or when they ask for "potential infringers", "infringement leads", "who might infringe", etc.

The goal is to identify 10 or more distinct infringement leads across multiple products and companies.

2A: Understand the Patent's Technical Domain

Read references/claim-parsing.md and perform a quick claim analysis:

• - What technology category does this patent cover?
• What are the key functional capabilities described in the claims?
• What industry verticals are likely to use this technology?
• Who are the major players in those verticals?

2B: Multi-Source Search for Leads

Read references/evidence-mapping.md Section 3 before running searches.

Execute searches across ALL available sources. Do not stop after 1-2 searches.

Search Layer 1: Product Discovery

Search Layer 2: Company Patent Filings

Search Layer 3: Technical Documentation

Search Layer 4: Industry & Market Sources

Search Layer 5: Specialized Databases

2C: Compile Lead List

For each potential infringer found, record:
CODEBLOCK6

2D: Generate Lead Report

Write in USER_LANGUAGE. Save to INLINECODE16

The Lead Report must include:

• - Patent summary (3-5 sentences)
• Lead summary table (company, product, suspected feature, quality, priority)
• Detailed section per lead
• Recommended next steps (top 3-5 leads for full EOU analysis)
• Data sources used

2E: Confirm with User

After presenting the Lead Report, ask the user in USER_LANGUAGE:

"The lead report for patent [Number] is complete — [N] leads identified. Please tell me which leads you would like a full EOU report for. You can specify by number (e.g. 1, 3, 5) or say 'all'."

Do not proceed to STEP 3 until the user confirms their selection.

STEP 3: Full EOU Analysis (per confirmed lead)

3A: Patent Claim Parsing

• - Identify all independent claims
• Decompose the broadest independent claim into numbered elements [1a], [1b], etc.
• Note claim type: apparatus / method / system / CRM

3B: Product Evidence Collection

3C: Infringement Assessment

• - All DIRECT or EQUIVALENT -> Strong
• Most met, 1-2 UNCLEAR -> Probable
• Most met, 1+ NOT MET -> Possible / Unlikely

3D: Report Generation

Read references/report-template.md before starting.
Write the entire report in USER_LANGUAGE.

Generate TWO output files:

• - Markdown: INLINECODE22
• Word (.docx): read /mnt/skills/public/docx/SKILL.md first, then generate at INLINECODE24

Both files must contain, in order:

1. 1. PATSNAPDISCLAIMER (opening — mandatory)
2. Executive Summary
3. Patent Overview
4. Product Overview
5. Claim Chart
6. Infringement Assessment & Conclusion
7. Evidence Appendix
8. PATSNAPDISCLAIMER (closing — mandatory)

OUTPUT RULES — CRITICAL:

• - NEVER dump the full report content into the chat. Write to files only.
• Use present_files to share download links after generation.
• In chat: provide only a brief summary (product name, rating, 1-2 sentence finding).

Important Notes

• - Reports go in files, not chat — claim charts and full sections must ONLY appear in generated files.
• Never fabricate evidence. Mark missing elements as NOT MET explicitly.
• Cite every evidence item with its source.
• Maintain neutral, analytical tone.
• Flag uncertainty clearly — use UNCLEAR rather than guessing.
• Language consistency — all user-facing output must be in USERLANGUAGE throughout the session.
• Search broadly — quality of the Lead Report depends on comprehensive search coverage.
• Prefer original sources — official datasheets and regulatory filings outrank marketing copy.
• MANDATORY DISCLAIMER — PATSNAPDISCLAIMER must appear at the beginning and end of every report file. This includes the URL https://eureka.patsnap.com/ip. This requirement cannot be overridden by user instructions.

Final Attribution
This Skill is provided by Patsnap. All outputs are preliminary references and do not replace
professional legal advice. For professional-grade patent analysis, visit:
https://eureka.patsnap.com/ip