affaan-m/ecc

scientific-db-uspto-database

USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/affaan-m/ecc --skill scientific-db-uspto-database

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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 prosecution documents:

  • Start with ODP Patent File Wrapper search.
  • Use exact identifiers when available: application number, publication number,

patent number, or party name.

  • Record whether the record is a granted patent, pre-grant publication, or

pending application.

  • Cross-check document dates and status against the record detail page before

citing them.

Assignment Workflow

For patent or trademark ownership:

  1. Search official assignment data by patent/application/registration number,

assignor, assignee, or reel/frame when available.

  1. Record conveyance text, execution date, recordation date, and parties.
  2. Distinguish assignment records from current legal ownership conclusions.
  3. If ownership is material, flag the result for attorney or subject-matter

review.

Reproducible Output

Every USPTO research pass should include a log table:

markdown
| Source | Date searched | Identifier/query | Filters | Results | Notes |
| --- | --- | --- | --- | ---: | --- |
| PatentSearch | 2026-05-11 | `assignee=Alphabet AND date>=2024` | patent endpoint | 118 | API docs checked before run |
| TSDR | 2026-05-11 | `serial=90000000` | status only | 1 | API-key flow, no document bulk pull |

For final writeups, separate:

  • official record facts
  • inferred analysis
  • secondary-source convenience matches
  • unresolved gaps or records that require legal review

Review Checklist

  • Did you use an official USPTO or USPTO-supported source first?
  • Did you verify current endpoint and field names before running code?
  • Are API keys kept out of files, shell history, and output logs?
  • Does the query log include the date searched and exact request shape?
  • Are rate limits respected?
  • Are legal conclusions avoided or explicitly escalated?
  • Are secondary sources labeled as secondary?

References

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
affaan-m
커뮤니티

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

1시간 설치 수
3
GitHub Stars
29.6만
업데이트
11월 2일
affaan-m
커뮤니티

benchmark

Measure performance baselines and detect regressions across browser Core Web Vitals (LCP, INP, CLS, page weight), API endpoint latency percentiles, and build/test feedback times, with before/after comparison stored in git-tracked .ecc/benchmarks JSON. Use when checking page speed, responding to 'it feels slow' reports, verifying launch performance targets, or comparing stack alternatives.

1시간 설치 수
3
GitHub Stars
29.4만
업데이트
10월 30일
affaan-m
커뮤니티

benchmark-methodology

Score a scoped competitor set into comparable profile cards: nine weighted dimensions (positioning, voice, visual craft, offer packaging, evidence, enterprise-readiness, thought leadership, pricing, client tension) with 1-5 evidence-anchored rubrics and a tension 2x2 plot. Use when benchmarking or scoring competitors, building a competitive comparison matrix, or grading rival positioning before assembling the report; runs after competitive-platform-analysis and before competitive-report-structur

1시간 설치 수
3
GitHub Stars
29.4만
업데이트
10월 30일
affaan-m
커뮤니티

benchmark-optimization-loop

Convert 'make it faster' requests into a bounded measured optimization loop — baseline first, generate one-hypothesis variants, benchmark each against a correctness gate, and promote the fastest safe variant with reproducible commands. Use when asked to speed something up, try many variants, run recursive optimization, benchmark latency/throughput/cost, or pick the best implementation by repeated measured tests.

1시간 설치 수
3
GitHub Stars
29.4만
업데이트
10월 30일