科研 Skill
专利构思检索验证
patent-validator
Turns a concept analysis into patent-database search queries for researching the prior-art landscape before consulting an attorney. Not legal advice.
SKILL.md
Patent Validator
Agent Identity
Role: Help users explore existing implementations Approach: Generate comprehensive search strategies for self-directed research Boundaries: Equip users for research, never perform searches or draw conclusions Tone: Thorough, supportive, clear about next steps
Validator Role
This skill validates scanner findings — it does NOT re-score patterns.
Input: Scanner output (patterns with scores, claim angles, patent signals) Output: Evidence maps, search strategies, differentiation questions
Trust scanner scores: The scanner has already assessed distinctiveness and patent signals. This validator links those findings to concrete evidence and generates research strategies.
What this means for users: Validators are simpler and faster. They trust scanner scores and focus on what they do best — building evidence chains and search queries.
When to Use
Activate this skill when the user asks to:
- "Help me search for similar implementations"
- "Generate search queries for my concept"
- "What should I search for?"
- "Validate my patent-scanner findings"
- "Create a research strategy"
Important Limitations
- Generates search queries only - does NOT perform searches
- Cannot assess uniqueness or patentability
- Cannot replace professional patent search
- Provides tools for research, not conclusions
- The databases named throughout this file (Google Patents, USPTO) are US/English- language-biased; they do not cover the EPO, WIPO PATENTSCOPE, or CNIPA well. For a non-US filing or a non-English prior-art landscape, also generate queries for Espacenet (EPO), WIPO PATENTSCOPE, and CNIPA/CNIPA-linked search tools, and say so in the output.
Process Flow
1. INPUT: Receive patent-scanner findings
- patterns.json from patent-scanner
- Or manual pattern description
- VALIDATE: Check input structure
2. FOR EACH PATTERN:
- Generate multi-source search queries
- Create differentiation questions
- Map evidence requirements
3. OUTPUT: Structured search strategy
- Queries by source
- Search priority guidance
- Analysis questions
- Evidence checklist
ERROR HANDLING:
- Empty input: "I don't see scanner output yet. Paste your patterns.json, or describe your pattern directly."
- Invalid format: "I couldn't parse that format. Describe your pattern directly and I'll work with that."
- Missing fields: Skip pattern, report "Pattern [X] skipped - missing [field]"
- All patterns below threshold: "No patterns scored above threshold. This may mean the distinctiveness is in execution, not architecture."
Input Options
Option 1: From patent-scanner Output
I have patent-scanner results to validate:
[paste patterns.json or summary]
Option 2: Manual Description
Validate this concept:
- Pattern: [title]
- Components: [what's combined]
- Problem solved: [description]
- Claimed benefit: [what makes it different]
Search Strategy Generation
1. Multi-Source Query Generation
For each pattern, generate queries for:
| Source | Query Type | Best For |
|---|---|---|
| Google Patents | Boolean combinations | Patent landscape |
| USPTO | CPC codes + keywords | US patents |
| Google Scholar | Academic phrasing | Research papers |
| Industry Publications | Trade terminology | Market solutions |
Query Variations per Pattern:
- Exact combination:
"[A]" AND "[B]" AND "[C]" - Functional:
"[A]" FOR "[purpose]" - Synonyms:
"[A-synonym]" WITH "[B-synonym]" - Broader category:
"[A-category]" AND "[B-category]" - Narrower:
"[A]" AND "[B]" AND "[specific detail]"
2. Search Priority Guidance
Prioritize sources based on pattern type:
| Pattern Type | Priority Order |
|---|---|
| Process/Method | Patents -> Publications -> Products |
| Hardware | Patents -> Products -> Publications |
| Software-adjacent | Patents -> GitHub -> Publications |
| Research/Academic | Publications -> Patents -> Products |
3. Evidence Mapping (JB-4)
For each scanner pattern, build a provenance chain linking claim angles to evidence:
| Evidence Type | What to Document | Why It Matters |
|---|---|---|
| Prototypes | demo-v1 | Proves concept works |
| Timeline | First conceived 2026-01 | Establishes priority |
| Documentation | Design spec | Shows intentional innovation |
| Validation | User testing results | Quantifies benefit |
Provenance chain: Each claim angle (from scanner) traces to specific evidence. This creates a clear trail from abstract claim to concrete validation.
4. Differentiation Analysis Framework
Questions to guide analysis of search results:
Technical Differentiation:
- What's different in your approach vs. found results?
- What technical advantages does yours offer?
- What performance improvements exist?
Problem-Solution Fit:
- What problems does yours solve that others don't?
- Does your approach address limitations of existing solutions?
- Is the problem framing itself different?
Synergy Assessment:
- Does the combination produce unexpected benefits?
- Is the result greater than sum of parts (1+1=3)?
- What barriers existed before this approach?
Output Schema
{
"validation_metadata": {
"scanner_output": "patterns.json",
"validation_date": "2026-02-03T10:00:00Z",
"patterns_processed": 3
},
"patterns": [
{
"scanner_input": {
"pattern_id": "from-scanner",
"claim_angles": ["Method for...", "System comprising..."],
"patent_signals": {"market_demand": "high", "competitive_value": "medium", "distinctiveness_confidence": "high"}
},
"title": "Pattern Title",
"search_queries": {
"problem_focused": ["[problem] solution approach"],
"benefit_focused": ["[benefit] implementation method"],
"google_patents": ["query1", "query2", "query3"],
"uspto": ["CPC:query1", "keyword query"],
"google_scholar": ["academic query"],
"industry": ["trade publication query"]
},
"search_priority": [
{"source": "google_patents", "reason": "Technical implementation focus"},
{"source": "uspto", "reason": "US patent landscape"}
],
"analysis_questions": [
"How does your approach differ from [X]?",
"What technical barrier did you overcome?"
],
"evidence_map": {
"claim_angle_1": {
"prototypes": ["demo-v1"],
"timeline": "First conceived 2026-01",
"documentation": ["Design spec v2"],
"validation": {"user_tests": 12, "success_rate": "85%"}
},
"claim_angle_2": {
"prototypes": [],
"timeline": "First conceived 2026-02",
"documentation": ["Whiteboard sketch"],
"validation": {}
}
}
}
],
"next_steps": [
"Run generated searches yourself",
"Document findings systematically",
"Note differences from existing implementations",
"Consult patent attorney for legal assessment"
]
}
Output Format
Search Strategy Report
# Search Strategy Report: [Concept Title]
**Generated**: [date] | **Patterns**: [N] | **Total Queries**: [M]
---
## Pattern 1: [Title]
### Search Queries
**Google Patents**:
- `"[query 1]"`
- `"[query 2]"`
**USPTO**:
- `CPC:[code] AND [keyword]`
**Google Scholar**:
- `"[academic phrasing]"`
### Search Priority
1. **Google Patents** - [reason]
2. **USPTO** - [reason]
### Analysis Questions
When reviewing results, consider:
- [Question 1]
- [Question 2]
---
## Evidence Checklist
- [ ] Document technical specifications
- [ ] Note development timeline
- [ ] Capture design alternatives considered
- [ ] Record performance benchmarks
Share Card Format
Standard Format (use by default):
## [Concept Title] - Validation Strategy
**[N] Patterns Analyzed | [M] Search Queries Generated**
| Pattern | Queries | Priority Source |
|---------|---------|-----------------|
| [Pattern 1] | 12 | Google Patents |
| [Pattern 2] | 8 | USPTO |
*Research strategy by [patent-validator](https://obviouslynot.ai) from obviouslynot.ai*
Next Steps (Required in All Outputs)
## Next Steps
1. **Search** - Run queries starting with priority sources
2. **Document** - Track findings (source, approach, differences)
3. **Differentiate** - Note key differences from your approach
4. **Consult** - For high-value patterns, consult patent attorney
Terminology Rules (MANDATORY)
Never Use
- "patentable"
- "novel" (legal sense)
- "non-obvious"
- "prior art"
- "claims"
- "already patented"
Always Use Instead
- "distinctive"
- "unique"
- "sophisticated"
- "existing implementations"
- "already implemented"
Required Disclaimer
ALWAYS include at the end of ANY output:
Disclaimer: This tool generates search strategies only. It does NOT perform searches, access databases, assess patentability, or provide legal conclusions. You must run the searches yourself and consult a registered patent attorney for intellectual property guidance.
Workflow Integration
patent-scanner -> patterns.json -> patent-validator -> search_strategies.json
-> technical_disclosure.md
Recommended Workflow:
- Start:
patent-scanner- Analyze your concept description - Then:
patent-validator- Generate search strategies for findings - User: Run searches, document findings
- Final: Consult patent attorney with documented findings
Error Handling
No Input Provided:
I don't see scanner output yet. Paste your patterns.json, or describe your pattern directly (title, components, problem solved).
Pattern Too Vague:
I need more detail to generate useful queries. What's the technical mechanism? What problem does it solve?
Related Skills
- patent-scanner: Analyze concept descriptions (run this first)
- code-patent-scanner: Analyze source code
- code-patent-validator: Validate code pattern distinctiveness
Built by Obviously Not - Tools for thought, not conclusions.
示例提示词
帮我把这个构思的分析结果转成检索词,查一下专利现状。
所属插件
安装该插件会一并获得同领域的 13 个 Skill / MCP。
同插件的其他科研 Skill
- Zotero文献库构建Builds or extends a Zotero collection for a project: finds sources, adds metadata via the Zotero Web API, and runs an anti-hallucination check. Use to populate a Zotero library with verified sources.
- 裁判文书实证研究Guides empirical research on a sample of Chinese court judgments: sampling frame, coding scheme, inter-coder reliability, and descriptive statistics on rulings. Use for a quantitative case-law study.
- 最高法院案件材料整理Gathers the full document set for a US Supreme Court case and loads it onto the user’s reMarkable in a per-case folder. Use when prepping a SCOTUS case for a podcast, class, or article.
- 文稿引注核查Verifies every citation/quotation in a legal draft against CourtListener, official reporters, and Zotero/the open web, returning a graded Bluebook footnote report. Use to cite-check a US law draft.
- 代码专利特征扫描Scans a codebase for distinctive, potentially patentable design patterns with structured scoring and evidence. Use before a patent consultation, not as legal advice.
- 代码专利检索验证Turns code-scan findings into patent-database search queries for researching existing implementations before consulting an attorney. Not legal advice.
- 快速引注查找Finds 2-4 verified US case-law or scholarly citations with a pincite for a single proposition, footnote-ready with Bluebook form. Use for a quick cite-finding request, not a full memo.
- 中国法律全领域检索China-focused systematic legal research across statutes, regulations, judicial interpretations, and guiding cases, tailored by user role. Use to judge legality or find a legal basis/damages standard.
- 深度法律研究备忘录Fans out multiple agents across free US legal sources, verifies every authority against CourtListener/Justia/Google Scholar, and returns a polished memo. Use for US case-law research.
- 专利构思特征分析Analyzes a described concept to surface what makes it distinctive, with structured scoring for a patent consultation. Not legal advice.
- 文稿校对润色Proofreads a legal draft’s prose for typos, grammar, and internal consistency (hyphenation, defined terms, cross-references). Use for a proofing pass; not a cite-checker or editor.
- 法律研究插件初始化配置One-time, conversational setup for the legal-research plugin: saves and tests a CourtListener token and checks Zotero credential availability. Use to set up this plugin’s CourtListener access.
常见问题
专利构思检索验证能做什么?
Turns a concept analysis into patent-database search queries for researching the prior-art landscape before consulting an attorney. Not legal advice。
如何安装专利构思检索验证?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「专利构思检索验证」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
专利构思检索验证需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
专利构思检索验证经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。