patent architect

Engineering Community

Skill notes

Output Mode

Parse $ARGUMENTS to determine output mode: Argument · Mode · Output --md (default) · Local Markdown · Save as .md file to project directory --lark · Feishu Cloud Doc · Create via lark-cli, using Lark rich-text features --lark mode accepts optional location arguments (mutually exclusive), supporting token or Feishu URL:

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

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) Method B: Exa.ai (Semantic) Extract from API results: Patent IDs and titles

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")

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@FradSer · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · Vendor-specific
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 2: Prior Art Search

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

02
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

03
Step 2.2: API Patent Search (Conditional)

Execute only if API keys are available: Method A: SerpAPI Google Patents (Keyword-based) Method B: Exa.ai (Semantic) Extract from API results: Patent IDs and titles

04
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")`

05
Step 2.4: Parallel Web Search

Perform web searches to gather comprehensive context regardless of API availability: Specific patents: Search for detailed patent information by technical concept Technical implementations: Search for how the solution works in practice Industry standards: Search for relevant technical standards and specifications Academic research: Search for latest research papers on related technologies

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.