Agent skill

USPTO Patent and Trademark Data

by davila7 in davila7/claude-code-templates

Searches USPTO patent and trademark data through its APIs: patent search, PEDS examination history, assignments, citations, office actions and TSDR status.

MITAuto-check passedLegal & Compliance

Install USPTO Patent and Trademark Data

skills CLI
$ npx skills add davila7/claude-code-templates --skill uspto-database -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davila7/claude-code-templates uspto-database --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/scientific/uspto-database .claude/skills/uspto-database && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
uspto-database
GitHub stars
32k
Used in
12 other repos
Token cost
~4.6k tokens
SKILL.md length
1,165 words
Files
8 (incl. scripts, references)
Skills in repo
477
Repo updated
First seen
Licence
MIT

At a glance

Searches USPTO patent and trademark data through its APIs: patent search, PEDS examination history, assignments, citations, office actions and TSDR status.

  • Works in 3 steps: PatentSearch API - Modern… → PEDS (Patent Examination Data System) -… → TSDR (Trademark Status & Document…
  • Searching patents by keyword, inventor, assignee or classification
  • SKILL.md covers Overview, When to Use This Skill, USPTO API Ecosystem and Quick Start, plus 6 more sections
  • Runs Python scripts from its folder; calls uv; reaches assignment-api.uspto.gov and search.patentsview.org; needs USPTO_API_KEY

What it does

The skill covers the USPTO's APIs for patents and trademarks. The core ones are PatentSearch, an ElasticSearch-based search by keyword, inventor, assignee, classification or date; PEDS, for application status and transaction history from 1981 onward, used through the `uspto-opendata-python` library; and TSDR, for trademark status, ownership and prosecution history by serial or registration number.

Further APIs handle patent and trademark assignments, enriched citation analysis, office action text and office action citations. Three scripts, `scripts/patent_search.py`, `scripts/peds_client.py` and `scripts/trademark_client.py`, wrap the clients, and reference notes cover each API. The skill notes that PatentSearch replaced legacy PatentsView in May 2025, holds data through June 30, 2025, and is limited to 45 requests per minute.

When your agent uses it

  • Searching patents by keyword, inventor, assignee or classification
  • Checking the status and ownership history of a trademark
  • Pulling examination history and office actions for a patent application
  • Analyzing a company's patent portfolio or citations for a prior art search

Example prompts

  • “Search for patents on solid-state batteries assigned to Toyota and list their claims.”
  • “Look up the status and prosecution history of the trademark with this serial number.”
  • “Pull the office actions for this patent application and summarize the rejections.”

Requirements

  • Python
  • Network access to the USPTO APIs

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. PatentSearch API - Modern ElasticSearch-based patent search (replaced legacy PatentsView in May 2025)
  2. PEDS (Patent Examination Data System) - Patent examination history
  3. TSDR (Trademark Status & Document Retrieval) - Trademark data

What it can do on your machine

Read from SKILL.md and the folder at commit 14680ec. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • assignment-api.uspto.gov
    • search.patentsview.org
    • tsdrapi.uspto.gov

    Also links to:

    • account.uspto.gov
    • developer.uspto.gov
    • data.uspto.gov
    • pypi.org
    • docs.ip-tools.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • USPTO_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

USPTO Patent and Trademark Data loads about 4.6k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 44 tokens; SKILL.md has 1,165 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~13k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from davila7/claude-code-templates at commit 14680ec, republished under its MIT licence (© davila7). 1,165 words, ~4,623 tokens.

Download SKILL.mdSave it as .claude/skills/uspto-database/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
uspto-database
description
Access USPTO APIs for patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR, for IP analysis and prior art searches.

USPTO Database

Overview

USPTO provides specialized APIs for patent and trademark data. Search patents by keywords/inventors/assignees, retrieve examination history via PEDS, track assignments, analyze citations and office actions, access TSDR for trademarks, for IP analysis and prior art searches.

When to Use This Skill

This skill should be used when:

  • Patent Search: Finding patents by keywords, inventors, assignees, classifications, or dates
  • Patent Details: Retrieving full patent data including claims, abstracts, citations
  • Trademark Search: Looking up trademarks by serial or registration number
  • Trademark Status: Checking trademark status, ownership, and prosecution history
  • Examination History: Accessing patent prosecution data from PEDS (Patent Examination Data System)
  • Office Actions: Retrieving office action text, citations, and rejections
  • Assignments: Tracking patent/trademark ownership transfers
  • Citations: Analyzing patent citations (forward and backward)
  • Litigation: Accessing patent litigation records
  • Portfolio Analysis: Analyzing patent/trademark portfolios for companies or inventors

USPTO API Ecosystem

The USPTO provides multiple specialized APIs for different data needs:

Core APIs
  1. PatentSearch API - Modern ElasticSearch-based patent search (replaced legacy PatentsView in May 2025)

    • Search patents by keywords, inventors, assignees, classifications, dates
    • Access to patent data through June 30, 2025
    • 45 requests/minute rate limit
    • Base URL: https://search.patentsview.org/api/v1/
  2. PEDS (Patent Examination Data System) - Patent examination history

    • Application status and transaction history from 1981-present
    • Office action dates and examination events
    • Use uspto-opendata-python Python library
    • Replaced: PAIR Bulk Data (PBD) - decommissioned
  3. TSDR (Trademark Status & Document Retrieval) - Trademark data

    • Trademark status, ownership, prosecution history
    • Search by serial or registration number
    • Base URL: https://tsdrapi.uspto.gov/ts/cd/
Additional APIs
  1. Patent Assignment Search - Ownership records and transfers
  2. Trademark Assignment Search - Trademark ownership changes
  3. Enriched Citation API - Patent citation analysis
  4. Office Action Text Retrieval - Full text of office actions
  5. Office Action Citations - Citations from office actions
  6. Office Action Rejection - Rejection reasons and types
  7. PTAB API - Patent Trial and Appeal Board proceedings
  8. Patent Litigation Cases - Federal district court litigation data
  9. Cancer Moonshot Data Set - Cancer-related patents

Quick Start

API Key Registration

All USPTO APIs require an API key. Register at: https://account.uspto.gov/api-manager/

Set the API key as an environment variable:

bash
export USPTO_API_KEY="your_api_key_here"
Helper Scripts

This skill includes Python scripts for common operations:

  • scripts/patent_search.py - PatentSearch API client for searching patents
  • scripts/peds_client.py - PEDS client for examination history
  • scripts/trademark_client.py - TSDR client for trademark data

Task 1: Searching Patents

Using the PatentSearch API

The PatentSearch API uses a JSON query language with various operators for flexible searching.

Basic Patent Search Examples

Search by keywords in abstract:

python
from scripts.patent_search import PatentSearchClient

client = PatentSearchClient()

# Search for machine learning patents
results = client.search_patents({
    "patent_abstract": {"_text_all": ["machine", "learning"]}
})

for patent in results['patents']:
    print(f"{patent['patent_number']}: {patent['patent_title']}")

Search by inventor:

python
results = client.search_by_inventor("John Smith")

Search by assignee/company:

python
results = client.search_by_assignee("Google")

Search by date range:

python
results = client.search_by_date_range("2024-01-01", "2024-12-31")

Search by CPC classification:

python
results = client.search_by_classification("H04N")  # Video/image tech

Combine multiple criteria with logical operators:

python
results = client.advanced_search(
    keywords=["artificial", "intelligence"],
    assignee="Microsoft",
    start_date="2023-01-01",
    end_date="2024-12-31",
    cpc_codes=["G06N", "G06F"]  # AI and computing classifications
)
Direct API Usage

For complex queries, use the API directly:

python
import requests

url = "https://search.patentsview.org/api/v1/patent"
headers = {
    "X-Api-Key": "YOUR_API_KEY",
    "Content-Type": "application/json"
}

query = {
    "q": {
        "_and": [
            {"patent_date": {"_gte": "2024-01-01"}},
            {"assignee_organization": {"_text_any": ["Google", "Alphabet"]}},
            {"cpc_subclass_id": ["G06N", "H04N"]}
        ]
    },
    "f": ["patent_number", "patent_title", "patent_date", "inventor_name"],
    "s": [{"patent_date": "desc"}],
    "o": {"per_page": 100, "page": 1}
}

response = requests.post(url, headers=headers, json=query)
results = response.json()
Query Operators
  • Equality: {"field": "value"} or {"field": {"_eq": "value"}}
  • Comparison: _gt, _gte, _lt, _lte, _neq
  • Text search: _text_all, _text_any, _text_phrase
  • String matching: _begins, _contains
  • Logical: _and, _or, _not

Best Practice: Use _text_* operators for text fields (more performant than _contains or _begins)

Available Patent Endpoints
  • /patent - Granted patents
  • /publication - Pregrant publications
  • /inventor - Inventor information
  • /assignee - Assignee information
  • /cpc_subclass, /cpc_at_issue - CPC classifications
  • /uspc - US Patent Classification
  • /ipc - International Patent Classification
  • /claims, /brief_summary_text, /detail_description_text - Text data (beta)
Reference Documentation

See references/patentsearch_api.md for complete PatentSearch API documentation including:

  • All available endpoints
  • Complete field reference
  • Query syntax and examples
  • Response formats
  • Rate limits and best practices

Task 2: Retrieving Patent Examination Data

Using PEDS (Patent Examination Data System)

PEDS provides comprehensive prosecution history including transaction events, status changes, and examination timeline.

Installation
bash
uv pip install uspto-opendata-python
Basic PEDS Usage

Get application data:

python
from scripts.peds_client import PEDSHelper

helper = PEDSHelper()

# By application number
app_data = helper.get_application("16123456")
print(f"Title: {app_data['title']}")
print(f"Status: {app_data['app_status']}")

# By patent number
patent_data = helper.get_patent("11234567")

Get transaction history:

python
transactions = helper.get_transaction_history("16123456")

for trans in transactions:
    print(f"{trans['date']}: {trans['code']} - {trans['description']}")

Get office actions:

python
office_actions = helper.get_office_actions("16123456")

for oa in office_actions:
    if oa['code'] == 'CTNF':
        print(f"Non-final rejection: {oa['date']}")
    elif oa['code'] == 'CTFR':
        print(f"Final rejection: {oa['date']}")
    elif oa['code'] == 'NOA':
        print(f"Notice of allowance: {oa['date']}")

Get status summary:

python
summary = helper.get_status_summary("16123456")

print(f"Current status: {summary['current_status']}")
print(f"Filing date: {summary['filing_date']}")
print(f"Pendency: {summary['pendency_days']} days")

if summary['is_patented']:
    print(f"Patent number: {summary['patent_number']}")
    print(f"Issue date: {summary['issue_date']}")
Prosecution Analysis

Analyze prosecution patterns:

python
analysis = helper.analyze_prosecution("16123456")

print(f"Total office actions: {analysis['total_office_actions']}")
print(f"Non-final rejections: {analysis['non_final_rejections']}")
print(f"Final rejections: {analysis['final_rejections']}")
print(f"Allowed: {analysis['allowance']}")
print(f"Responses filed: {analysis['responses']}")
Common Transaction Codes
  • CTNF - Non-final rejection mailed
  • CTFR - Final rejection mailed
  • NOA - Notice of allowance mailed
  • WRIT - Response filed
  • ISS.FEE - Issue fee payment
  • ABND - Application abandoned
  • AOPF - Office action mailed
Reference Documentation

See references/peds_api.md for complete PEDS documentation including:

  • All available data fields
  • Transaction code reference
  • Python library usage
  • Portfolio analysis examples

Task 3: Searching and Monitoring Trademarks

Using TSDR (Trademark Status & Document Retrieval)

Access trademark status, ownership, and prosecution history.

Basic Trademark Usage

Get trademark by serial number:

python
from scripts.trademark_client import TrademarkClient

client = TrademarkClient()

# By serial number
tm_data = client.get_trademark_by_serial("87654321")

# By registration number
tm_data = client.get_trademark_by_registration("5678901")

Get trademark status:

python
status = client.get_trademark_status("87654321")

print(f"Mark: {status['mark_text']}")
print(f"Status: {status['status']}")
print(f"Filing date: {status['filing_date']}")

if status['is_registered']:
    print(f"Registration #: {status['registration_number']}")
    print(f"Registration date: {status['registration_date']}")

Check trademark health:

python
health = client.check_trademark_health("87654321")

print(f"Mark: {health['mark']}")
print(f"Status: {health['status']}")

for alert in health['alerts']:
    print(alert)

if health['needs_attention']:
    print("⚠️  This mark needs attention!")
Trademark Portfolio Monitoring

Monitor multiple trademarks:

python
def monitor_portfolio(serial_numbers, api_key):
    """Monitor trademark portfolio health."""
    client = TrademarkClient(api_key)

    results = {
        'active': [],
        'pending': [],
        'problems': []
    }

    for sn in serial_numbers:
        health = client.check_trademark_health(sn)

        if 'REGISTERED' in health['status']:
            results['active'].append(health)
        elif 'PENDING' in health['status'] or 'PUBLISHED' in health['status']:
            results['pending'].append(health)
        elif health['needs_attention']:
            results['problems'].append(health)

    return results
Common Trademark Statuses
  • REGISTERED - Active registered mark
  • PENDING - Under examination
  • PUBLISHED FOR OPPOSITION - In opposition period
  • ABANDONED - Application abandoned
  • CANCELLED - Registration cancelled
  • SUSPENDED - Examination suspended
  • REGISTERED AND RENEWED - Registration renewed
Show full SKILL.md (463 more words)Show less
Reference Documentation

See references/trademark_api.md for complete trademark API documentation including:

  • TSDR API reference
  • Trademark Assignment Search API
  • All status codes
  • Prosecution history access
  • Ownership tracking

Task 4: Tracking Assignments and Ownership

Patent and Trademark Assignments

Both patents and trademarks have Assignment Search APIs for tracking ownership changes.

Patent Assignment API

Base URL: https://assignment-api.uspto.gov/patent/v1.4/

Search by patent number:

python
import requests
import xml.etree.ElementTree as ET

def get_patent_assignments(patent_number, api_key):
    url = f"https://assignment-api.uspto.gov/patent/v1.4/assignment/patent/{patent_number}"
    headers = {"X-Api-Key": api_key}

    response = requests.get(url, headers=headers)
    if response.status_code == 200:
        return response.text  # Returns XML

assignments_xml = get_patent_assignments("11234567", api_key)
root = ET.fromstring(assignments_xml)

for assignment in root.findall('.//assignment'):
    recorded_date = assignment.find('recordedDate').text
    assignor = assignment.find('.//assignor/name').text
    assignee = assignment.find('.//assignee/name').text
    conveyance = assignment.find('conveyanceText').text

    print(f"{recorded_date}: {assignor} → {assignee}")
    print(f"  Type: {conveyance}\n")

Search by company name:

python
def find_company_patents(company_name, api_key):
    url = "https://assignment-api.uspto.gov/patent/v1.4/assignment/search"
    headers = {"X-Api-Key": api_key}
    data = {"criteria": {"assigneeName": company_name}}

    response = requests.post(url, headers=headers, json=data)
    return response.text
Common Assignment Types
  • ASSIGNMENT OF ASSIGNORS INTEREST - Ownership transfer
  • SECURITY AGREEMENT - Collateral/security interest
  • MERGER - Corporate merger
  • CHANGE OF NAME - Name change
  • ASSIGNMENT OF PARTIAL INTEREST - Partial ownership

Task 5: Accessing Additional USPTO Data

Office Actions, Citations, and Litigation

Multiple specialized APIs provide additional patent data.

Office Action Text Retrieval

Retrieve full text of office actions using application number. Integrate with PEDS to identify which office actions exist, then retrieve full text.

Enriched Citation API

Analyze patent citations:

  • Forward citations (patents citing this patent)
  • Backward citations (prior art cited)
  • Examiner vs. applicant citations
  • Citation context
Patent Litigation Cases API

Access federal district court patent litigation records:

  • 74,623+ litigation records
  • Patents asserted
  • Parties and venues
  • Case outcomes
PTAB API

Patent Trial and Appeal Board proceedings:

  • Inter partes review (IPR)
  • Post-grant review (PGR)
  • Appeal decisions
Reference Documentation

See references/additional_apis.md for comprehensive documentation on:

  • Enriched Citation API
  • Office Action APIs (Text, Citations, Rejections)
  • Patent Litigation Cases API
  • PTAB API
  • Cancer Moonshot Data Set
  • OCE Status/Event Codes

Complete Analysis Example

Comprehensive Patent Analysis

Combine multiple APIs for complete patent intelligence:

python
def comprehensive_patent_analysis(patent_number, api_key):
    """
    Full patent analysis using multiple USPTO APIs.
    """
    from scripts.patent_search import PatentSearchClient
    from scripts.peds_client import PEDSHelper

    results = {}

    # 1. Get patent details
    patent_client = PatentSearchClient(api_key)
    patent_data = patent_client.get_patent(patent_number)
    results['patent'] = patent_data

    # 2. Get examination history
    peds = PEDSHelper()
    results['prosecution'] = peds.analyze_prosecution(patent_number)
    results['status'] = peds.get_status_summary(patent_number)

    # 3. Get assignment history
    import requests
    assign_url = f"https://assignment-api.uspto.gov/patent/v1.4/assignment/patent/{patent_number}"
    assign_resp = requests.get(assign_url, headers={"X-Api-Key": api_key})
    results['assignments'] = assign_resp.text if assign_resp.status_code == 200 else None

    # 4. Analyze results
    print(f"\n=== Patent {patent_number} Analysis ===\n")
    print(f"Title: {patent_data['patent_title']}")
    print(f"Assignee: {', '.join(patent_data.get('assignee_organization', []))}")
    print(f"Issue Date: {patent_data['patent_date']}")

    print(f"\nProsecution:")
    print(f"  Office Actions: {results['prosecution']['total_office_actions']}")
    print(f"  Rejections: {results['prosecution']['non_final_rejections']} non-final, {results['prosecution']['final_rejections']} final")
    print(f"  Pendency: {results['prosecution']['pendency_days']} days")

    # Analyze citations
    if 'cited_patent_number' in patent_data:
        print(f"\nCitations:")
        print(f"  Cites: {len(patent_data['cited_patent_number'])} patents")
    if 'citedby_patent_number' in patent_data:
        print(f"  Cited by: {len(patent_data['citedby_patent_number'])} patents")

    return results

Best Practices

  1. API Key Management

    • Store API key in environment variables
    • Never commit keys to version control
    • Use same key across all USPTO APIs
  2. Rate Limiting

    • PatentSearch: 45 requests/minute
    • Implement exponential backoff for rate limit errors
    • Cache responses when possible
  3. Query Optimization

    • Use _text_* operators for text fields (more performant)
    • Request only needed fields to reduce response size
    • Use date ranges to narrow searches
  4. Data Handling

    • Not all fields populated for all patents/trademarks
    • Handle missing data gracefully
    • Parse dates consistently
  5. Combining APIs

    • Use PatentSearch for discovery
    • Use PEDS for prosecution details
    • Use Assignment APIs for ownership tracking
    • Combine data for comprehensive analysis

Important Notes

  • Legacy API Sunset: PatentsView legacy API discontinued May 1, 2025 - use PatentSearch API
  • PAIR Bulk Data Decommissioned: Use PEDS instead
  • Data Coverage: PatentSearch has data through June 30, 2025; PEDS from 1981-present
  • Text Endpoints: Claims and description endpoints are in beta with ongoing backfilling
  • Rate Limits: Respect rate limits to avoid service disruptions

Resources

API Documentation
Python Libraries
Reference Files
  • references/patentsearch_api.md - Complete PatentSearch API reference
  • references/peds_api.md - PEDS API and library documentation
  • references/trademark_api.md - Trademark APIs (TSDR and Assignment)
  • references/additional_apis.md - Citations, Office Actions, Litigation, PTAB
Scripts
  • scripts/patent_search.py - PatentSearch API client
  • scripts/peds_client.py - PEDS examination data client
  • scripts/trademark_client.py - Trademark search client

© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts, references) in cli-tool/components/skills/scientific/uspto-database of davila7/claude-code-templates.

  • SKILL.md
  • references/additional_apis.md
  • references/patentsearch_api.md
  • references/peds_api.md
  • references/trademark_api.md
  • scripts/patent_search.py
  • scripts/peds_client.py
  • scripts/trademark_client.py

Open the folder on GitHubat commit 14680ec

Used in 12 other repositories

We found 15 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 12 other GitHub owners. This page covers the copy in davila7/claude-code-templates, which our catalogue first saw on October 7, 2026.

Compare with similar skills

USPTO Patent and Trademark Data next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

USPTO Patent and Trademark Data compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
USPTO Patent and Trademark Data this skilldavila7/claude-code-templates32k12 repos~4.6kAutomated safety check: PassMIT
Tw Legal RAGaa0101181514/tw-legal-rag327—~580Automated safety check: PassCustom licence
Hard Predict Futuredavepoon/buildwithclaude3.6k1 repos~4.2kAutomated safety check: PassMIT
Moot Court Simulation Buildercat-xierluo/legal-skills713—~1.4kAutomated safety check: PassCC-BY-NC-4.0
Claim ChartZekaiSuni/claude-for-legal-turkish107—~719Automated safety check: PassApache-2.0
Patent Downloadcat-xierluo/legal-skills7131 repos~951Automated safety check: NotesMIT

Similar skills

  • Tw Legal RAG

    aa0101181514/tw-legal-rag

    Retrieve real Taiwan court judgments with verifiable citations before answering any question about Taiwan law or case law.

    327 GitHub stars~580 tokensUpdated 4 days ago
    Legal & ComplianceAuto-check passed
  • Hard Predict Future

    davepoon/buildwithclaude

    Activate this agent for any future-oriented question that requires deep quantitative analysis, historical precedents, and structured scenario planning.

    3.6k GitHub starsUsed in 1 repo~4.2k tokens
    Legal & ComplianceAuto-check passed
  • Moot Court Simulation Builder

    cat-xierluo/legal-skills

    Chinese-language skill that organizes a case file into a multi-role mock trial with judge, parties and clerk, producing a transcript, issue review and a to-strengthen list.

    713 GitHub stars~1.4k tokensUpdated yesterday
    Legal & ComplianceAuto-check passed
  • Claim Chart

    ZekaiSuni/claude-for-legal-turkish

    Build or review an element chart. An agent skill from ZekaiSuni/claude-for-legal-turkish.

    107 GitHub stars~719 tokensUpdated 4 mo ago
    Legal & ComplianceAuto-check passed
  • Patent Download

    cat-xierluo/legal-skills

    专利 PDF 批量下载工具。当用户需要下载专利全文 PDF、查询专利信息、批量导出专利文件时使用。支持多平台(Google Patents 优先),自动处理申请号和公告号格式。

    713 GitHub starsUsed in 1 repo~951 tokens
    Legal & ComplianceAuto-check: notes
  • Mpep Search

    RobThePCGuy/Claude-Patent-Creator

    Expert system for searching USPTO MPEP, 35 USC statutes, 37 CFR regulations, and post-Jan 2024 updates.

    196 GitHub stars~978 tokensUpdated 2 days ago
    Legal & ComplianceAuto-check passed

More from davila7/claude-code-templates

All 477 skills in this repo
  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    32k GitHub starsUsed in 12 repos~3.5k tokens
    Auto-check: notes
  • Neuropixels Data Analysis

    davila7/claude-code-templates

    Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.

    32k GitHub starsUsed in 10 repos~2.8k tokens
    Auto-check passed
  • Scientific Venue Templates

    davila7/claude-code-templates

    Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.

    32k GitHub starsUsed in 9 repos~5.1k tokens
    Auto-check: notes
  • Brand Voice Content Creator

    davila7/claude-code-templates

    Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.

    32k GitHub starsUsed in 3 repos~1.9k tokens
    Auto-check passed
  • CAPA Officer

    davila7/claude-code-templates

    Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.

    32k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Fda Consultant Specialist

    davila7/claude-code-templates

    Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.

    32k GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed

Works with

Questions about USPTO Patent and Trademark Data

What does USPTO Patent and Trademark Data do?

Searches USPTO patent and trademark data through its APIs: patent search, PEDS examination history, assignments, citations, office actions and TSDR status. The skill covers the USPTO's APIs for patents and trademarks. The core ones are PatentSearch, an ElasticSearch-based search by keyword, inventor, assignee, classification or date; PEDS, for application status and transaction history from 1981 onward, used through the `uspto-opendata-python` library; and TSDR, for trademark status, ownership and prosecution history by serial or registration number.

When should I use USPTO Patent and Trademark Data?

USPTO Patent and Trademark Data fits situations like: searching patents by keyword, inventor, assignee or classification; checking the status and ownership history of a trademark; pulling examination history and office actions for a patent application; analyzing a company's patent portfolio or citations for a prior art search.

How do I install USPTO Patent and Trademark Data in Claude Code?

Run `npx skills add davila7/claude-code-templates --skill uspto-database -a claude-code`. Or copy the skill folder (cli-tool/components/skills/scientific/uspto-database in davila7/claude-code-templates) into .claude/skills/uspto-database in your project. Claude Code loads it when a task matches its description.

How do I install USPTO Patent and Trademark Data in Codex?

Run `npx skills add davila7/claude-code-templates --skill uspto-database -a codex`. Or copy the skill folder (cli-tool/components/skills/scientific/uspto-database in davila7/claude-code-templates) into .agents/skills/uspto-database in your project. Codex loads it when a task matches its description.

Can I use USPTO Patent and Trademark Data in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill uspto-database -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/uspto-database, .gemini/skills/uspto-database, .github/skills/uspto-database and .opencode/skills/uspto-database in your project.

What does USPTO Patent and Trademark Data need to run?

Going by SKILL.md and its folder, USPTO Patent and Trademark Data needs Python for the scripts in its folder, the command-line tools its instructions call (uv) and credentials named USPTO_API_KEY. Our summary lists: Python; Network access to the USPTO APIs.

Does USPTO Patent and Trademark Data access the network?

SKILL.md names 8 domains. In commands or code: assignment-api.uspto.gov, search.patentsview.org and tsdrapi.uspto.gov; the agent is likely to contact these when it follows the instructions. As links in the text: account.uspto.gov, developer.uspto.gov, data.uspto.gov, pypi.org and docs.ip-tools.org. This is read from the text; nothing was executed.

Is USPTO Patent and Trademark Data safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does USPTO Patent and Trademark Data use?

USPTO Patent and Trademark Data is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does USPTO Patent and Trademark Data use?

About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.4k tokens, read only when the agent opens those files.

What are the alternatives to USPTO Patent and Trademark Data?

Skills that share tags, products or a category with USPTO Patent and Trademark Data: Tw Legal RAG (aa0101181514/tw-legal-rag, 327 stars), Hard Predict Future (davepoon/buildwithclaude, 3.6k stars), Moot Court Simulation Builder (cat-xierluo/legal-skills, 713 stars) and Claim Chart (ZekaiSuni/claude-for-legal-turkish, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains USPTO Patent and Trademark Data?

davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,463 GitHub stars. The repository holds 477 skills in this directory. The repository was last updated on October 8, 2026.

Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.