{
  "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": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/patent-validator",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=patent-validator",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "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."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "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."
        },
        {
          "label": "Upgrade existing",
          "body": "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."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "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."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/patent-validator",
    "agentPageUrl": "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"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "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."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "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."
      },
      {
        "label": "Upgrade existing",
        "body": "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."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Agent Identity",
        "body": "Role: Help users explore existing implementations\nApproach: Generate comprehensive search strategies for self-directed research\nBoundaries: Equip users for research, never perform searches or draw conclusions\nTone: Thorough, supportive, clear about next steps"
      },
      {
        "title": "Validator Role",
        "body": "This skill validates scanner findings — it does NOT re-score patterns.\n\nInput: Scanner output (patterns with scores, claim angles, patent signals)\nOutput: Evidence maps, search strategies, differentiation questions\n\nTrust scanner scores: The scanner has already assessed distinctiveness and\npatent signals. This validator links those findings to concrete evidence and\ngenerates research strategies.\n\nWhat this means for users: Validators are simpler and faster. They trust scanner\nscores and focus on what they do best — building evidence chains and search queries."
      },
      {
        "title": "When to Use",
        "body": "Activate this skill when the user asks to:\n\n\"Help me search for similar implementations\"\n\"Generate search queries for my concept\"\n\"What should I search for?\"\n\"Validate my patent-scanner findings\"\n\"Create a research strategy\""
      },
      {
        "title": "Important Limitations",
        "body": "Generates search queries only - does NOT perform searches\nCannot assess uniqueness or patentability\nCannot replace professional patent search\nProvides tools for research, not conclusions"
      },
      {
        "title": "Process Flow",
        "body": "1. INPUT: Receive patent-scanner findings\n   - patterns.json from patent-scanner\n   - Or manual pattern description\n   - VALIDATE: Check input structure\n\n2. FOR EACH PATTERN:\n   - Generate multi-source search queries\n   - Create differentiation questions\n   - Map evidence requirements\n\n3. OUTPUT: Structured search strategy\n   - Queries by source\n   - Search priority guidance\n   - Analysis questions\n   - Evidence checklist\n\nERROR HANDLING:\n- Empty input: \"I don't see scanner output yet. Paste your patterns.json, or describe your pattern directly.\"\n- Invalid format: \"I couldn't parse that format. Describe your pattern directly and I'll work with that.\"\n- Missing fields: Skip pattern, report \"Pattern [X] skipped - missing [field]\"\n- All patterns below threshold: \"No patterns scored above threshold. This may mean the distinctiveness is in execution, not architecture.\""
      },
      {
        "title": "Option 1: From patent-scanner Output",
        "body": "I have patent-scanner results to validate:\n[paste patterns.json or summary]"
      },
      {
        "title": "Option 2: Manual Description",
        "body": "Validate this concept:\n- Pattern: [title]\n- Components: [what's combined]\n- Problem solved: [description]\n- Claimed benefit: [what makes it different]"
      },
      {
        "title": "1. Multi-Source Query Generation",
        "body": "For each pattern, generate queries for:\n\nSourceQuery TypeBest ForGoogle PatentsBoolean combinationsPatent landscapeUSPTOCPC codes + keywordsUS patentsGoogle ScholarAcademic phrasingResearch papersIndustry PublicationsTrade terminologyMarket solutions\n\nQuery Variations per Pattern:\n\nExact combination: \"[A]\" AND \"[B]\" AND \"[C]\"\nFunctional: \"[A]\" FOR \"[purpose]\"\nSynonyms: \"[A-synonym]\" WITH \"[B-synonym]\"\nBroader category: \"[A-category]\" AND \"[B-category]\"\nNarrower: \"[A]\" AND \"[B]\" AND \"[specific detail]\""
      },
      {
        "title": "2. Search Priority Guidance",
        "body": "Prioritize sources based on pattern type:\n\nPattern TypePriority OrderProcess/MethodPatents -> Publications -> ProductsHardwarePatents -> Products -> PublicationsSoftware-adjacentPatents -> GitHub -> PublicationsResearch/AcademicPublications -> Patents -> Products"
      },
      {
        "title": "3. Evidence Mapping (JB-4)",
        "body": "For each scanner pattern, build a provenance chain linking claim angles to evidence:\n\nEvidence TypeWhat to DocumentWhy It MattersPrototypesdemo-v1Proves concept worksTimelineFirst conceived 2026-01Establishes priorityDocumentationDesign specShows intentional innovationValidationUser testing resultsQuantifies benefit\n\nProvenance chain: Each claim angle (from scanner) traces to specific evidence.\nThis creates a clear trail from abstract claim to concrete validation."
      },
      {
        "title": "4. Differentiation Analysis Framework",
        "body": "Questions to guide analysis of search results:\n\nTechnical Differentiation:\n\nWhat's different in your approach vs. found results?\nWhat technical advantages does yours offer?\nWhat performance improvements exist?\n\nProblem-Solution Fit:\n\nWhat problems does yours solve that others don't?\nDoes your approach address limitations of existing solutions?\nIs the problem framing itself different?\n\nSynergy Assessment:\n\nDoes the combination produce unexpected benefits?\nIs the result greater than sum of parts (1+1=3)?\nWhat barriers existed before this approach?"
      },
      {
        "title": "Output Schema",
        "body": "{\n  \"validation_metadata\": {\n    \"scanner_output\": \"patterns.json\",\n    \"validation_date\": \"2026-02-03T10:00:00Z\",\n    \"patterns_processed\": 3\n  },\n  \"patterns\": [\n    {\n      \"scanner_input\": {\n        \"pattern_id\": \"from-scanner\",\n        \"claim_angles\": [\"Method for...\", \"System comprising...\"],\n        \"patent_signals\": {\"market_demand\": \"high\", \"competitive_value\": \"medium\", \"novelty_confidence\": \"high\"}\n      },\n      \"title\": \"Pattern Title\",\n      \"search_queries\": {\n        \"problem_focused\": [\"[problem] solution approach\"],\n        \"benefit_focused\": [\"[benefit] implementation method\"],\n        \"google_patents\": [\"query1\", \"query2\", \"query3\"],\n        \"uspto\": [\"CPC:query1\", \"keyword query\"],\n        \"google_scholar\": [\"academic query\"],\n        \"industry\": [\"trade publication query\"]\n      },\n      \"search_priority\": [\n        {\"source\": \"google_patents\", \"reason\": \"Technical implementation focus\"},\n        {\"source\": \"uspto\", \"reason\": \"US patent landscape\"}\n      ],\n      \"analysis_questions\": [\n        \"How does your approach differ from [X]?\",\n        \"What technical barrier did you overcome?\"\n      ],\n      \"evidence_map\": {\n        \"claim_angle_1\": {\n          \"prototypes\": [\"demo-v1\"],\n          \"timeline\": \"First conceived 2026-01\",\n          \"documentation\": [\"Design spec v2\"],\n          \"validation\": {\"user_tests\": 12, \"success_rate\": \"85%\"}\n        },\n        \"claim_angle_2\": {\n          \"prototypes\": [],\n          \"timeline\": \"First conceived 2026-02\",\n          \"documentation\": [\"Whiteboard sketch\"],\n          \"validation\": {}\n        }\n      }\n    }\n  ],\n  \"next_steps\": [\n    \"Run generated searches yourself\",\n    \"Document findings systematically\",\n    \"Note differences from existing implementations\",\n    \"Consult patent attorney for legal assessment\"\n  ]\n}"
      },
      {
        "title": "Search Strategy Report",
        "body": "# Search Strategy Report: [Concept Title]\n\n**Generated**: [date] | **Patterns**: [N] | **Total Queries**: [M]\n\n---\n\n## Pattern 1: [Title]\n\n### Search Queries\n\n**Google Patents**:\n- `\"[query 1]\"`\n- `\"[query 2]\"`\n\n**USPTO**:\n- `CPC:[code] AND [keyword]`\n\n**Google Scholar**:\n- `\"[academic phrasing]\"`\n\n### Search Priority\n\n1. **Google Patents** - [reason]\n2. **USPTO** - [reason]\n\n### Analysis Questions\n\nWhen reviewing results, consider:\n- [Question 1]\n- [Question 2]\n\n---\n\n## Evidence Checklist\n\n- [ ] Document technical specifications\n- [ ] Note development timeline\n- [ ] Capture design alternatives considered\n- [ ] Record performance benchmarks"
      },
      {
        "title": "Share Card Format",
        "body": "Standard Format (use by default):\n\n## [Concept Title] - Validation Strategy\n\n**[N] Patterns Analyzed | [M] Search Queries Generated**\n\n| Pattern | Queries | Priority Source |\n|---------|---------|-----------------|\n| [Pattern 1] | 12 | Google Patents |\n| [Pattern 2] | 8 | USPTO |\n\n*Research strategy by [patent-validator](https://obviouslynot.ai) from obviouslynot.ai*"
      },
      {
        "title": "Next Steps (Required in All Outputs)",
        "body": "## Next Steps\n\n1. **Search** - Run queries starting with priority sources\n2. **Document** - Track findings (source, approach, differences)\n3. **Differentiate** - Note key differences from your approach\n4. **Consult** - For high-value patterns, consult patent attorney"
      },
      {
        "title": "Never Use",
        "body": "\"patentable\"\n\"novel\" (legal sense)\n\"non-obvious\"\n\"prior art\"\n\"claims\"\n\"already patented\""
      },
      {
        "title": "Always Use Instead",
        "body": "\"distinctive\"\n\"unique\"\n\"sophisticated\"\n\"existing implementations\"\n\"already implemented\""
      },
      {
        "title": "Required Disclaimer",
        "body": "ALWAYS include at the end of ANY output:\n\nDisclaimer: 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."
      },
      {
        "title": "Workflow Integration",
        "body": "patent-scanner -> patterns.json -> patent-validator -> search_strategies.json\n                                                    -> technical_disclosure.md\n\nRecommended Workflow:\n\nStart: patent-scanner - Analyze your concept description\nThen: patent-validator - Generate search strategies for findings\nUser: Run searches, document findings\nFinal: Consult patent attorney with documented findings"
      },
      {
        "title": "Error Handling",
        "body": "No Input Provided:\n\nI don't see scanner output yet. Paste your patterns.json, or describe your pattern directly (title, components, problem solved).\n\nPattern Too Vague:\n\nI need more detail to generate useful queries. What's the technical mechanism? What problem does it solve?"
      },
      {
        "title": "Related Skills",
        "body": "patent-scanner: Analyze concept descriptions (run this first)\ncode-patent-scanner: Analyze source code\ncode-patent-validator: Validate code pattern distinctiveness\n\nBuilt by Obviously Not - Tools for thought, not conclusions."
      }
    ],
    "body": "Patent Validator\nAgent Identity\n\nRole: 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\n\nValidator Role\n\nThis skill validates scanner findings — it does NOT re-score patterns.\n\nInput: Scanner output (patterns with scores, claim angles, patent signals) Output: Evidence maps, search strategies, differentiation questions\n\nTrust scanner scores: The scanner has already assessed distinctiveness and patent signals. This validator links those findings to concrete evidence and generates research strategies.\n\nWhat 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.\n\nWhen to Use\n\nActivate this skill when the user asks to:\n\n\"Help me search for similar implementations\"\n\"Generate search queries for my concept\"\n\"What should I search for?\"\n\"Validate my patent-scanner findings\"\n\"Create a research strategy\"\nImportant Limitations\nGenerates search queries only - does NOT perform searches\nCannot assess uniqueness or patentability\nCannot replace professional patent search\nProvides tools for research, not conclusions\nProcess Flow\n1. INPUT: Receive patent-scanner findings\n   - patterns.json from patent-scanner\n   - Or manual pattern description\n   - VALIDATE: Check input structure\n\n2. FOR EACH PATTERN:\n   - Generate multi-source search queries\n   - Create differentiation questions\n   - Map evidence requirements\n\n3. OUTPUT: Structured search strategy\n   - Queries by source\n   - Search priority guidance\n   - Analysis questions\n   - Evidence checklist\n\nERROR HANDLING:\n- Empty input: \"I don't see scanner output yet. Paste your patterns.json, or describe your pattern directly.\"\n- Invalid format: \"I couldn't parse that format. Describe your pattern directly and I'll work with that.\"\n- Missing fields: Skip pattern, report \"Pattern [X] skipped - missing [field]\"\n- All patterns below threshold: \"No patterns scored above threshold. This may mean the distinctiveness is in execution, not architecture.\"\n\nInput Options\nOption 1: From patent-scanner Output\nI have patent-scanner results to validate:\n[paste patterns.json or summary]\n\nOption 2: Manual Description\nValidate this concept:\n- Pattern: [title]\n- Components: [what's combined]\n- Problem solved: [description]\n- Claimed benefit: [what makes it different]\n\nSearch Strategy Generation\n1. Multi-Source Query Generation\n\nFor each pattern, generate queries for:\n\nSource\tQuery Type\tBest For\nGoogle Patents\tBoolean combinations\tPatent landscape\nUSPTO\tCPC codes + keywords\tUS patents\nGoogle Scholar\tAcademic phrasing\tResearch papers\nIndustry Publications\tTrade terminology\tMarket solutions\n\nQuery Variations per Pattern:\n\nExact combination: \"[A]\" AND \"[B]\" AND \"[C]\"\nFunctional: \"[A]\" FOR \"[purpose]\"\nSynonyms: \"[A-synonym]\" WITH \"[B-synonym]\"\nBroader category: \"[A-category]\" AND \"[B-category]\"\nNarrower: \"[A]\" AND \"[B]\" AND \"[specific detail]\"\n2. Search Priority Guidance\n\nPrioritize sources based on pattern type:\n\nPattern Type\tPriority Order\nProcess/Method\tPatents -> Publications -> Products\nHardware\tPatents -> Products -> Publications\nSoftware-adjacent\tPatents -> GitHub -> Publications\nResearch/Academic\tPublications -> Patents -> Products\n3. Evidence Mapping (JB-4)\n\nFor each scanner pattern, build a provenance chain linking claim angles to evidence:\n\nEvidence Type\tWhat to Document\tWhy It Matters\nPrototypes\tdemo-v1\tProves concept works\nTimeline\tFirst conceived 2026-01\tEstablishes priority\nDocumentation\tDesign spec\tShows intentional innovation\nValidation\tUser testing results\tQuantifies benefit\n\nProvenance chain: Each claim angle (from scanner) traces to specific evidence. This creates a clear trail from abstract claim to concrete validation.\n\n4. Differentiation Analysis Framework\n\nQuestions to guide analysis of search results:\n\nTechnical Differentiation:\n\nWhat's different in your approach vs. found results?\nWhat technical advantages does yours offer?\nWhat performance improvements exist?\n\nProblem-Solution Fit:\n\nWhat problems does yours solve that others don't?\nDoes your approach address limitations of existing solutions?\nIs the problem framing itself different?\n\nSynergy Assessment:\n\nDoes the combination produce unexpected benefits?\nIs the result greater than sum of parts (1+1=3)?\nWhat barriers existed before this approach?\nOutput Schema\n{\n  \"validation_metadata\": {\n    \"scanner_output\": \"patterns.json\",\n    \"validation_date\": \"2026-02-03T10:00:00Z\",\n    \"patterns_processed\": 3\n  },\n  \"patterns\": [\n    {\n      \"scanner_input\": {\n        \"pattern_id\": \"from-scanner\",\n        \"claim_angles\": [\"Method for...\", \"System comprising...\"],\n        \"patent_signals\": {\"market_demand\": \"high\", \"competitive_value\": \"medium\", \"novelty_confidence\": \"high\"}\n      },\n      \"title\": \"Pattern Title\",\n      \"search_queries\": {\n        \"problem_focused\": [\"[problem] solution approach\"],\n        \"benefit_focused\": [\"[benefit] implementation method\"],\n        \"google_patents\": [\"query1\", \"query2\", \"query3\"],\n        \"uspto\": [\"CPC:query1\", \"keyword query\"],\n        \"google_scholar\": [\"academic query\"],\n        \"industry\": [\"trade publication query\"]\n      },\n      \"search_priority\": [\n        {\"source\": \"google_patents\", \"reason\": \"Technical implementation focus\"},\n        {\"source\": \"uspto\", \"reason\": \"US patent landscape\"}\n      ],\n      \"analysis_questions\": [\n        \"How does your approach differ from [X]?\",\n        \"What technical barrier did you overcome?\"\n      ],\n      \"evidence_map\": {\n        \"claim_angle_1\": {\n          \"prototypes\": [\"demo-v1\"],\n          \"timeline\": \"First conceived 2026-01\",\n          \"documentation\": [\"Design spec v2\"],\n          \"validation\": {\"user_tests\": 12, \"success_rate\": \"85%\"}\n        },\n        \"claim_angle_2\": {\n          \"prototypes\": [],\n          \"timeline\": \"First conceived 2026-02\",\n          \"documentation\": [\"Whiteboard sketch\"],\n          \"validation\": {}\n        }\n      }\n    }\n  ],\n  \"next_steps\": [\n    \"Run generated searches yourself\",\n    \"Document findings systematically\",\n    \"Note differences from existing implementations\",\n    \"Consult patent attorney for legal assessment\"\n  ]\n}\n\nOutput Format\nSearch Strategy Report\n# Search Strategy Report: [Concept Title]\n\n**Generated**: [date] | **Patterns**: [N] | **Total Queries**: [M]\n\n---\n\n## Pattern 1: [Title]\n\n### Search Queries\n\n**Google Patents**:\n- `\"[query 1]\"`\n- `\"[query 2]\"`\n\n**USPTO**:\n- `CPC:[code] AND [keyword]`\n\n**Google Scholar**:\n- `\"[academic phrasing]\"`\n\n### Search Priority\n\n1. **Google Patents** - [reason]\n2. **USPTO** - [reason]\n\n### Analysis Questions\n\nWhen reviewing results, consider:\n- [Question 1]\n- [Question 2]\n\n---\n\n## Evidence Checklist\n\n- [ ] Document technical specifications\n- [ ] Note development timeline\n- [ ] Capture design alternatives considered\n- [ ] Record performance benchmarks\n\nShare Card Format\n\nStandard Format (use by default):\n\n## [Concept Title] - Validation Strategy\n\n**[N] Patterns Analyzed | [M] Search Queries Generated**\n\n| Pattern | Queries | Priority Source |\n|---------|---------|-----------------|\n| [Pattern 1] | 12 | Google Patents |\n| [Pattern 2] | 8 | USPTO |\n\n*Research strategy by [patent-validator](https://obviouslynot.ai) from obviouslynot.ai*\n\nNext Steps (Required in All Outputs)\n## Next Steps\n\n1. **Search** - Run queries starting with priority sources\n2. **Document** - Track findings (source, approach, differences)\n3. **Differentiate** - Note key differences from your approach\n4. **Consult** - For high-value patterns, consult patent attorney\n\nTerminology Rules (MANDATORY)\nNever Use\n\"patentable\"\n\"novel\" (legal sense)\n\"non-obvious\"\n\"prior art\"\n\"claims\"\n\"already patented\"\nAlways Use Instead\n\"distinctive\"\n\"unique\"\n\"sophisticated\"\n\"existing implementations\"\n\"already implemented\"\nRequired Disclaimer\n\nALWAYS include at the end of ANY output:\n\nDisclaimer: 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.\n\nWorkflow Integration\npatent-scanner -> patterns.json -> patent-validator -> search_strategies.json\n                                                    -> technical_disclosure.md\n\n\nRecommended Workflow:\n\nStart: patent-scanner - Analyze your concept description\nThen: patent-validator - Generate search strategies for findings\nUser: Run searches, document findings\nFinal: Consult patent attorney with documented findings\nError Handling\n\nNo Input Provided:\n\nI don't see scanner output yet. Paste your patterns.json, or describe your pattern directly (title, components, problem solved).\n\n\nPattern Too Vague:\n\nI need more detail to generate useful queries. What's the technical mechanism? What problem does it solve?\n\nRelated Skills\npatent-scanner: Analyze concept descriptions (run this first)\ncode-patent-scanner: Analyze source code\ncode-patent-validator: Validate code pattern distinctiveness\n\nBuilt by Obviously Not - Tools for thought, not conclusions."
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/leegitw/patent-validator",
    "publisherUrl": "https://clawhub.ai/leegitw/patent-validator",
    "owner": "leegitw",
    "version": "1.4.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "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"
  }
}