Skip to content

nexscope-ai/nexscope-ecommerce-skills / ecommerce-patent-detailed-bibliography

ecommerce.patent-detailed-bibliography

Verified

Query patent bibliographic (catalog) information from the Nexscope patent database by patent ID or publication number. Triggered when users mention patent bibliographic info queries, patent catalog information, patent applicant queries, patent inventor queries, patent classification codes, patent abstract retrieval, patent citation analysis, patent priority claims, patent application citations, patent examiner information, patent bibliographic data, inventor lookup, applicant lookup, patent classification, patent metadata, Nexscope, or patent citations. Even if the user does not explicitly mention "bibliographic info," this skill should be triggered whenever their need involves querying detailed metadata for a specific patent by patent ID or publication number.

Nexscope Patent Bibliography

This skill guides you on how to query patent bibliography (bibliographic) data from the Nexscope patent database, helping users retrieve detailed metadata for specific patents.

Core Concepts

Patent bibliography data (also called bibliographic data) is the structured metadata associated with a patent document. It includes the patent title, applicants, inventors, classification codes, priority claims, cited references, abstracts, and more. This tool allows querying by patent ID or publication number, returning comprehensive bibliographic records for one patent per Skill call.

Patent types: The patentType field indicates the type of patent document:

  • APPLICATION -- Invention application (published but not yet granted)
  • PATENT -- Granted invention patent
  • UTILITY -- Utility model
  • DESIGN -- Design patent

Data Fields

FieldAPI NameDescription
Patent IDpatentIdInternal patent identifier
Publication NumberpnPublication/announcement number
Invention TitleinventionTitlePatent title with language info
AbstractsabstractsPatent abstract text
Patent TypepatentTypeAPPLICATION, PATENT, UTILITY, or DESIGN
ApplicantsapplicantsOriginal applicant(s)
AssigneesassigneesCurrent patent holder(s) / assignee(s)
InventorsinventorsInventor(s) listed on the patent
AgentsagentsPatent attorney / agent(s)
AgencyagencyFiling agency / patent firm
ExaminersexaminersPatent examiner(s)
Priority ClaimspriorityClaimsPriority right declarations
Application ReferenceapplicationReferenceApplication filing data
Publication ReferencepublicationReferencePublication data
Dates of Public AvailabilitydatesOfPublicAvailabilityPublic availability dates
IPC ClassificationclassificationIpcrInternational Patent Classification
CPC ClassificationclassificationCpcCooperative Patent Classification
UPC ClassificationclassificationUpcUS Patent Classification
LOC ClassificationclassificationLocLocarno Classification (designs)
FI ClassificationclassificationFiFI classification codes (Japan)
F-term ClassificationclassificationFtermF-term codes (Japan)
GBC ClassificationclassificationGbcGBC classification
Cited PatentsreferenceCitedPatentsPatent documents cited as references
Cited Non-Patent LiteraturereferenceCitedOthersNon-patent literature cited
Related DocumentsrelatedDocumentsDivisional / continuation application info
PCT Filing DatapctOrRegionalFilingDataPCT or regional phase filing data
PCT Publishing DatapctOrRegionalPublishingDataPCT or regional phase publication data
Estimated Expiry DateexdtEstimated patent expiration date (Nexscope)

Invocation

  • API Endpoint: POST /zhihuiya/bibliography (full parameters/response/error codes in references/api.md)
  • Python Script: python scripts/patent_detailed_bibliography.py '<JSON params>' [--inline]
  • Cost Constraints: This tool consumes credits. The same parameter combination defaults to a single call per session. The script includes a 24-hour local cache. Do not automatically retry with different keywords, pagination, or modified parameters on failure or empty results; inform the user that additional costs will be incurred before continuing to search. Skill single-patent policy: This endpoint consumes credits. This Skill sends one patent per call to control credits; obtain explicit consent before separate calls for multiple patents.

Output Strategy (default script behavior):

  • Always write the full response to <cwd>/nexscope/<YYYY-MM-DD>/<session>/data/nexscope-zhihuiya-bibliography-<timestamp>.json (<cwd> is the working directory at script execution time, which in Claude Code is the current project directory; <session> is taken from the SESSION_ID environment variable, auto-grouped by user task; writing to /tmp is forbidden -- error if the current directory is not writable)
  • Response body <= 8 KB: print the full JSON to stdout after writing to disk
  • Response body > 8 KB: print only a summary to stdout after writing to disk (top-level fields, common counts like total/costToken, length of the largest list field + first 3 samples)
  • Add --inline to force full output to stdout (still writes to disk)

