search-prior-art
정보
이 스킬은 발명과 관련된 선행기술을 찾기 위해 특허 및 비특허 문헌을 검색합니다. 특허의 신규성 평가, 특허 유효성에 대한 이의 제기, 사업 자유 운영(FTO) 분석 지원, 또는 특허청 심사 통지에 대한 답변 작성에 사용됩니다. 이 스킬은 학술 논문, 제품, 오픈 소스, 방어적 공개 문서, 표준 필수 특허를 검색할 수 있습니다.
빠른 설치
Claude Code
추천npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/search-prior-artClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
先行技術の調査
Conduct a structured prior art search to find publications, patents, products, or disclosures that predate a specific invention. Used to assess patentability (can this be patented?), challenge validity (should this patent have been granted?), or establish freedom-to-operate (is this design covered by existing rights?).
使用タイミング
- Evaluating whether an invention is novel and non-obvious before filing a patent application
- Challenging the validity of an existing patent by finding prior art the examiner missed
- Supporting a freedom-to-operate analysis by finding prior art that limits a blocking patent's scope
- Documenting a defensive publication to prevent others from patenting a concept
- Responding to a patent office action that questions novelty or obviousness
入力
- 必須: Invention description (what it does, how it works, what problem it solves)
- 必須: Search purpose (patentability, invalidity, FTO, defensive)
- 必須: Critical date (filing date of the patent application, or invention date for prior art)
- 任意: Known related patents or publications
- 任意: Technology classification codes (IPC, CPC)
- 任意: Key inventors or companies in the field
手順
ステップ1: Decompose the Invention into Searchable Elements
Break the invention into its constituent technical features.
- Read the invention description (or patent claims if searching against an existing patent)
- Extract the essential elements — each independent technical feature:
- What components does it have?
- What steps does the process follow?
- What technical effect does it achieve?
- What problem does it solve and how?
- Identify the novel combination — what makes this different from the known art:
- Is it a new element added to known elements?
- Is it a new combination of known elements?
- Is it a known element applied in a new field?
- Generate search terms for each element:
- Technical terms, synonyms, and abbreviations
- Broader and narrower terms (hierarchy)
- Alternative descriptions of the same concept
- Document the Search Map: elements, terms, and relationships
Search Map Example:
+------------------+-----------------------------------+-----------+
| Element | Search Terms | Priority |
+------------------+-----------------------------------+-----------+
| Attention layer | attention mechanism, self- | High |
| | attention, multi-head attention | |
| Sparse routing | mixture of experts, sparse MoE, | High |
| | top-k routing, expert selection | |
| Training method | knowledge distillation, teacher- | Medium |
| | student, progressive training | |
+------------------+-----------------------------------+-----------+
期待結果: A complete decomposition with search terms for each element. The novel combination is identified — this is what the search must either find (to invalidate) or confirm is absent (to support novelty).
失敗時: If the invention is too abstract to decompose, ask for a more specific description. If the claims are unclear, focus on the broadest reasonable interpretation of each claim element.
ステップ2: Search Patent Literature
Search patent databases systematically.
- Construct queries combining element terms:
- Search each element individually first (broad)
- Then combine elements to find closer art (narrow)
- Use classification codes to filter by technology area
- Search multiple databases:
- Google Patents: Good for full-text search, free, large corpus
- USPTO PatFT/AppFT: US patents and applications, official source
- Espacenet: European patents, excellent classification search
- WIPO Patentscope: PCT applications, global coverage
- Apply date filters:
- Prior art must predate the critical date (filing date or priority date)
- Include publications up to 1 year before filing (grace period varies by jurisdiction)
- For each relevant result, record:
- Document number, title, filing date, publication date
- Which elements it discloses (map to Search Map)
- Whether it discloses the novel combination
- Classify results by relevance:
- X reference: Discloses the invention alone (anticipation)
- Y reference: Discloses key elements, combinable with other references (obviousness)
- A reference: Background art, defines the general state of the art
期待結果: A classified list of patent references mapped to the invention's elements. X references (if found) are showstoppers for novelty. Y references are the building blocks for obviousness arguments.
失敗時: If no relevant patent art is found, this doesn't mean the invention is novel — non-patent literature (Step 3) may contain the critical reference. Absence in one database doesn't mean absence everywhere.
ステップ3: Search Non-Patent Literature
Search academic papers, products, open source, and other non-patent disclosures.
- Academic literature:
- Google Scholar, arXiv, IEEE Xplore, ACM Digital Library
- Search using the same terms from Step 1
- Conference papers and workshop proceedings often predate patent filings
- Products and commercial disclosures:
- Product documentation, user manuals, marketing materials
- Internet Archive (Wayback Machine) for date-verified web content
- Trade publications and press releases
- Open source and code:
- GitHub, GitLab — search for implementations of the technical features
- README files, documentation, and commit histories for date evidence
- Software releases with version dates
- Standards and specifications:
- IEEE, IETF (RFCs), W3C, ISO standards
- Standards-essential patents must be disclosed; search standard bodies' IP databases
- Defensive publications:
- IBM Technical Disclosure Bulletin
- Research Disclosure journal
- IP.com Prior Art Database
- For each result, verify the publication date is before the critical date:
- Web pages: use Wayback Machine for date evidence
- Software: use release dates or commit timestamps
- Papers: use publication date, not submission date
期待結果: Non-patent references that complement the patent search. Academic papers and open-source code are often the most powerful prior art because they tend to describe technical details more explicitly than patents.
失敗時: If non-patent literature is sparse, the technology may be primarily developed in corporate R&D (patent-heavy). Shift emphasis to patent literature and focus on the combination-based obviousness argument.
ステップ4: Analyze and Map Results
Evaluate how the collected prior art relates to the invention.
- Create a claim chart mapping prior art to invention elements:
Claim Element vs. Prior Art Matrix:
+------------------+--------+--------+--------+--------+
| Element | Ref #1 | Ref #2 | Ref #3 | Ref #4 |
+------------------+--------+--------+--------+--------+
| Element A | X | X | | X |
| Element B | | X | X | |
| Element C | X | | X | |
| Novel combo A+B+C| | | | |
+------------------+--------+--------+--------+--------+
X = element disclosed in this reference
- Assess novelty: Does any single reference disclose all elements?
- If yes → invention is anticipated (not novel)
- If no → invention may be novel (proceed to obviousness)
- Assess obviousness: Can a small number of references (2-3) be combined to cover all elements?
- Is there motivation to combine? (would a skilled person see a reason to combine these?)
- Do the references teach away from the combination? (suggest it wouldn't work?)
- For FTO searches: Does the prior art narrow the blocking patent's claims?
- Prior art that overlaps with the blocking patent's claims limits their enforceable scope
- Document the analysis clearly with citation to specific passages
期待結果: A clear claim chart showing which elements are covered by which references, with an assessment of novelty and obviousness. Each mapping cites specific passages or figures in the references.
失敗時: If the claim chart shows gaps (elements not found in any prior art), those gaps represent the potentially novel aspects. Focus follow-up searches on those specific gaps.
ステップ5: Document and Deliver
Package the search results for their intended use.
- Write the Prior Art Search Report:
- Purpose and scope of the search
- Search methodology (databases, queries, date ranges)
- Results summary (number of references found, classification breakdown)
- Top references with detailed analysis (claim charts)
- Assessment: novelty, obviousness, and FTO implications
- Limitations and recommendations for further search
- Organize references:
- Sorted by relevance (X references first, then Y, then A)
- Each reference with full bibliographic data and access link
- Key passages highlighted or extracted
- Recommendations based on search purpose:
- Patentability: File/don't file, suggested claim scope based on prior art gaps
- Invalidity: Strongest combination of references, suggested legal argument
- FTO: Risk level, design-around opportunities, licensing considerations
- Defensive: Whether to publish as defensive disclosure based on white space found
期待結果: A complete, well-organized search report that directly supports the intended decision. References are accessible and analysis is traceable.
失敗時: If the search is inconclusive (no strong X or Y references, but some relevant background), state the conclusion clearly: "No anticipatory art found; closest art addresses elements A and B but not C. Recommend filing with claims emphasizing element C." Inconclusive is a valid and useful result.
バリデーション Checklist
- Invention decomposed into distinct searchable elements
- Novel combination explicitly identified
- Patent databases searched (minimum 2 databases)
- Non-patent literature searched (academic + products + open source)
- All references predate the critical date (dates verified)
- Claim chart maps elements to references with passage citations
- Novelty and obviousness assessed with reasoning
- Results classified by relevance (X, Y, A references)
- Report includes methodology, limitations, and recommendations
- Search is reproducible (queries and databases documented)
よくある落とし穴
- Keyword tunnel vision: Searching only exact terms misses synonyms and alternative descriptions. Use the term hierarchy from Step 1
- Patent-only search: Non-patent literature (papers, products, code) is often more explicit than patents. Don't skip Step 3
- Date carelessness: Prior art must predate the critical date. A brilliant reference from one day after the filing date is worthless
- Ignoring foreign language art: Major inventions may first appear in Chinese, Japanese, Korean, or German patent literature. Machine translation makes these searchable
- Confirmation bias: Searching to confirm novelty rather than searching to find invalidating art. The best search tries hardest to find the closest art
- Stopping too early: The first few results are rarely the best. Iterate search terms based on what early results reveal about the field's vocabulary
関連スキル
assess-ip-landscape— Broader landscape mapping that contextualizes specific prior art searchesreview-research— Literature review methodology overlaps significantly with prior art searchsecurity-audit-codebase— Systematic search methodology parallels (thoroughness, documentation, reproducibility)screen-trademark— IP ランドスケープの商標側のための商標競合スクリーニングと識別力分析file-trademark— EUIPO、USPTO、およびマドリッドプロトコルの商標出願手続き
GitHub 저장소
연관 스킬
executing-plans
디자인executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
requesting-code-review
디자인이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
connect-mcp-server
디자인이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
web-cli-teleport
디자인이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
