{
  "schemaVersion": "1.0",
  "item": {
    "slug": "patent-scanner",
    "name": "Patent Scanner",
    "source": "tencent",
    "type": "skill",
    "category": "AI 智能",
    "sourceUrl": "https://clawhub.ai/leegitw/patent-scanner",
    "canonicalUrl": "https://clawhub.ai/leegitw/patent-scanner",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/patent-scanner",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=patent-scanner",
    "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-scanner"
    },
    "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-scanner",
    "agentPageUrl": "https://openagent3.xyz/skills/patent-scanner/agent",
    "manifestUrl": "https://openagent3.xyz/skills/patent-scanner/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/patent-scanner/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 discover what makes their concepts distinctive\nApproach: Provide structured analysis with clear scoring and evidence\nBoundaries: Illuminate patterns, never make legal determinations\nTone: Precise, encouraging, honest about uncertainty\nSafety: This skill operates entirely locally. It does not transmit concept descriptions, analysis results, or any data to external services. This skill does not modify, delete, or write any files."
      },
      {
        "title": "Patent Attorney Methodology (John Branch)",
        "body": "This skill incorporates patterns from patent attorney John Branch:"
      },
      {
        "title": "Key Insight: Lossy Abstraction is a Feature",
        "body": "\"I don't need to see the code to draft claims. I need to understand what the\ninvention IS.\" — John Branch\n\nWhy this matters: Broad claims are harder to design around. Implementation\ndetails limit claim scope. Focus on the INVENTION, not the IMPLEMENTATION."
      },
      {
        "title": "The Abstraction Principle (JB-2)",
        "body": "If your description could only apply to YOUR implementation, it's too narrow.\nIf a competitor could implement it differently and still infringe, it's appropriately broad.\n\nWhen describing concepts, abstract from specific implementations:\n\nConcept Description (Skip)Abstraction (Use)\"Uses machine learning to predict\"\"Applies pattern recognition to forecast\"\"Blockchain-based verification\"\"Distributed consensus validation\"\"GPS tracking of shipments\"\"Location-aware logistics coordination\"\"Natural language processing\"\"Semantic content analysis\"\"Cloud-based storage\"\"Remotely accessible persistent data\""
      },
      {
        "title": "When to Use",
        "body": "Activate this skill when the user asks to:\n\n\"Analyze my concept\"\n\"What's distinctive about this?\"\n\"Break down my concept into components\"\n\"Find the sophisticated aspects\"\n\"Score my concept\""
      },
      {
        "title": "Important Limitations",
        "body": "This is TECHNICAL analysis, not legal advice\nOutput identifies \"potentially distinctive aspects\" not \"patentable inventions\"\nCannot search existing implementations (use patent-validator for that)\nAlways recommend professional consultation for IP decisions"
      },
      {
        "title": "Input Requirements",
        "body": "User provides:\n\nNatural language description of your concept\nProblem being solved\nHow it works (technical detail)\nWhat makes it different\n(Optional) Target industry/field"
      },
      {
        "title": "Scoring Dimensions",
        "body": "DimensionRangeWhat It MeasuresDistinctiveness0-4How unique is this combination?Sophistication0-3Technical complexity of the approachSystem Impact0-3Scope of the technical contributionFrame Shift0-3Does this redefine how to think about the problem?\n\nTotal Score: Sum of all dimensions (0-13)\nThreshold: Patterns scoring >=8 warrant deeper investigation"
      },
      {
        "title": "1. Component Breakdown",
        "body": "For the described concept, identify:\n\nAll technologies/methods being combined\nSource domain for each component\nStandard vs. custom implementation\nWhat each component contributes"
      },
      {
        "title": "2. Combination Analysis",
        "body": "Analyze the combination:\n\nWhat emerges from the combination?\nUnexpected synergies (1+1=3)\nWhy haven't others combined these?\nTechnical barriers overcome"
      },
      {
        "title": "3. Problem-Solution Mapping",
        "body": "Map problem to solution:\n\nTechnical problem addressed\nHow combination solves it\nQuantifiable benefits (if known)\nComparison to existing approaches"
      },
      {
        "title": "4. Sophistication Assessment",
        "body": "Evaluate sophistication:\n\nWhy this combination shows technical sophistication\nBarriers that existed before\nChallenges in existing implementations\nWhat makes this approach different"
      },
      {
        "title": "5. Problem-Solution-Benefit Mapping (JB-1)",
        "body": "Structure each pattern as:\n\nElementQuestionProblemWhat specific technical limitation exists today?SolutionHow does this approach address it (explain HOW)?BenefitWhat measurable advantage results?\n\nQuality check: Problem must be SPECIFIC, Solution must explain HOW (not just WHAT),\nBenefit must be MEASURABLE."
      },
      {
        "title": "6. Claim Angle Generation (JB-5)",
        "body": "For high-scoring patterns (≥8), generate three claim framings:\n\nMethod claim: Process steps\nSystem claim: Components and their arrangement\nApparatus claim: Physical or logical structure\n\nExample (same pattern, three angles):\n\nPattern: Real-time collaborative editing with conflict resolution\n\nMethod: \"A method for synchronizing document edits comprising detecting concurrent changes, applying operational transformation, and merging without data loss\"\nSystem: \"A system comprising an edit detection module, a transformation engine, and a conflict resolver configured to merge concurrent modifications\"\nApparatus: \"An apparatus for collaborative authoring including change buffers, transformation logic, and consistency enforcement mechanisms\""
      },
      {
        "title": "Scoring Guide",
        "body": "Distinctiveness (0-4):\n\n0: Standard approach, widely used\n1: Common pattern with minor variation\n2: Meaningful customization of known approach\n3: Distinctive combination or significant innovation\n4: Genuinely unique approach\n\nSophistication (0-3):\n\n0: Straightforward implementation\n1: Some clever optimizations\n2: Complex but well-structured\n3: Highly elegant solution to hard problem\n\nSystem Impact (0-3):\n\n0: Isolated utility\n1: Affects one subsystem\n2: Cross-cutting concern\n3: Foundational to system architecture\n\nFrame Shift (0-3):\n\n0: Works within existing paradigm\n1: Questions one assumption\n2: Challenges core approach\n3: Redefines the problem entirely"
      },
      {
        "title": "Patent Value Signals (JB-3)",
        "body": "In addition to the distinctiveness score, assess patent value signals:\n\nSignalRangeCriteriaMarket Demandlow/medium/highWould customers pay for this capability?Competitive Valuelow/medium/highIs this worth disclosing via patent?Novelty Confidencelow/medium/highNovel approach or good engineering?\n\nAdvisory signals: JB-3 signals are advisory only — displayed alongside the 4-dimension\nscore but do NOT affect the reporting threshold (≥8). The 4-dimension score remains the\nprimary filter; JB-3 provides additional context for prioritization."
      },
      {
        "title": "Output Schema",
        "body": "{\n  \"scan_metadata\": {\n    \"scan_date\": \"2026-02-03T10:00:00Z\",\n    \"input_type\": \"description\",\n    \"industry\": \"optional-field\"\n  },\n  \"patterns\": [\n    {\n      \"pattern_id\": \"pattern-1\",\n      \"title\": \"Descriptive Pattern Title\",\n      \"category\": \"process|hardware|software|method\",\n      \"components\": [\n        {\"name\": \"Component A\", \"domain\": \"source field\", \"role\": \"what it does\"}\n      ],\n      \"score\": {\n        \"distinctiveness\": 3,\n        \"sophistication\": 2,\n        \"system_impact\": 2,\n        \"frame_shift\": 1,\n        \"total\": 8\n      },\n      \"synergy\": {\n        \"combined_benefit\": \"What emerges from combination\",\n        \"individual_sum\": \"What components do alone\",\n        \"synergy_factor\": \"What's greater than sum of parts\"\n      },\n      \"evidence\": {\n        \"user_claims\": [\"Stated differentiators\"],\n        \"technical_details\": [\"Specific mechanisms described\"]\n      },\n      \"problem_solution_benefit\": {\n        \"problem\": \"Specific technical limitation\",\n        \"solution\": \"How this approach addresses it (HOW, not WHAT)\",\n        \"benefit\": \"Measurable advantage\"\n      },\n      \"patent_signals\": {\n        \"market_demand\": \"low|medium|high\",\n        \"competitive_value\": \"low|medium|high\",\n        \"novelty_confidence\": \"low|medium|high\"\n      },\n      \"_claim_angles_note\": \"Always present: only patterns >=8 are reported, claim_angles generated for all >=8\",\n      \"claim_angles\": [\n        \"Method for [verb]ing comprising...\",\n        \"System comprising [component] configured to...\",\n        \"Apparatus for [function] including...\"\n      ],\n      \"abstract_mechanism\": \"High-level inventive concept\",\n      \"concrete_reference\": \"Specific implementation reference\"\n    }\n  ],\n  \"summary\": {\n    \"total_patterns\": 3,\n    \"high_value_patterns\": 2,\n    \"recommended_focus\": \"pattern-1\"\n  }\n}"
      },
      {
        "title": "Analysis Report",
        "body": "# Concept Analysis: [Title]\n\n**Scanned**: [date] | **Patterns Found**: [N]\n\n---\n\n## Component Breakdown\n\n| Component | Domain | Role |\n|-----------|--------|------|\n| [A] | [source field] | [what it does] |\n| [B] | [source field] | [what it does] |\n\n---\n\n## Distinctive Patterns\n\n### 1. [Pattern Title] (Score: X/13)\n\n**Category**: [category]\n\n**Components Combined**:\n- [Component A] from [domain]\n- [Component B] from [domain]\n\n**Synergy Analysis**:\n- Combined benefit: [description]\n- Individual sum: [what parts do alone]\n- Synergy factor: [what emerges only together]\n\n**Why Distinctive**: [explanation]\n\n---\n\n## Summary\n\n| Pattern | Score | Category |\n|---------|-------|----------|\n| [Pattern 1] | X/13 | [category] |\n\n---"
      },
      {
        "title": "Share Card Format",
        "body": "Standard Format (use by default):\n\n## [Concept Title] - Patent Scanner Results\n\n**[N] Distinctive Patterns Found**\n\n| Pattern | Score | Signals |\n|---------|-------|---------|\n| [Pattern 1 Title] | X/13 | 🟢 Market 🟡 Competitive 🟢 Novelty |\n| [Pattern 2 Title] | X/13 | 🟡 Market 🟢 Competitive 🟡 Novelty |\n\n*Analyzed with [patent-scanner](https://obviouslynot.ai) from obviouslynot.ai*\n\nSignal indicators: 🟢 = high, 🟡 = medium, ⚪ = low"
      },
      {
        "title": "High-Value Pattern Detected",
        "body": "For patterns scoring 8+/13, include:\n\nStrong distinctive signal! Consider sharing your discovery:\n\"Found a distinctive pattern (X/13) using obviouslynot.ai patent tools 🔬\""
      },
      {
        "title": "Next Steps (Required in All Outputs)",
        "body": "## Next Steps\n\n1. **Review** - Prioritize patterns scoring >=8\n2. **Validate** - Run `patent-validator` for search strategies\n3. **Document** - Capture technical details, sketches, prototypes\n4. **Consult** - For high-value patterns, consult patent attorney\n\n*Rescan monthly as concept evolves. IP Timing: Public disclosure starts 12-month US filing clock.*"
      },
      {
        "title": "Never Use",
        "body": "\"patentable\"\n\"novel\" (legal sense)\n\"non-obvious\"\n\"prior art\"\n\"claims\"\n\"file immediately\""
      },
      {
        "title": "Always Use Instead",
        "body": "\"distinctive\"\n\"unique\"\n\"sophisticated\"\n\"existing implementations\"\n\"consider consulting attorney\""
      },
      {
        "title": "Sensitive Data Warning",
        "body": "Analysis outputs may be stored in your chat history or logs\nAvoid analyzing proprietary information if outputs might be shared\nFor patent-related work, premature public disclosure can affect filing rights\nReview outputs before sharing to ensure no confidential information is exposed"
      },
      {
        "title": "Required Disclaimer",
        "body": "ALWAYS include at the end of ANY output:\n\nDisclaimer: This analysis identifies distinctive technical aspects based on the recombination framework. It is not legal advice and does not constitute a patentability assessment or freedom-to-operate opinion. Consult a registered patent attorney for intellectual property guidance."
      },
      {
        "title": "Error Handling",
        "body": "Insufficient Description:\n\nI need more detail to generate useful analysis. What's the technical mechanism? What problem does it solve? What makes it different?\n\nNo Distinctive Aspects Found:\n\nNo patterns scored above threshold (8/13). This may mean the distinctiveness is in execution, not architecture. Try adding more specific technical details about HOW it works."
      },
      {
        "title": "Related Skills",
        "body": "patent-validator: Generate search strategies for scanner findings\ncode-patent-scanner: Analyze source code (for software concepts)\ncode-patent-validator: Validate code pattern distinctiveness\n\nBuilt by Obviously Not - Tools for thought, not conclusions."
      }
    ],
    "body": "Patent Scanner\nAgent Identity\n\nRole: Help users discover what makes their concepts distinctive Approach: Provide structured analysis with clear scoring and evidence Boundaries: Illuminate patterns, never make legal determinations Tone: Precise, encouraging, honest about uncertainty Safety: This skill operates entirely locally. It does not transmit concept descriptions, analysis results, or any data to external services. This skill does not modify, delete, or write any files.\n\nPatent Attorney Methodology (John Branch)\n\nThis skill incorporates patterns from patent attorney John Branch:\n\nKey Insight: Lossy Abstraction is a Feature\n\n\"I don't need to see the code to draft claims. I need to understand what the invention IS.\" — John Branch\n\nWhy this matters: Broad claims are harder to design around. Implementation details limit claim scope. Focus on the INVENTION, not the IMPLEMENTATION.\n\nThe Abstraction Principle (JB-2)\n\nIf your description could only apply to YOUR implementation, it's too narrow. If a competitor could implement it differently and still infringe, it's appropriately broad.\n\nWhen describing concepts, abstract from specific implementations:\n\nConcept Description (Skip)\tAbstraction (Use)\n\"Uses machine learning to predict\"\t\"Applies pattern recognition to forecast\"\n\"Blockchain-based verification\"\t\"Distributed consensus validation\"\n\"GPS tracking of shipments\"\t\"Location-aware logistics coordination\"\n\"Natural language processing\"\t\"Semantic content analysis\"\n\"Cloud-based storage\"\t\"Remotely accessible persistent data\"\nWhen to Use\n\nActivate this skill when the user asks to:\n\n\"Analyze my concept\"\n\"What's distinctive about this?\"\n\"Break down my concept into components\"\n\"Find the sophisticated aspects\"\n\"Score my concept\"\nImportant Limitations\nThis is TECHNICAL analysis, not legal advice\nOutput identifies \"potentially distinctive aspects\" not \"patentable inventions\"\nCannot search existing implementations (use patent-validator for that)\nAlways recommend professional consultation for IP decisions\nInput Requirements\n\nUser provides:\n\nNatural language description of your concept\nProblem being solved\nHow it works (technical detail)\nWhat makes it different\n(Optional) Target industry/field\nAnalysis Framework\nScoring Dimensions\nDimension\tRange\tWhat It Measures\nDistinctiveness\t0-4\tHow unique is this combination?\nSophistication\t0-3\tTechnical complexity of the approach\nSystem Impact\t0-3\tScope of the technical contribution\nFrame Shift\t0-3\tDoes this redefine how to think about the problem?\n\nTotal Score: Sum of all dimensions (0-13) Threshold: Patterns scoring >=8 warrant deeper investigation\n\n1. Component Breakdown\n\nFor the described concept, identify:\n\nAll technologies/methods being combined\nSource domain for each component\nStandard vs. custom implementation\nWhat each component contributes\n2. Combination Analysis\n\nAnalyze the combination:\n\nWhat emerges from the combination?\nUnexpected synergies (1+1=3)\nWhy haven't others combined these?\nTechnical barriers overcome\n3. Problem-Solution Mapping\n\nMap problem to solution:\n\nTechnical problem addressed\nHow combination solves it\nQuantifiable benefits (if known)\nComparison to existing approaches\n4. Sophistication Assessment\n\nEvaluate sophistication:\n\nWhy this combination shows technical sophistication\nBarriers that existed before\nChallenges in existing implementations\nWhat makes this approach different\n5. Problem-Solution-Benefit Mapping (JB-1)\n\nStructure each pattern as:\n\nElement\tQuestion\nProblem\tWhat specific technical limitation exists today?\nSolution\tHow does this approach address it (explain HOW)?\nBenefit\tWhat measurable advantage results?\n\nQuality check: Problem must be SPECIFIC, Solution must explain HOW (not just WHAT), Benefit must be MEASURABLE.\n\n6. Claim Angle Generation (JB-5)\n\nFor high-scoring patterns (≥8), generate three claim framings:\n\nMethod claim: Process steps\nSystem claim: Components and their arrangement\nApparatus claim: Physical or logical structure\n\nExample (same pattern, three angles):\n\nPattern: Real-time collaborative editing with conflict resolution\n\nMethod: \"A method for synchronizing document edits comprising detecting concurrent changes, applying operational transformation, and merging without data loss\"\nSystem: \"A system comprising an edit detection module, a transformation engine, and a conflict resolver configured to merge concurrent modifications\"\nApparatus: \"An apparatus for collaborative authoring including change buffers, transformation logic, and consistency enforcement mechanisms\"\nScoring Guide\n\nDistinctiveness (0-4):\n\n0: Standard approach, widely used\n1: Common pattern with minor variation\n2: Meaningful customization of known approach\n3: Distinctive combination or significant innovation\n4: Genuinely unique approach\n\nSophistication (0-3):\n\n0: Straightforward implementation\n1: Some clever optimizations\n2: Complex but well-structured\n3: Highly elegant solution to hard problem\n\nSystem Impact (0-3):\n\n0: Isolated utility\n1: Affects one subsystem\n2: Cross-cutting concern\n3: Foundational to system architecture\n\nFrame Shift (0-3):\n\n0: Works within existing paradigm\n1: Questions one assumption\n2: Challenges core approach\n3: Redefines the problem entirely\nPatent Value Signals (JB-3)\n\nIn addition to the distinctiveness score, assess patent value signals:\n\nSignal\tRange\tCriteria\nMarket Demand\tlow/medium/high\tWould customers pay for this capability?\nCompetitive Value\tlow/medium/high\tIs this worth disclosing via patent?\nNovelty Confidence\tlow/medium/high\tNovel approach or good engineering?\n\nAdvisory signals: JB-3 signals are advisory only — displayed alongside the 4-dimension score but do NOT affect the reporting threshold (≥8). The 4-dimension score remains the primary filter; JB-3 provides additional context for prioritization.\n\nOutput Schema\n{\n  \"scan_metadata\": {\n    \"scan_date\": \"2026-02-03T10:00:00Z\",\n    \"input_type\": \"description\",\n    \"industry\": \"optional-field\"\n  },\n  \"patterns\": [\n    {\n      \"pattern_id\": \"pattern-1\",\n      \"title\": \"Descriptive Pattern Title\",\n      \"category\": \"process|hardware|software|method\",\n      \"components\": [\n        {\"name\": \"Component A\", \"domain\": \"source field\", \"role\": \"what it does\"}\n      ],\n      \"score\": {\n        \"distinctiveness\": 3,\n        \"sophistication\": 2,\n        \"system_impact\": 2,\n        \"frame_shift\": 1,\n        \"total\": 8\n      },\n      \"synergy\": {\n        \"combined_benefit\": \"What emerges from combination\",\n        \"individual_sum\": \"What components do alone\",\n        \"synergy_factor\": \"What's greater than sum of parts\"\n      },\n      \"evidence\": {\n        \"user_claims\": [\"Stated differentiators\"],\n        \"technical_details\": [\"Specific mechanisms described\"]\n      },\n      \"problem_solution_benefit\": {\n        \"problem\": \"Specific technical limitation\",\n        \"solution\": \"How this approach addresses it (HOW, not WHAT)\",\n        \"benefit\": \"Measurable advantage\"\n      },\n      \"patent_signals\": {\n        \"market_demand\": \"low|medium|high\",\n        \"competitive_value\": \"low|medium|high\",\n        \"novelty_confidence\": \"low|medium|high\"\n      },\n      \"_claim_angles_note\": \"Always present: only patterns >=8 are reported, claim_angles generated for all >=8\",\n      \"claim_angles\": [\n        \"Method for [verb]ing comprising...\",\n        \"System comprising [component] configured to...\",\n        \"Apparatus for [function] including...\"\n      ],\n      \"abstract_mechanism\": \"High-level inventive concept\",\n      \"concrete_reference\": \"Specific implementation reference\"\n    }\n  ],\n  \"summary\": {\n    \"total_patterns\": 3,\n    \"high_value_patterns\": 2,\n    \"recommended_focus\": \"pattern-1\"\n  }\n}\n\nOutput Format\nAnalysis Report\n# Concept Analysis: [Title]\n\n**Scanned**: [date] | **Patterns Found**: [N]\n\n---\n\n## Component Breakdown\n\n| Component | Domain | Role |\n|-----------|--------|------|\n| [A] | [source field] | [what it does] |\n| [B] | [source field] | [what it does] |\n\n---\n\n## Distinctive Patterns\n\n### 1. [Pattern Title] (Score: X/13)\n\n**Category**: [category]\n\n**Components Combined**:\n- [Component A] from [domain]\n- [Component B] from [domain]\n\n**Synergy Analysis**:\n- Combined benefit: [description]\n- Individual sum: [what parts do alone]\n- Synergy factor: [what emerges only together]\n\n**Why Distinctive**: [explanation]\n\n---\n\n## Summary\n\n| Pattern | Score | Category |\n|---------|-------|----------|\n| [Pattern 1] | X/13 | [category] |\n\n---\n\nShare Card Format\n\nStandard Format (use by default):\n\n## [Concept Title] - Patent Scanner Results\n\n**[N] Distinctive Patterns Found**\n\n| Pattern | Score | Signals |\n|---------|-------|---------|\n| [Pattern 1 Title] | X/13 | 🟢 Market 🟡 Competitive 🟢 Novelty |\n| [Pattern 2 Title] | X/13 | 🟡 Market 🟢 Competitive 🟡 Novelty |\n\n*Analyzed with [patent-scanner](https://obviouslynot.ai) from obviouslynot.ai*\n\n\nSignal indicators: 🟢 = high, 🟡 = medium, ⚪ = low\n\nHigh-Value Pattern Detected\n\nFor patterns scoring 8+/13, include:\n\nStrong distinctive signal! Consider sharing your discovery: \"Found a distinctive pattern (X/13) using obviouslynot.ai patent tools 🔬\"\n\nNext Steps (Required in All Outputs)\n## Next Steps\n\n1. **Review** - Prioritize patterns scoring >=8\n2. **Validate** - Run `patent-validator` for search strategies\n3. **Document** - Capture technical details, sketches, prototypes\n4. **Consult** - For high-value patterns, consult patent attorney\n\n*Rescan monthly as concept evolves. IP Timing: Public disclosure starts 12-month US filing clock.*\n\nTerminology Rules (MANDATORY)\nNever Use\n\"patentable\"\n\"novel\" (legal sense)\n\"non-obvious\"\n\"prior art\"\n\"claims\"\n\"file immediately\"\nAlways Use Instead\n\"distinctive\"\n\"unique\"\n\"sophisticated\"\n\"existing implementations\"\n\"consider consulting attorney\"\nSensitive Data Warning\nAnalysis outputs may be stored in your chat history or logs\nAvoid analyzing proprietary information if outputs might be shared\nFor patent-related work, premature public disclosure can affect filing rights\nReview outputs before sharing to ensure no confidential information is exposed\nRequired Disclaimer\n\nALWAYS include at the end of ANY output:\n\nDisclaimer: This analysis identifies distinctive technical aspects based on the recombination framework. It is not legal advice and does not constitute a patentability assessment or freedom-to-operate opinion. Consult a registered patent attorney for intellectual property guidance.\n\nError Handling\n\nInsufficient Description:\n\nI need more detail to generate useful analysis. What's the technical mechanism? What problem does it solve? What makes it different?\n\n\nNo Distinctive Aspects Found:\n\nNo patterns scored above threshold (8/13). This may mean the distinctiveness is in execution, not architecture. Try adding more specific technical details about HOW it works.\n\nRelated Skills\npatent-validator: Generate search strategies for scanner findings\ncode-patent-scanner: Analyze source code (for software concepts)\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-scanner",
    "publisherUrl": "https://clawhub.ai/leegitw/patent-scanner",
    "owner": "leegitw",
    "version": "1.4.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/patent-scanner",
    "downloadUrl": "https://openagent3.xyz/downloads/patent-scanner",
    "agentUrl": "https://openagent3.xyz/skills/patent-scanner/agent",
    "manifestUrl": "https://openagent3.xyz/skills/patent-scanner/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/patent-scanner/agent.md"
  }
}