Skip to content

nexscope-ai/nexscope-ecommerce-skills / ecommerce-maidalv-product-tro-detection

ecommerce.maidalv-product-tro-detection

Verified

Assess product imagery for TRO, trademark, patent, and copyright infringement risk. Use this skill when the user asks for this exact ecommerce workflow, analysis, data lookup, or deliverable.

FileKindSize
SKILL.mdskill md5.8 KB
manifest.jsonconfig653 B
references/api.jsonconfig1.1 KB
references/api.mdmarkdown3.8 KB
references/credentials.mdmarkdown943 B
references/testing.mdmarkdown1.0 KB
references/workflow.mdmarkdown1.2 KB
scripts/maidalv_check_api_flash.pyscript11.2 KB
scripts/upload_image.pyscript5.4 KB

references/api.md

View on GitHub
# Product infringement and TRO risk API

`POST /api/v1/tools/research/maidalv/checkApiFlash`

| Field | Type | Required | Constraint |
|---|---|---:|---|
| `mainProductImage` | string | Yes | Public URL or image data URI; maximum 1000 characters. |
| `referenceImages` | string[] | No | Up to 3 similar-product images. |
| `otherProductImages` | string[] | No | Up to 5 additional product images. |
| `ipImages` | string[] | No | Up to 3 IP evidence images. |
| `referenceText` | string | No | Maximum 1000 characters. |
| `description` | string | No | Prefer a concise product title; maximum 1000 characters. |
| `ipKeywords` | string[] | No | Up to 20 keywords. |
| `language` | string | No | `zh` or `en`; default `zh`. |

For a local image, run `scripts/upload_image.py` first and pass the resulting public URL as `mainProductImage`.

The response includes `status`, `checkId`, `total`, overall `riskLevel`, `results`, `nonResults`, and rendering `columns`. Result entries may include `ipType`, `text`, `ipOwner`, `regNo`, `riskLevel`, `riskScore`, `riskDescription`, `ipAssetUrls`, TRO plaintiff/case fields, and an assessment `report`. Optional fields are omitted when unavailable; do not assume they are present.

```bash
python scripts/maidalv_check_api_flash.py '{"mainProductImage":"https://example.com/product.jpg","language":"zh"}'
```

Allow at least 120 seconds. Require outer platform `code: 0`, then inspect the business `status` for task completion. Prefer the upstream `X-Cost-Token` header when available; the outer Nexscope wrapper may not expose it.

## 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.

## 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.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall