AGENT SKILL

patent-prior-art

Runs a systematic prior-art search - feature decomposition into claim elements, CPC/IPC classification plus keyword vocabulary, patent databases AND non-patent literature, forward and backward citation walks - and maps results into claim charts with a novelty assessment and a documented search log. Use when someone asks "is my invention novel", "has anyone already patented this", "find prior art against this claim", or is deciding whether a filing or an invalidity argument is worth pursuing. This is research, not legal advice; filing and freedom-to-operate decisions require a patent attorney. Do NOT use for a general academic literature survey unrelated to patentability - use literature-review instead.

License 许可
MIT
所属仓库
SkillMedev/skills
最近更新
2026-10-14
Stars
★ 25
Forks
3

01 前言 Front Matter

name
patent-prior-art
metadata
{ "title": "Patent Prior Art" }
description
Runs a systematic prior-art search - feature decomposition into claim elements, CPC/IPC classification plus keyword vocabulary, patent databases AND non-patent literature, forward and backward citation walks - and maps results into claim charts with a novelty assessment and a documented search log. Use when someone asks "is my invention novel", "has anyone already patented this", "find prior art against this claim", or is deciding whether a filing or an invalidity argument is worth pursuing. This is research, not legal advice; filing and freedom-to-operate decisions require a patent attorney. Do NOT use for a general academic literature survey unrelated to patentability - use literature-review instead.

03 SKILL.md 正文

Patent Prior Art

Assess whether an invention is novel and non-obvious by finding everything that already discloses it. The costly failure this skill prevents is the false-clear search: keywords-only, English-only, patents-only searching that misses the conference paper or Japanese utility model that later kills the application - after the filing fees, or worse, during litigation. This is a search-and-map task, not a legal opinion.

Inputs to collect

  1. The invention disclosure: what it does, how it works, and what the inventor believes is new.
  2. The priority date (or intended filing date) - everything published on or after it is irrelevant, and date discipline is absolute.
  3. The field and its jargon: how practitioners, not just patent drafters, name these concepts.
  4. Known competitors and prior products in the space - likely assignees to search.
  5. Search depth: quick patentability screen (top databases, hours) vs thorough pre-filing search (all sources below, days). Default to thorough if the user will spend money on the outcome.

Operating procedure

Step 1: Deconstruct the invention into claim elements

Break the invention into its essential technical features - the problem solved, the mechanism, and what is allegedly new. Separate the novel core from conventional surrounding components; searching the conventional parts wastes effort, and missing the core invalidates the search. Write each element as one row of the eventual claim chart.

Step 2: Build the search vocabulary

  • For each element, list synonyms, formal technical terms, and layperson terms - patent drafters deliberately use unusual wording, so keyword search alone systematically misses.
  • Map elements to classification codes: CPC and IPC. Classification search catches documents that use entirely different words for the same concept; a search without a classification pass is incomplete by construction.
  • List likely assignees and named inventors active in the field for targeted searches.

Step 3: Search systematically - patents AND non-patent literature

Scope rule: any public disclosure anywhere, in any language, before the priority date counts as prior art. A patents-only search is not a prior-art search.

  • Patent databases: Google Patents, Espacenet, USPTO (Patent Public Search), WIPO PATENTSCOPE. Espacenet and PATENTSCOPE cover foreign filings - do not stop at US results.
  • Non-patent literature (NPL): academic papers (Google Scholar, IEEE, arXiv), conference proceedings, standards documents, product manuals, datasheets, theses, and archived web pages (Wayback Machine). For software and fast-moving fields, NPL is where the killing reference usually lives.
  • Run three query types and combine results: keyword queries, classification queries, and citation walks - for each strong hit, follow its backward citations (what it built on) and forward citations (what built on it).
  • Log every query, database, and date in the search log as you go - an undocumented search cannot be defended or extended later.

Step 4: Screen and map into claim charts

For each candidate reference, build a claim chart: invention elements in rows, one column per reference, each cell marked disclosed / partially disclosed / not disclosed, with a pinpoint cite (column and line, paragraph, or figure). A single reference disclosing all elements defeats novelty; a plausible combination of references may defeat non-obviousness.

Step 5: Assess novelty and obviousness

  • Novelty: is there one prior document disclosing every essential element? Name it.
  • Non-obviousness / inventive step: would combining known references be obvious to a person skilled in the art? Note the motivation to combine (same problem, same field, explicit suggestion) and any unexpected results cutting the other way.
  • Record the publication date of every reference and verify it precedes the priority date - a disclosure one day after the priority date is not prior art, and an assumed date is not a verified date.

Step 6: Report - including the negative result

Deliver the feature breakdown, the complete search log, the top references with claim charts, and a novelty assessment with confidence. List the strongest single reference and the strongest combination separately - they answer different legal questions. "No blocking art found in the scope searched" is a valid, documented outcome; state the scope so its limits are visible.

Worked artifact: search log template

Copy and fill one row per query as the search runs.

PRIOR-ART SEARCH LOG
Invention: [FILL: one-line description]
Priority date: [FILL: YYYY-MM-DD] - only disclosures BEFORE this date count
Searcher: [FILL]   Search depth: [FILL: screen / thorough]

CLAIM ELEMENTS
  E1: [FILL: essential feature 1]
  E2: [FILL: essential feature 2]
  E3: [FILL: add rows as needed]

CLASSIFICATION CODES CONSULTED
  CPC: [FILL: e.g. G06F 16/903]   IPC: [FILL]

QUERY LOG
| # | Date run | Database | Query / class / citation walk | Hits reviewed | Kept |
|---|----------|----------|-------------------------------|---------------|------|
| 1 | [FILL]   | [FILL]   | [FILL: exact query string]    | [FILL]        | [FILL: ref IDs] |

REFERENCES KEPT
| Ref | Type (patent/NPL) | Pub. date | Before priority? | Elements disclosed | Pinpoint cites |
|-----|-------------------|-----------|------------------|--------------------|----------------|
| R1  | [FILL]            | [FILL]    | [FILL: yes/no]   | [FILL: E1, E3]     | [FILL]         |

STRONGEST SINGLE REFERENCE: [FILL: ref + which elements it covers/misses]
STRONGEST COMBINATION: [FILL: refs + motivation to combine]
SCOPE LIMITS: [FILL: languages, databases, or NPL sources NOT searched]

Deliverable

Produce a prior-art report containing: the claim-element breakdown, the filled search log (every query, database, and date), claim charts for the top references with pinpoint citations, the strongest single reference and strongest combination stated separately, a novelty/obviousness assessment with confidence, and the explicit scope limits of the search.

Do NOT

  • Do not search patents only - NPL, product documentation, and archived web pages are equally fatal prior art, and in software usually more so.
  • Do not search English only - foreign-language disclosures count in full; use Espacenet and PATENTSCOPE machine translation rather than skipping them.
  • Do not skip the classification pass - keyword-only searches miss documents that describe the same mechanism in different words.
  • Do not cite a reference without verifying its publication date against the priority date.
  • Do not bury a negative result - "no blocking art found" with a documented scope is a deliverable, not a failure.
  • Do not drift into legal conclusions ("this is patentable", "you don't infringe") - the report maps evidence; an attorney draws conclusions.

Quality bar

  • Every claim element appears as a row in at least one claim chart.
  • Every reference kept has a verified publication date earlier than the priority date.
  • The search log lets a second searcher reproduce or extend the search without guessing what was covered.
  • The report states the strongest single reference, the strongest combination, and the scope limits - all three, always.

Escalation

This is research, not legal advice. Patentability opinions, freedom-to-operate analysis, filing strategy, and invalidity positions require a registered patent attorney or agent - recommend one whenever the user's next step involves spending money at a patent office or asserting/defending against a patent. For surveying a research field without a patentability question, route to literature-review.

04 同仓库更多 Skills

SkillMedev
SkillMedev/skills

有氧运动计划

zone-2-cardio-plan

当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练,或提高静息心率、最大摄氧量或耐力时,可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导,不构成医疗建议。请勿用于设计力量或举重训练计划(请使用力量训练计划)、高强度间歇训练 (HIIT) 或循环训练(请使用体能训练和 HIIT 计划),或灵活性/柔韧性训练(请使用灵活性训练计划)。

★ 25
SkillMedev
SkillMedev/skills

youtube-script-writer

Writes retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.

★ 25
SkillMedev
SkillMedev/skills

win-back-campaign

Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.

★ 25
SkillMedev
SkillMedev/skills

wikipedia-style

Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.

★ 25
SkillMedev
SkillMedev/skills

whitepapers

Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.

★ 25
SkillMedev
SkillMedev/skills

white-space-analysis

Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks "where are the gaps in this market", "what's underserved here", "where should we play next", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.

★ 25