nexscope-ai/nexscope-ecommerce-skills / ecommerce-utility-patent-detector
ecommerce.utility-patent-detector
VerifiedDetect and search for similar utility/invention patents based on product information. Trigger when users mention utility patent detection, patent infringement risk, patent similarity search, patent screening, invention patent search, patent risk assessment, TRO (Temporary Restraining Order) risk analysis, utility patent, invention patent detection, patent infringement risk, patent search, TRO risk, Ruiguan. Even if the user does not explicitly say "utility patent", trigger this skill whenever their need involves checking whether a product may infringe existing utility/invention patents before selling in a target market.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.1 KB |
| manifest.json | config | 238 B |
| references/api.md | markdown | 6.4 KB |
| scripts/utility_patent_detector.py | script | 6.6 KB |
references/api.md
View on GitHub# Ruiguan Utility Patent Detection API Reference
## API Specification
- **Endpoint**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/ruiguan/utilityPatentDetection`
- **HTTP Method**: POST, Content-Type: application/json
- **Authentication**: Header `Authorization: <api_key>`, api_key is read from environment variable `NEXSCOPE_API_KEY` or `NEXSCOPE_API_KEY` (if not configured, follow the **## Resolving Authentication and Credit Issues** section in SKILL.md)
## Request Parameters
POST Body (JSON):
| Parameter | Type | Required | Description |
|------|------|------|------|
| productTitle | string | Yes | Product title, max 1000 characters |
| productDescription | string | Yes | Product description, max 1000 characters |
| region | string | Yes | Country/region code(s) where the product is intended for sale, multiple separated by commas. Currently supports US. Default `US` |
| topNumber | integer | Yes | Number of results to recall, range: 10--200, default `100` |
## Nexscope response envelope
These research endpoints return a platform object with numeric `code`, nullable `msg`, and business `data`. Only outer `code: 0` means success; `200`, string codes, missing codes, and HTTP 200 alone do not. A nonzero code is a platform error: show `msg` and do not interpret the payload as a successful result.
`msg` preserves the upstream message when available; Chinese messages are translated to English by Nexscope. A successful response without a message has `msg: null`. Do not infer success or retry behavior from the message text. On both success and failure, the direct fields `code`, `errcode`, `errorCode`, `msg`, `errmsg`, `message`, and `errorMsg` are removed from public `data`. Read the message only from outer `msg`; deeper business fields are preserved, including nested `code` and `status`.
Business field tables and abbreviated business examples below describe `data`, unless explicitly labeled as a complete platform response. For example, a business `products` field is at HTTP `data.products`, and a business `data` array is at HTTP `data.data`. The research endpoints already had this outer envelope; no additional wrapper is added.
```json
{"code":0,"msg":null,"data":{}}
```
Metadata includes string `ts` (epoch milliseconds), string `cost` (elapsed milliseconds, not credits), `time`, and nullable `traceId`. Handle network/HTTP failures before the platform code; gateway failures may not be platform JSON. Keep the existing billing-header guidance separate from elapsed time.
## Response Structure
| Field | Type | Description |
|------|------|------|
| total | integer | Record count |
| detectId | string | Detection ID |
| costToken | integer | Token cost |
| type | string | Render style |
| columns | array | Render column definitions |
| data | array | Patent list (see below) |
### Patent Object Fields
| Field | Type | Description |
|------|------|------|
| globalUtilityId | string | Patent ID |
| title | string | Utility patent title |
| titleCn | string | Utility patent title (Chinese) |
| similarity | number | Similarity between the product and this patent (0--1) |
| patentValidity | string | Patent validity: `Active` or `Invalid` |
| applicationNumber | string | Application number |
| applicationDate | string | Application date (yyyy-MM-dd) |
| publicationNumber | string | Publication number |
| publicationDate | string | Publication date (yyyy-MM-dd) |
| estimatedDueDate | string | Estimated expiration date (yyyy-MM-dd) |
| region | string | Receiving office |
| patentAbstract | string | Abstract |
| patentAbstractCn | string | Abstract (Chinese) |
| claims | string | Claims |
| claimsCn | string | Claims (Chinese) |
| specification | string | Specification |
| specificationCn | string | Specification (Chinese) |
| inventors | array | Inventors and countries concatenated, array format |
| inventorAddresses | array | Inventor addresses, array format |
| applicants | array | Applicants and countries concatenated, array format |
| applicantAddresses | array | Rights holder addresses, array format |
| priorityNumber | array | Priority numbers, array format |
| relatedPublicationDate | array | First publication dates (yyyy-MM-dd), array format |
| patentImageUrl | string | Patent cover image |
| images | array | Patent drawings |
| classNumList | array | Classification number path list, format: classNum1 > classNum2 > classNum3 |
| cpcKindRaw | array | CPC classification (raw JSONArray) |
| troCase | boolean | Whether there is a TRO enforcement history |
| troHolder | boolean | Whether it is a patent of a TRO rights holder |
## Error Codes
HTTP 200 does not prove business success. Read only the numeric outer platform `code`: `0` succeeds and any other value fails. Show outer `msg`; never test removed provider codes or nested business `code` as the platform status. Authentication, permissions, balance, and validation failures may be platform errors even with HTTP 200; also handle non-2xx HTTP and non-JSON responses.
### Recovery guidance
| Condition | Action |
|---|---|
| Authentication failed | HTTP 401 or authorized error: Follow the **## Resolving Authentication and Credit Issues** section in SKILL.md. |
| Insufficient credits or balance | HTTP 402: Follow the **## Resolving Authentication and Credit Issues** section in SKILL.md. |
## curl Example
```bash
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/ruiguan/utilityPatentDetection \
-H "Authorization: Bearer ${NEXSCOPE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{"productTitle": "Portable USB-C 65W GaN Fast Charger", "productDescription": "A compact 65W GaN USB-C fast charger, equipped with foldable prongs, supporting PD3.0 and QC4.0 protocols, dual USB-C ports and one USB-A port, suitable for laptops, phones, and tablets.", "region": "US", "topNumber": 100}'
```
---
## API Key request rate and retries
All API Keys of one Nexscope user share the public API execution request-rate allowance, measured in any rolling 1-second window. The allowed RPS depends on that user's entitlements; it is not a universal 1 RPS. One Skill operation may issue multiple public API requests, each of which uses the allowance.
HTTP 429 with Nexscope outer code `13012` means request-rate exhaustion: honor the response's `Retry-After`. Outer code `13013` means concurrent-request exhaustion, not rate exhaustion; honor `Retry-After` when supplied. Check the HTTP status and outer JSON code separately. Do not automatically replay writes or requests with uncertain outcomes; first reconcile the operation's state.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |