360 Secure SkillHub
360 安全技能中心

USPTO

该 Skill 通过 oo CLI 调用 OOMOL 的 uspto 连接器，提供商标案件最新更新日期、TSDR 案件状态和文档元数据三类只读查询动作。使用前需安装并登录 oo CLI 并连接 USPTO，凭据由 OOMOL 服务端注入；输入为动作名与符合 Schema 的 JSON 负载，输出为 JSON 结构化响应。

oomol
oomol
热度 31.07
最近更新 2026-09-20 11:16:04
分类：搜索依赖：代码执行 / 第三方 API应用场景：研究 / 法律文档

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-uspto
Metadata
name
oo-uspto
description
USPTO (uspto.gov). Use this skill for ANY USPTO request — searching and reading data. Whenever a task involves USPTO, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"USPTO","author":"OOMOL","version":"1.0.3","services":["uspto"],"icon":"https://static.oomol.com/logo/third-party/uspto.png"}

USPTO

Operate USPTO through your OOMOL-connected account. This skill calls the uspto connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected USPTO. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "uspto" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "uspto" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • get_trademark_case_last_update — Get the latest recorded TSDR update dates for a trademark application serial number.
  • get_trademark_case_status — Get the official TSDR case status record for a trademark application serial number as XML.
  • get_trademark_documents_metadata — Get TSDR metadata for documents associated with a trademark application serial number.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change USPTO state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — USPTO is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=uspto

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources