Search official USPTO records and organize reproducible patent and trademark research.
The material appears to be a prompt/workflow for querying official USPTO records, and the system flags it as prompt-only, open-source, and highly trusted by the community. No local code execution or undisclosed data exfiltration is evident, but the README conflicts with the metadata on whether API keys are needed, so the actual implementation and credential requirements should be verified.
The metadata says 'no keys', but the README explicitly states that many USPTO API flows require USPTO_API_KEY or PATENTSVIEW_API_KEY via environment variables. This inconsistency warrants caution; if those APIs are actually used, the keys should be treated as sensitive and kept out of code and chat logs.
The documented purpose is to access official or USPTO-supported sites and APIs such as ODP, PatentSearch, TSDR, and Assignment Search, which is normal network use within the stated function. There is no evidence of connections to unrelated or unknown endpoints, but any search content would be transmitted to the corresponding USPTO services.
The system objectively flags this as prompt-only. The README provides request examples and workflow guidance rather than requiring a local daemon, script execution, or privileged system capabilities, so no actual code-execution permission request is evident from the material.
The material focuses on retrieving public patent, trademark, prosecution-history, and assignment records, and does not claim local file access, local database access, or permissions beyond that scope. Aside from user-supplied query content, there is no sign of excessive data access.
The source is an open-source GitHub repository with extremely high community adoption (~210.5k stars), both strong risk-reducing signals, and the system also marks it as open-source. The missing license and unknown maintenance status suggest basic repo verification is still prudent, but no clear supply-chain red flags are evident from the provided material.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "uspto-database" skill from askskill: 1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/scientific-db-uspto-database/SKILL.md 2. Save it as ~/.claude/skills/scientific-db-uspto-database/SKILL.md 3. Reload skills and tell me it's ready
Help me create a USPTO research workflow: first search patents related to a technology topic, then check relevant trademark status, and organize the steps, keywords, and sources into a reproducible research log.
A structured workflow covering patent search, trademark status checks, and a research log template.
I have a U.S. trademark application number. Explain how to use TSDR to check its current status, filing history, and key dates, then produce a report-ready summary.
A concise summary with TSDR lookup steps, status interpretation, key milestones, and conclusions.
Please design a workflow using USPTO data to verify assignment records for a patent, track ownership changes, and generate an auditable research log.
A step-by-step assignment verification process with ownership-change tracking and an auditable log format.
Use this skill when a task needs official United States patent or trademark records from USPTO systems.
Do not use this skill to give legal advice. Treat it as a data-gathering and record-verification workflow.
Prefer official USPTO or USPTO-supported surfaces first:
Use secondary sources only as convenience indexes. When the answer matters, cross-check the official record.
Many USPTO API flows require an API key. Store keys in environment variables or a secret manager, never in committed files or pasted transcripts.
Common environment names:
export USPTO_API_KEY="..."
export PATENTSVIEW_API_KEY="..."
For PatentSearch, send the key with the X-Api-Key header. For TSDR, follow
the current USPTO API Manager instructions and rate-limit guidance.
Use PatentSearch for broad patent and pre-grant publication search when the question is about trends, inventors, assignees, classifications, dates, or portfolio slices.
Workflow:
Python request skeleton:
import os
import requests
API_KEY = os.environ["PATENTSVIEW_API_KEY"]
BASE = "https://search.patentsview.org/api/v1"
payload = {
"q": {
"_and": [
{"patent_date": {"_gte": "2024-01-01"}},
{"assignees.assignee_organization": {"_text_any": ["Google", "Alphabet"]}},
]
},
"f": ["patent_id", "patent_title", "patent_date"],
"s": [{"patent_date": "desc"}],
"o": {"per_page": 100, "page": 1},
}
response = requests.post(
f"{BASE}/patent/",
headers={"X-Api-Key": API_KEY, "Content-Type": "application/json"},
json=payload,
timeout=30,
)
response.raise_for_status()
print(response.json())
Before reusing a query, verify current endpoint names, field paths, request parameters, and API-key availability in the live PatentSearch docs.
Use TSDR when the task needs trademark case status, documents, images, owner history, or prosecution events.
Workflow:
For large trademark pulls, prefer documented bulk-data flows rather than screen-scraping public pages.
For application status, transaction history, and prosecution documents:
…
Handle returns, refunds, fraud checks, and warranty claim decisions efficiently.
Use Bun for runtime, bundling, testing, packages, and Node migration decisions.
Use the correct Ethereum Keccak-256 hashing in Node.js and TypeScript.
Apply Nuxt 4 patterns for SSR safety, performance, and data fetching.
Generate images, videos, and audio with one unified AI media workflow.
Design Quarkus 3 backend patterns for messaging, APIs, data, and async workflows.
Search US patents, extract claims, and map citations.
Search US patents, analyze assignee portfolios, and explore citation networks.
Access and analyze USPTO final petition decision documents more efficiently.
Search patents and trademarks, including claims, legal status, and prosecution details.
Search patents and analyze company IP portfolios and filing landscapes.
Search patents, trademarks, assignees, and inventors through Google Patents.