# Send Patent Validator to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "patent-validator", "name": "Patent Validator", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/leegitw/patent-validator", "canonicalUrl": "https://clawhub.ai/leegitw/patent-validator", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/patent-validator", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=patent-validator", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "patent-validator", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-06T23:12:45.800Z", "expiresAt": "2026-05-13T23:12:45.800Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=patent-validator", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=patent-validator", "contentDisposition": "attachment; filename=\"patent-validator-1.4.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "patent-validator" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/patent-validator" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/patent-validator", "downloadUrl": "https://openagent3.xyz/downloads/patent-validator", "agentUrl": "https://openagent3.xyz/skills/patent-validator/agent", "manifestUrl": "https://openagent3.xyz/skills/patent-validator/agent.json", "briefUrl": "https://openagent3.xyz/skills/patent-validator/agent.md" } } ``` ## Documentation ### 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 ### 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." ### 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] ### 1. Multi-Source Query Generation For each pattern, generate queries for: SourceQuery TypeBest ForGoogle PatentsBoolean combinationsPatent landscapeUSPTOCPC codes + keywordsUS patentsGoogle ScholarAcademic phrasingResearch papersIndustry PublicationsTrade terminologyMarket 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 TypePriority OrderProcess/MethodPatents -> Publications -> ProductsHardwarePatents -> Products -> PublicationsSoftware-adjacentPatents -> GitHub -> PublicationsResearch/AcademicPublications -> Patents -> Products ### 3. Evidence Mapping (JB-4) For each scanner pattern, build a provenance chain linking claim angles to evidence: Evidence TypeWhat to DocumentWhy It MattersPrototypesdemo-v1Proves concept worksTimelineFirst conceived 2026-01Establishes priorityDocumentationDesign specShows intentional innovationValidationUser testing resultsQuantifies 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", "novelty_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" ] } ### 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 ### 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. ## Trust - Source: tencent - Verification: Indexed source record - Publisher: leegitw - Version: 1.4.0 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-05-06T23:12:45.800Z - Expires at: 2026-05-13T23:12:45.800Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/patent-validator) - [Send to Agent page](https://openagent3.xyz/skills/patent-validator/agent) - [JSON manifest](https://openagent3.xyz/skills/patent-validator/agent.json) - [Markdown brief](https://openagent3.xyz/skills/patent-validator/agent.md) - [Download page](https://openagent3.xyz/downloads/patent-validator)