USPTO Database
Official USPTO patent and trademark records: PatentSearch, TSDR, assignments, and reproducible IP logs.
- What
- Official USPTO patent and trademark records: PatentSearch, TSDR, assignments, and reproducible IP logs.
- Cost
- Free
- Needs
- USPTO and/or PatentsView API keys for the API flows (export USPTO_API_KEY and/or PATENTSVIEW_API_KEY as environment variables, never in committed files or pasted transcripts). The Muse app (mobile or web) for the planning side. Check the current USPTO API Manager instructions before starting, as endpoints and rate limits change.
- Level
- Intermediate — USPTO and/or PatentsView API keys for the API flows…
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a data-gathering workflow for official United States patent and trademark records from USPTO systems. It prefers official surfaces first (Open Data Portal, Patent File Wrapper, PatentSearch API, TSDR Data API, assignment search, PTAB data) and treats secondary indexes like Google Patents or Lens.org as convenience only, cross-checking the official record whenever the answer matters. Includes a PatentSearch JSON query workflow with a Python request skeleton (explicit filters, deterministic sort and pagination), a TSDR workflow for trademark status, documents, and owner history (normalize serial numbers, respect the lower rate limits on document downloads), file-wrapper and prosecution-history lookup, an assignment workflow (conveyance text, execution vs. recordation dates, distinguishing assignment records from legal ownership conclusions), and a reproducible research log table separating official facts from inferred analysis. Ends with a review checklist: official source first, endpoints verified before running code, keys kept out of files and logs, rate limits respected, legal conclusions escalated. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: requires USPTO/PatentsView API keys for the API flows (see the prerequisites in the install prompt); data gathering only, it gives no legal advice and flags ownership conclusions for attorney review. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
a data-gathering workflow for official United States patent and trademark records from USPTO systems. It prefers official surfaces first (Open Data Portal, Patent File Wrapper, PatentSearch API, TSDR Data API, assignment search, PTAB data) and treats secondary indexes like Google Patents or Lens.org as convenience only, cross-checking the official record whenever the answer matters.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "USPTO Database" with your Muse. Prerequisites: USPTO and/or PatentsView API keys for the API flows (export USPTO_API_KEY and/or PATENTSVIEW_API_KEY as environment variables, never in committed files or pasted transcripts). The Muse app (mobile or web) for the planning side. Check the current USPTO API Manager instructions before starting, as endpoints and rate limits change. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/scientific-db-uspto-database/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Look up [the patent / the trademark / the assignment history] for [number, name, or assignee]. Start with the official USPTO record." 3. Ask Muse to keep a reproducible log table (source, date searched, identifier/query, filters, results, notes) and to flag anything needing legal review. Tip: when the answer matters, always cross-check the official record. Secondary indexes are convenient but they are not the record. Safety: a skill is plain-text instructions; it runs nothing by itself. This is data gathering only, never legal advice. Keep API keys out of files and logs, never paste secrets into a chat, and review anything Muse proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It works with an API key or a token that you provide.
What the scan found — excerpts from the install prompt
- uses API keys or tokens — Prerequisites: USPTO and/or PatentsView API keys for the API flows (export USPTO_API_KEY and/or PATENTSVIEW_AP · Prérequis : clés API USPTO et/ou PatentsView pour les flux API (exportez USPTO_API_KEY et/ou PATENTSVIEW_API_K
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : uses API keys or tokens
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.