Ecommerce.Patent Title Abstract Translation logo

Ecommerce.Patent Title Abstract Translation

Organization
nexscope-ai
ecommerce.patent-title-abstract-translation

Retrieve translated patent titles and abstracts from the Nexscope (Nexscope) patent database. Triggered when users request patent abstract translation, patent title translation, translated patent abstracts, patent content in other languages, patent abstracts in Chinese/English/Japanese, or need to look up abstracts and titles of specific patents by patent ID or publication number, patent abstract translation, patent title translation, Nexscope, patent translation, or abstract lookup. Also triggered when users mention Nexscope, Nexscope, or patent abstract queries, even if "translation" is not explicitly mentioned.

Overview

Publishernexscope-ai
Repositorynexscope-ecommerce-skills
Skill nameecommerce.patent-title-abstract-translation
Stars
104
Forks
14
Bundled files
3
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by nexscope-ai on GitHub. Read the source before you install it.

Installation

Install the Ecommerce.Patent Title Abstract Translation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/nexscope-ai/nexscope-ecommerce-skills/tree/main/ecommerce-patent-title-abstract-translation
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/nexscope-ai/nexscope-ecommerce-skills.git /tmp/nexscope-ecommerce-skills
mkdir -p .claude/skills
cp -r /tmp/nexscope-ecommerce-skills/ecommerce-patent-title-abstract-translation .claude/skills/ecommerce.patent-title-abstract-translation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ecommerce.Patent Title Abstract Translation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ecommerce.Patent Title Abstract Translation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ecommerce.Patent Title Abstract Translation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Nexscope Patent Abstract (Translated)

This skill guides you on how to retrieve translated patent titles and abstracts from the Nexscope (Nexscope) patent database, supporting Chinese, English, and Japanese translations.

Core Concepts

Nexscope (Nexscope) is a leading patent intelligence platform. This tool queries its database to return translated titles and abstracts for one patent per Skill call. You can look up patents by patent ID or publication (announcement) number, and receive translations in Chinese, English, or Japanese.

Patent identification: Each patent can be identified by either a patentId (internal Nexscope identifier) or a patentNumber (public publication/announcement number such as US20200012345A1 or CN112345678A). If both are provided, the patent ID takes priority.

Family patent fallback: When the original patent has no abstract available, you can optionally substitute the abstract from a related family patent by enabling the replacement option.

Parameter Guide

ParameterTypeRequiredDescription
patentIdstringAt least one of patentId or patentNumberNexscope internal patent ID. This Skill sends one patent ID per call; the gateway accepts comma-separated IDs. Max length 60,000 characters.
patentNumberstringAt least one of patentId or patentNumberPublication (announcement) number. This Skill sends one publication number per call; the gateway accepts comma-separated numbers. Max length 60,000 characters.
replaceByRelatedintegerNoWhether to substitute a family patent abstract when the original is unavailable. 1 = yes, 0 = no. Default 0.
langstringNoTarget translation language. en = English (default), cn = Chinese, jp = Japanese.

Key Rules

  1. At least one identifier is required: You must provide either patentId or patentNumber (or both). If both are supplied, patentId takes priority.
  2. Single patent per request: This Skill sends one patent per call to control credits. For multiple patents, obtain explicit consent before separate calls; the gateway accepts comma-separated identifiers.
  3. Default language is English: When the user does not specify a language, use en.
  4. Family fallback: Set replaceByRelated to 1 only when the user explicitly wants a substitute abstract from a family patent if the original is missing.

Skill single-patent policy: This endpoint consumes credits. If you need to check multiple patents, you must obtain explicit user consent and make separate requests. This Skill sends one patent per call to control credits; the gateway accepts comma-separated identifiers.

Response Fields

FieldDescription
totalNumber of patent records returned
dataArray of patent objects (see below)
data[].patentIdNexscope internal patent ID
data[].pnPublication (announcement) number
data[].titleTranslated patent title
data[].abstractTextTranslated patent abstract
data[].pnRelatedPublication number of the substitute family patent (only present when family replacement was used)
costTokenTokens consumed by this request

Usage Examples

1. Translate a single patent abstract to English by publication number

Look up patent number US20200012345A1 and give me the English abstract.

Parameters: patentNumber = "US20200012345A1", lang = "en"

2. Look up by patent ID with family fallback

Get the Japanese abstract for patent ID 12345678. If the abstract is unavailable, use a family patent instead.

Parameters: patentId = "12345678", lang = "jp", replaceByRelated = 1

Display Rules

  1. Present data clearly: Show results in a well-structured table with patent number, title, and abstract.
  2. Indicate language: Mention the translation language in the output header so users know which language the results are in.
  3. Family patent notice: If pnRelated is present in any result, explicitly inform the user that the abstract was sourced from a family patent and show the substitute publication number.
  4. Long abstracts: For very long abstracts, display the full text without truncation so users can review the complete content.
  5. Error handling: When a query fails or returns no results, explain the likely cause (e.g., invalid patent number, patent not found in database) and suggest corrections.
  6. No subjective commentary: Present the translated text as-is without adding interpretation or legal analysis of the patent content.

Invocation

  • API Endpoint: POST /zhihuiya/abstractDataTranslated (full parameters/response/error codes in references/api.md)
  • Python Script: python scripts/patent_title_abstract_translation.py '<JSON params>' [--inline]
  • Cost Constraints: This tool consumes credits. The same parameter combination defaults to a single call per session. The script includes a 24-hour local cache. Do not automatically retry with different keywords, pagination, or modified parameters on failure or empty results; inform the user that additional costs will be incurred before continuing to search. Skill single-patent policy: This endpoint consumes credits. This Skill sends one patent per call to control credits; obtain explicit consent before separate calls for multiple patents.

Output Strategy (default script behavior):

  • Always write the full response to <cwd>/nexscope/<YYYY-MM-DD>/<session>/data/nexscope-zhihuiya-abstract-data-translated-<timestamp>.json (<cwd> is the working directory at script execution time, which in Claude Code is the current project directory; <session> is taken from the SESSION_ID environment variable, auto-grouped by user task; writing to /tmp is forbidden -- error if the current directory is not writable)
  • Response body <= 8 KB: print the full JSON to stdout after writing to disk
  • Response body > 8 KB: print only a summary to stdout after writing to disk (top-level fields, common counts like total/costToken, length of the largest list field + first 3 samples)
  • Add --inline to force full output to stdout (still writes to disk)

Data Reading Tip: Check the summary first to determine if it is sufficient; when specific fields are needed, prefer using jq or ConvertFrom-Json to extract from the saved JSON file on demand to avoid loading the entire JSON into context.

Authentication

Set NEXSCOPE_API_KEY. Visit https://www.nexscope.ai/help/skills-external-access?co-from=skillNS to manage credits.

Important Limitations

  • Identifier required: At least one of patent ID or publication number must be provided; the tool cannot perform keyword-based searches.
  • Translation languages: Only Chinese (cn), English (en), and Japanese (jp) are supported.
  • No full-text retrieval: This tool returns only titles and abstracts, not full patent claims or descriptions.
  • Family replacement is optional: The substitute family patent abstract is only provided when explicitly requested via replaceByRelated = 1.

User Expression & Scenario Quick Reference

Applicable -- Patent abstract and title translation queries:

User SaysScenario
"Translate this patent abstract"Single patent translation
"What does patent XX say / what is it about"Abstract lookup
"Get the Chinese/Japanese version of this patent"Specific language translation
"Look up the abstract for patent number XX"Publication number lookup
"The abstract is missing, try a family patent"Family patent fallback

Not applicable -- Needs beyond abstract translation:

  • Full patent text, claims, or description retrieval
  • Patent search by keyword, classification, or applicant
  • Patent legal status, citation analysis, or landscape reports
  • Patent valuation or infringement analysis

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ecommerce.Patent Title Abstract Translation AI skill do?

Retrieve translated patent titles and abstracts from the Nexscope (Nexscope) patent database. Triggered when users request patent abstract translation, patent title translation, translated patent abstracts, patent content in other languages, patent abstracts in Chinese/English/Japanese, or need to look up abstracts and titles of specific patents by patent ID or publication number, patent abstract translation, patent title translation, Nexscope, patent translation, or abstract lookup. Also triggered when users mention Nexscope, Nexscope, or patent abstract queries, even if "translation" is n...

Why use Ecommerce.Patent Title Abstract Translation on TypingMind?

Because you install it once and use it with any model. Ecommerce.Patent Title Abstract Translation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ecommerce.Patent Title Abstract Translation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/nexscope-ai/nexscope-ecommerce-skills/tree/main/ecommerce-patent-title-abstract-translation. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ecommerce.Patent Title Abstract Translation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ecommerce.Patent Title Abstract Translation?

As many as you like. As long as a model supports skills, you can use Ecommerce.Patent Title Abstract Translation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ecommerce.Patent Title Abstract Translation AI skill free?

It is published on GitHub by nexscope-ai. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