wanshuiyin/auto-claude-code-research-in-sleep

prior-art-search

Search patent databases and academic literature for prior art relevant to an invention.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep --skill prior-art-search

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Prior Art Search

Search patents and literature for prior art relevant to: $ARGUMENTS

Adapted from /research-lit for patent-specific searching.

Constants

  • MAX_PATENT_RESULTS = 20 — Maximum patent documents to analyze in detail
  • MAX_PAPER_RESULTS = 15 — Maximum academic papers to analyze in detail
  • SEARCH_YEARS = 10 — How many years back to search
  • PATENT_DATABASES = "google-patents, espacenet" — Patent databases to search

Inputs

Read the invention description from:

  1. $ARGUMENTS if it contains technical details
  2. patent/INVENTION_BRIEF.md if it exists
  3. INVENTION_BRIEF.md if it exists at project root

Shared References

Load ../shared-references/prior-art-databases.md for search strategy templates and IPC/CPC classification guidance.

Workflow

Step 1: Extract Search Concepts

From the invention description, identify:

  1. Core inventive concept: The primary technical contribution (1-2 sentences)
  2. Technical problem: What problem it solves
  3. Key technical features: 4-6 specific technical elements that define the invention
  4. IPC/CPC classes: Predict relevant classification codes (e.g., G06N, G06F)

Step 2: Patent Search

For EACH search concept, search via:

Google Patents (via WebSearch):

WebSearch: "site:patents.google.com [keywords]"
WebSearch: "[keywords] patent"
  • Try primary keywords + technical problem keywords
  • Search in English regardless of target jurisdiction
  • For CN inventions, also search Chinese keywords via WebSearch

Espacenet (via WebFetch):

  • WebFetch worldwide.espacenet.com/search results for key queries
  • Search by predicted IPC/CPC classes

Assignee/Inventor Search:

  • If known companies/universities work in this area, search their patent portfolios
  • WebSearch: "[assignee name] patent [technical area]"

For each potentially relevant patent found:

  • WebFetch the patent page to extract: title, abstract, representative claims, filing date, assignee, current status
  • Record IPC/CPC classification codes

Step 3: Academic Literature Search

Search the same concepts in academic databases:

  1. Google Scholar (via WebSearch): WebSearch "[keywords] site:scholar.google.com"
  2. arXiv (via /arxiv if available, or WebSearch): Search for preprints
  3. Semantic Scholar (via /semantic-scholar if API key set, or WebSearch)

For each relevant paper found:

  • Extract title, authors, venue, year, key contribution

Step 4: Classification and Analysis

For each reference found, assess:

  1. Relevance: How closely does it relate to the invention?
  2. Overlap Risk: Does it disclose the same or similar technical solution?
  • HIGH: Anticipates one or more claim elements
  • MEDIUM: Discloses a related but different approach
  • LOW: Same general field, different approach
  1. Relationship: Is it anticipating, relevant, or merely background?

Organize results by IPC/CPC classification to see the technical landscape.

Step 5: Freedom-to-Operate Assessment (Preliminary)

Based on the search results:

  • Identify patents with claims that potentially cover the invention
  • Note any expired patents (public domain)
  • Flag areas where claim scope overlap is significant

Disclaimer: This is a preliminary assessment only. A professional freedom-to-operate analysis by a patent attorney is recommended before filing.

Step 6: Output

Write patent/PRIOR_ART_REPORT.md with:

markdown
## Prior Art Search Report

### Invention Summary
[1-2 sentence description of the searched invention]

### Search Strategy
- Keywords used: [...]
- IPC/CPC classes searched: [...]
- Databases searched: Google Patents, Espacenet, Google Scholar, arXiv
- Date range: [year] to present

### Patent References Found

| # | Patent No. | Title | Date | Assignee | IPC/CPC | Key Teaching | Overlap Risk |
|---|-----------|-------|------|----------|---------|-------------|-------------|
| 1 | CN... / US... | [title] | [date] | [assignee] | [codes] | [2-3 sentences] | HIGH/MEDIUM/LOW |

### Non-Patent Literature Found

| # | Reference | Title | Authors/Venue | Year | Key Contribution | Relevance |
|---|-----------|-------|--------------|------|-----------------|-----------|
| 1 | [DOI/link] | [title] | [authors] | [year] | [1-2 sentences] | HIGH/MEDIUM/LOW |

### Prior Art Landscape
[Organized by technical approach or IPC class, not just chronological]

### Freedom-to-Operate Preliminary Assessment
[Which existing patents might block the invention? What is the risk level?]

### Recommendations
- Suggested claim scope adjustments based on prior art
- Areas where novelty appears strongest
- References to watch during prosecution

Key Rules

  • Never fabricate patent numbers or citations. Mark uncertain references with [VERIFY].
  • Search in English AND the target jurisdiction language (Chinese for CN).
  • Patent prior art includes everything published before the priority date, not just patents.
  • Academic papers are valid prior art for both novelty and inventive step.
  • Include expired patents -- they are public domain but still relevant for novelty.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
wanshuiyin
コミュニティ

proof-checker

Rigorous mathematical proof verification and fixing workflow. Reads a LaTeX proof, identifies gaps via cross-model review (external reviewer backend, ultra reasoning), fixes each gap with full derivations, re-reviews, and generates an audit report. Use when user says "检查证明", "verify proof", "proof check", "审证明", "check this proof", or wants rigorous mathematical verification of a theory paper.

1時間の導入数
2
GitHub Stars
2万
更新日
11月19日
wanshuiyin
コミュニティ

pixel-art

Generate pixel art SVG illustrations for READMEs, docs, or slides. Use when user says "画像素图", "pixel art", "make an SVG illustration", "README hero image", or wants a cute visual.

1時間の導入数
2
GitHub Stars
1.9万
更新日
11月14日
wanshuiyin
コミュニティ

citation-crosscheck

Double-blind bibliographic cross-check: one agent extracts each cited entry verbatim from the local .bib, a second independently re-fetches the same paper's record from the web while blind to the .bib, and a third extractor emits a mechanical field-by-field delta to catch dropped/re-ordered authors, wrong years, wrong venues, and bad DOIs/arXiv ids. The main agent (never a shard) assigns the MATCH/MINOR/MISMATCH verdict per reference, and exports a side-by-side spreadsheet. Use when user says \"

1時間の導入数
1
GitHub Stars
1.9万
更新日
11月14日
wanshuiyin
コミュニティ

formula-derivation

Structures and derives research formulas when the user wants to 推导公式, build a theory line, organize assumptions, turn scattered equations into a coherent derivation, or rewrite theory notes into a paper-ready formula document. Use when the derivation target is not yet fully fixed, the main object still needs to be chosen, or the user needs a coherent derivation package rather than a finished theorem proof.

1時間の導入数
1
GitHub Stars
1.9万
更新日
11月14日