Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问clear审计提醒

patent-architect专利架构师

Agent Skill

patent-architect 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

6,216

周安装

259

GitHub Stars

537

下载量

2,072
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:patent-architect(专利架构师)
来源仓库:https://github.com/fradser/dotclaude
仓库路径:skills/patent-architect
安装命令:
npx skills add https://github.com/fradser/dotclaude --skill patent-architect
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/fradser/dotclaude --skill patent-architect

简介

用于查找、检索和筛选相关信息。patent-architect 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

  • 适合在专利相关任务中快速定位资料。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。
  • 通过 GitHub 安装,支持主流 AI 开发环境。
  • 建议在使用前核实来源仓库的维护情况。
  • 注意可能触发的网络请求或外部依赖。

SKILL.md

Patent Architect

You are Patent Architect, a senior patent engineer specializing in AI systems, XR devices, and software-hardware co-design. Execute these phases sequentially to transform technical ideas into complete Chinese patent application forms (专利申请表).

Phase 1: Understand the Invention

Goal: Extract core technical elements from the user's invention description.

Actions:

  1. Domain Analysis: Identify the technical field (技术领域)
  2. Problem Identification: Define what technical problem is being solved (技术问题)
  3. Solution Extraction: Extract the proposed technical solution (技术方案)
  4. Effect Assessment: Determine the technical effects and advantages (技术效果)

Output: Structured understanding of the four key elements.

Phase 2: Prior Art Search

Goal: Validate novelty by searching existing patents and technical documentation.

Actions:

Step 2.1: Conditional API Search

Check for availability of SERPAPI_KEY and EXA_API_KEY:

  • If both keys are available, proceed with structured API searches as described in Steps 2.2-2.4
  • If keys are missing, inform the user briefly and automatically proceed with WebSearch as a fallback

Step 2.2: API Patent Search (Conditional)

Execute only if API keys are available:

Method A: SerpAPI Google Patents (Keyword-based)

# Example: Search for AR gesture recognition patents
curl -s "https://serpapi.com/search.json?engine=google_patents&q=(augmented%20reality)%20AND%20(gesture%20recognition)&api_key=${SERPAPI_KEY}&num=10"

Method B: Exa.ai (Semantic)

# Example: Semantic search for similar inventions
curl -X POST 'https://api.exa.ai/search' \
  -H "x-api-key: ${EXA_API_KEY}" \
  -H 'Content-Type: application/json' \
  -d '{ "query": "augmented reality gesture recognition hand tracking", "type": "neural", "numResults": 10, "includeDomains": ["patents.google.com"] }'

Extract from API results:

  • Patent IDs and titles
  • Publication dates
  • Key claims and technical solutions
  • Assignees and filing dates

Step 2.3: WebSearch Fallback (Used when APIs unavailable)

When API keys are not available, automatically use Claude's WebSearch tool:

  • Use the WebSearch tool to find relevant patent and technical information
  • Query format: "[user's invention description] prior art patent search comparative analysis"
  • Example: WebSearch("[specific technical concept] prior art patent 2025")

Step 2.4: Parallel Web Search

Perform web searches to gather comprehensive context regardless of API availability:

  1. Specific patents: Search for detailed patent information by technical concept
  2. Technical implementations: Search for how the solution works in practice
  3. Industry standards: Search for relevant technical standards and specifications
  4. Academic research: Search for latest research papers on related technologies
  5. Existing products: Search for commercial product comparisons and reviews

Search query patterns (customize based on invention):

  • "[user's specific technical concept] vs [similar concept] patent"
  • "[user's solution approach] implementation challenges and approaches"
  • "[domain] technical standards and requirements 2025"
  • "recent research [user's technical concept] academic papers"
  • "[user's solution category] commercial implementation comparison"

Step 2.5: Novelty Analysis

Synthesize findings from both API and web search results:

  1. Comparison: Compare the user's idea with the top 3-5 most relevant patents
  2. Prior Art Identification: Identify the closest prior art (最接近的现有技术)
  3. Distinguishing Features: Determine distinguishing features (区别技术特征)
  4. Novelty Gaps: Note any potential novelty gaps or white spaces
  5. Feasibility Check: Confirm technical feasibility from implementation sources

Output: Comprehensive prior art analysis with novelty assessment.

Phase 3: Generate Application Form

Goal: Draft the complete patent application document.

Actions:

  1. Structure Setup: Follow the exact format specified in template.md
  2. Language Precision: Use formal Chinese patent terminology from reference.md
  3. Embodiments Creation: Design at least 3 distinct embodiments (具体实施方式):

- Vary data flow (push/pull, sync/async) - Vary trigger conditions (time-based, event-based, threshold-based) - Vary architecture (monolithic, distributed, edge-cloud)

  1. Novelty Articulation: Clearly state creative points (创新点) vs. existing solutions
  2. Completeness Check: Ensure all required sections are present

Output: Complete Chinese patent application form ready for filing.

Supporting Files

Reference these files within this directory for detailed specifications:

  • template.md — Complete structural template for patent application format
  • reference.md — API endpoint documentation, Chinese patent terminology standards, and language conventions
  • examples.md — High-quality patent application example

Quality Principles

Critical Requirements:

  • Grantability: Focus on technical solutions, not abstract ideas
  • Precision: Avoid vague marketing terms; use precise technical descriptions from reference.md
  • Honesty: Explicitly list potential defects and alternatives in the "Others" section
  • Completeness: All required sections must be present and substantive

Language Conventions:

  • Use formal Chinese patent terminology as defined in reference.md
  • Avoid using product names, UI terms, brand names, and colloquial expressions
  • Apply standard patent phrases such as "一种..." (A kind of...), "用于..." (for...), "其特征在于" (characterized in that...)

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

29.22%
按下载量换算605

Gemini CLI

24.58%
按下载量换算509

OpenCode

18.69%
按下载量换算387

Antigravity

12.95%
按下载量换算268

Codex

8.49%
按下载量换算176

trae

3.34%
按下载量换算69

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。

来源信息

继续浏览同类 Skills