SuperAPI AI Directory

patent-chart

Writing & research

View repository

Updated 11-02 05:01

About this skill

Claim Comparison Chart

Purpose

Break the independent claim (by default also the dependent claims) into technical features and compare them cell by cell against prior-art documents / products / standards, attaching evidence and strength ratings. Used for invalidity comparisons, FTO preliminary screening, infringement/EoU, SEP, patentability, and examination-response rejection mapping. This package only fills in the matrix and exports it. The left column of features, the right column of original text, and supplementary search hits are produced by the interpretation package / search package.

When to use

Must be named by the user (comparison chart / claim chart / invalidity comparison / FTO preliminary screening / infringement comparison / /patent-chart)。

Input

The left column must have publication number / PDF / claims / claim_features.json / disclosure 5.1. Materials are collected in the conversation (prompts/intake.md first --alloc); if the three-piece set is incomplete, only ask questions. If not enough, ask questions; only after it is complete and INTAKE_OK:1 is done, analyze and write intake.json。

Steps

First Read prompts/guardrails.md, then Read prompts/intake.md。

Dispatch must first Read the other party SKILL.md, then run according to its processthat package tools/. When the interpretation package is dispatched by the comparison chart: if Obsidian is not ready, degrade to outputs/patent_reader/; by default also break the dependent claims into claim_features.json。

  1. prompts/guardrails.md → intake.md(first --alloc; if the three-piece set is incomplete, only ask questions. Only after it is complete and INTAKE_OK:1 is done, analyze)
  2. Missing claim_features.json or the compared patent's description_paragraphs.json → Read skills/patent-reader/SKILL.md. The comparison chart only needs these two documents (dependent claims are also broken into feature rows). Do not write plain-language notes, do not enter the database, do not adjudicate drawings. For full-text PDF use the interpretation package fetch_patent_pdf.py. If it cannot be downloaded, ask the user for the PDF.
  3. If the user allows supplementary D and there are empty cells → Read skills/patent-search/SKILL.md, then according to its covers_rank.md produce a bypass
  4. prompts/fill_chart.md fill in the cells (same color across columns, written correspondence explanation, complete excerpts)
  5. python skills/patent-chart/tools/emit_chart.py --json <payload.json> --into <INTAKE_DIR>
  6. Delivery end block Read prompts/delivery_confirm.md

Guardrails

  • Detailed rules prompts/guardrails.md。

Deliverables

outputs/patent-chart/{案件}/{会话}/:intake.json(archive of this round's input) + 对照表-{场景}-{时间戳}.xlsx(main deliverable) + chart.json(machine-readable working paper). The xlsx fixedly contains Overview / Comparison Chart / Details / Legend;invalidity add "Path Memo",fto add "Risk List",infringement add "Evidence Gaps",oa add "Rejection Mapping". Conversation end block title After delivery, please confirm。