
Uspto Database
Pull official USPTO patent and trademark records into reproducible prior-art and IP landscape research logs.
Overview
USPTO Database is an agent skill most often used in Idea (also Validate scope, Operate iterate) that walks you through official USPTO patent and trademark lookups with reproducible IP research logs—not legal advice.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill uspto-databaseWhat is this skill?
- Official-first workflow: ODP, Patent File Wrapper, PatentSearch API, TSDR, assignment search, PTAB in ODP
- Covers granted patents, pre-grant publications, prosecution history, and trademark status documents
- Explicit non-legal-advice boundary—data gathering and record verification only
- Reproducible research logs for prior-art, portfolio, and landscape analysis
- Guidance to treat Google Patents, Lens.org, and Semantic Scholar as secondary indexes only
Adoption & trust: 1.1k installs on skills.sh; 210k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need verified US patent or trademark records for prior art or portfolio checks, but ad-hoc Google searches leave gaps and no audit trail.
Who is it for?
Founders doing prior-art sweeps, indie SaaS builders checking naming collisions, or agents assembling IP landscape briefs from primary USPTO sources.
Skip if: Formal freedom-to-operate opinions, litigation strategy, or any task where the user needs a lawyer’s conclusion instead of raw government data.
When should I use this skill?
Searching granted patents or pre-grant publications, checking application or trademark status, building reproducible prior-art or IP landscape logs, or comparing USPTO records with secondary indexes.
What do I get? / Deliverables
You produce a reproducible log of official USPTO queries and retrieved records suitable for scope decisions and diligence—without substituting for legal counsel.
- Structured IP research log with sources and query metadata
- Verified bibliographic, file-wrapper, or trademark document references
- Notes on gaps where secondary tools were used only as indexes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
IP and competitive landscape work usually starts in Idea when you are still deciding what is novel and who already filed—canonical shelf is research even though validation and operate reuse the same workflow. Research subphase covers competitor and prior-art discovery; USPTO ODP, PatentSearch, and TSDR are primary sources for that evidence trail.
Where it fits
Map granted patents near your core feature using PatentSearch before you commit to a differentiated positioning.
Cross-check competitor portfolio pages against USPTO assignment and file-wrapper records for accuracy.
Document trademark clearance steps via TSDR while narrowing brand name candidates for a landing page.
Re-verify assignment or status changes after a product rename or acquisition rumor surfaces.
How it compares
Use this for official USPTO record workflows—not generic web scraping skills or marketing SEO research playbooks.
Common Questions / FAQ
Who is uspto-database for?
Solo builders and agents who must cite USPTO-primary evidence for patents, trademarks, assignments, or PTAB data while keeping research reproducible.
When should I use uspto-database?
In Idea research for prior art and landscapes; in Validate when scoping naming or patent overlap; in Operate when verifying assignment or status changes—always as data gathering, not legal advice.
Is uspto-database safe to install?
It is a documentation-style research workflow with network access to public USPTO systems; review the Security Audits panel on this Prism page before piping queries through automated agents.
SKILL.md
READMESKILL.md - Uspto Database
# USPTO Database Use this skill when a task needs official United States patent or trademark records from USPTO systems. ## When to Use - Searching granted patents or pre-grant publications. - Checking patent application status, file-wrapper data, assignments, or public prosecution history. - Looking up trademark status, documents, or assignment history. - Building reproducible prior-art, portfolio, or IP landscape research logs. - Comparing USPTO records with secondary tools such as Google Patents, Lens.org, Semantic Scholar, or company patent pages. Do not use this skill to give legal advice. Treat it as a data-gathering and record-verification workflow. ## Source Selection Prefer official USPTO or USPTO-supported surfaces first: - Open Data Portal (ODP): current home for migrated USPTO datasets and APIs. - Patent File Wrapper: public patent application bibliographic data and file wrapper records. - PatentSearch API: PatentsView search API for granted patents and pre-grant publication datasets. - TSDR Data API: trademark status and document retrieval. - Patent and Trademark Assignment Search: ownership transfer records. - PTAB data in ODP: Patent Trial and Appeal Board proceedings. Use secondary sources only as convenience indexes. When the answer matters, cross-check the official record. ## Authentication and Secrets 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: ```bash 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. ## PatentSearch Workflow Use PatentSearch for broad patent and pre-grant publication search when the question is about trends, inventors, assignees, classifications, dates, or portfolio slices. Workflow: 1. Identify the endpoint from the current PatentSearch reference or Swagger UI. 2. Build a JSON query with explicit filters. 3. Request only the fields needed for the analysis. 4. Sort and paginate deterministically. 5. Record the endpoint, query body, date, data currency note, and result count. Python request skeleton: ```python 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. ## Trademark/TSDR Workflow Use TSDR when the task needs trademark case status, documents, images, owner history, or prosecution events. Workflow: 1. Normalize the serial number or registration number. 2. Check the current TSDR API instructions and required API-key header. 3. Fetch status first, then documents only if needed. 4. Respect the lower rate limit for PDF, ZIP, and multi-case downloads. 5. Capture retrieval date and serial/registration identifier in the output. For large trademark pulls, prefer documented bulk-data flows rather than screen-scraping public pages. ## File Wrapper and Prosecution History For application status, transaction history, and prosecu