Data Reading Tip: Check the summary first to determine if it is sufficient; when specific fields are needed, prefer using jq or ConvertFrom-Json to extract from the saved JSON file on demand to avoid loading the entire JSON into context.

Authentication

Set NEXSCOPE_API_KEY. Visit https://www.nexscope.ai/help/skills-external-access?co-from=skillNS to manage credits.

Parameter Guide

The tool accepts two parameters. At least one must be provided; if both are supplied, patentId takes priority.

ParameterWhen to UseFormat
patentIdWhen the user provides an internal Nexscope patent IDThis Skill sends one patent ID per call; the gateway accepts comma-separated IDs.
patentNumberWhen the user provides a publication/announcement numberThis Skill sends one publication number per call; the gateway accepts comma-separated numbers.

Tips for Identifying Input Type

  • If the user provides something like US10123456B2, CN112345678A, EP3456789B1, or WO2023123456A1, treat it as a publication number and use patentNumber.
  • If the user provides a purely numeric or opaque identifier that does not match standard publication number patterns, treat it as a patent ID and use patentId.
  • This Skill sends one patent per call to control credits. For multiple patents, obtain explicit consent before separate calls; the gateway accepts comma-separated identifiers.

Usage Examples

1. Look up a single patent by publication number

User: "Show me the bibliography for US10123456B2"
Action: Call with patentNumber = "US10123456B2"

2. Look up a patent by internal ID

User: "Query bibliography for patent ID 8fa3b2c1-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
Action: Call with patentId = "8fa3b2c1-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

Display Rules

  1. Present data clearly: Show query results in well-structured tables or organized sections. For each patent, highlight the most commonly needed fields: title, applicants/assignees, inventors, filing/publication dates, classification codes, and abstract.
  2. Respect the query scope: Only display the fields the user asked about. If they asked for "inventors", do not dump the entire bibliography unless requested.
  3. Patent type labels: Translate patentType codes into human-readable labels (APPLICATION = Invention Application, PATENT = Granted Invention, UTILITY = Utility Model, DESIGN = Design Patent).
  4. Single-patent results: Results contain a single patent's data; present it clearly.
  5. Error handling: When a query returns an error or empty results, explain clearly and suggest the user verify their patent ID or publication number.
  6. No subjective analysis: Present factual bibliographic data without speculative legal or commercial interpretations.

User Expression & Scenario Quick Reference

Applicable -- Patent bibliography / metadata lookups:

User SaysScenario
"Look up patent info for XX"Single patent bibliography
"Who are the inventors of patent XX"Inventor lookup
"Who owns patent XX", "current assignee"Assignee / applicant query
"What IPC/CPC class is patent XX"Classification lookup
"Show me the abstract of patent XX"Abstract retrieval
"What patents does XX cite"Citation analysis
"When does patent XX expire"Expiry date query
"Patent details", "patent metadata"General bibliography

Not applicable -- Needs beyond patent bibliography:

  • Full-text patent search by keyword or semantic query
  • Patent landscape / analytics reports
  • Patent valuation or legal status tracking
  • Freedom-to-operate or infringement analysis
  • Patent family tree exploration (unless specific publication numbers are given)

Boundary judgment: When users say "find patents about X" or "search for patents in field Y", that is a patent search task, not a bibliography lookup. This skill only applies when the user already has a patent ID or publication number and wants to retrieve its metadata.

API Key request rate

All Nexscope API Keys belonging to the same user share one request-rate allowance for public API execution. The allowance is measured over any rolling 1-second window. Your RPS depends on your account entitlements; do not assume every user has a fixed 1 RPS. A single Skill operation may make multiple public API requests, and each request uses this allowance.

If an execution request returns HTTP 429 with outer code 13012, the request-rate allowance was exceeded. Honor the returned Retry-After before considering another request. Outer code 13013 means the concurrent-request limit was exceeded, not the rate limit; honor its Retry-After when supplied. Inspect the response and reconcile state before retrying. Never automatically replay a write operation or a request whose outcome is unclear.

deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall