What problem it solves

Engineers and inventors often have design documents and code but no structured way to identify patentable points, draft disclosure documents, or assemble application files. Public patent texts are also hard to read: claims are convoluted, terminology is dense, and the practical context is scattered across descriptions and drawings. The skill set addresses both sides of this gap.

Key features

• Disclosure drafting for invention, utility model and design — Project materials are turned into protectable points, prior-art checks, and a deliverable disclosure document, with iteration saved as new versions and diagrams that can be edited.

  Source: README, docs

• Application documents and docket drafting — An existing disclosure can be rewritten into claims, specification, abstract and drawings, while a separate docket workflow plays the roles of disclosure engineer and patent agent and asks for missing facts instead of inventing them.

  Source: README, SKILL.md

• Plain-language patent reading into a private knowledge base — A publication number or PDF is turned into readable notes and diagrams that are filed into Obsidian, so multiple interpreted patents can be linked with terms, clues and drawings into a personal knowledge base.

  Source: README, skills

• Patent map exploration from accumulated cases — Cases collected through interpretation are laid out as semantic terrain, applicant quadrants, family and citation networks, a technology-effect matrix and a dashboard, running locally and opened in a browser.

  Source: README, scripts

• Search, examination response and policy briefs — Beyond drafting, the skills cover bibliographic and image/claim-based search, drafting responses to examination opinions, building claim charts, and summarizing recent CNIPA policy messages in plain language.

  Source: README

Who it may suit

Inference: this may suit engineers, inventors and patent practitioners who need to turn project materials into disclosure and application documents, and who want a local, Obsidian-based workflow for reading and comparing patents.

Topics to discuss

• How should the disclosure workflow balance generating protectable points automatically against requiring human review before filing?

• Which Obsidian-based data structures best support comparing patent families and citation networks over time?

• How can the policy brief sub-skill detect when drafting templates need updating after changes in examination practice?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/handsomestWei/patent-disclosure-skill#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.