Important Statement (remind at the beginning every time)
The output of this skill isdrafts and auxiliary organization, and does not constitute legal advice. The final text of software copyright/patent must be reviewed by a professional agent or legal personnel; materials must not be fabricated or exaggerated (linked to a10).
Software Copyright (registration authority: Copyright Protection Center of China CPCC, ccopyright.com)
Software copyright only performsformal registration, does not examine code quality/novelty, and confirms ownership and completion time.
- Software naming: full name + abbreviation + version number, standardized and registrable, reflecting functions; it is inconvenient to change after registration, so confirm before finalizing.
- Function description: software purpose, main function modules, operating environment, technical features.
- Operation manual: installation, configuration, operation steps for each function, with interface screenshots and function module description.
- Source code organization: first 30 pages + last 30 pages (continuous, about 50 lines per page; if fewer than 60 pages, submit all), header contains full name + version, comments desensitized——For the single source of truth for the rules, see db08
databases/db08-ip-materials/resources_real.md§2 (with last_checked + CPCC guideline source_pointer), before submission verify the page count/line count criteria against the current CPCC guideline; scriptscripts/copyright_source_prep.pygenerates the submission text according to these rules. - Document: user manual or design specification, the first 30 pages + last 30 pages rule is the same as for source code.
- Materials checklist verification: registration application form (generated by the system), source program, document, identity/business license, ownership proof (corresponding proof required for cooperative/commissioned/service development).
- Key information: development completion date, first publication date (can be noted if unpublished), version number, development method (independent/cooperative/commissioned/service), ownership of rights.
- Process and cycle: fill in the online registration system→submit→acceptance→examination (statutory about 30 working days, paid expedited processing available)→issue the Computer Software Copyright Registration Certificate. Materials must correspond truthfully and must not be pieced together or fabricated. For templates and examination focus, see db08.
Patent
- Preliminary judgment of patentability: whether it belongs to an invention/utility model/design; preliminary judgment of novelty, inventiveness, and utility; conduct a novelty search (see below).
- Technical disclosure organization: technical problem to be solved → defects of prior art → technical solution of the present invention → beneficial effects → innovation points.
- Draft claims：
- An independent claim recordsall essential technical featuresthat solve the problem, constituting the maximum scope of protection.Choose one of the two drafting methods, do not mix them(the template claims_template.md provides two correct paradigms + warnings about common errors): ①single-part method(The solution as a whole is new, with no clearly closest prior art) "A ... method, comprising: S1 ... S3",do not write "characterized in that"；②two-part form(improved type) "A ... method, comprising [preamble: features shared with the prior art]; characterized in that, [characterizing part: only the distinguishing features]".The most common fatal error: cramming shared features into the part after "characterized in that", or forcibly adding "characterized in that" in the single-part form — the patent attorney will reject it outright.
- Dependent claims use "The ... according to claim N, characterized in that ..." to add limitations layer by layer; when referencing multiple claims use "or", and a claim must not reference a claim with a higher number.
- A commonly used combined layout for software inventions: method + apparatus/system + computer-readable storage medium.
- mustbe supported by the description; avoid functional/vague wording ("about", "approximately"); keep terminology consistent throughout; multiple independent claims must belong to the same general inventive concept (unity).
- Description Draft(mustsufficiently disclose, enabling a person skilled in the art to implement it), in the order of the Examination Guidelines: technical field → background technology (current state + comparison documents + objective defects) → summary of the invention (technical problem/technical solution/beneficial effects, with effects quantified where possible or with a mechanism given) → description of drawings (each figure + list of reference signs) → specific embodiments (≥1 embodiment; for software, provide process/module interaction/pseudocode-level description so that the solution can be reproduced). Every claim feature must find support in the description.
- Drawings: flowcharts/structural diagrams/schematic diagrams, drawn by m11 in accordance with patent drawing standards — for specific standards (figure numbering arrangement, reference sign lines not crossing, black-and-white line drawings as the principle with no coloring, flowcharts/block diagrams corresponding to claim terminology) see m11(light-figure-drawing)
references.md"Patent Drawing Standards" section. Patent drawings follow the black-and-white vector line pipeline, and do not adopt the color schemes/styles of paper data figures.Method flowcharts/apparatus structural block diagrams can use Draw.io MCP to produce diagram-as-code (.drawioi.e., XML, black-and-white lines, programmatically generatable, convenient for repeatedly revising the draft according to the agent's comments, and exportable as vectors), which exactly meets patent drawing requirements; after output, still check against the above standards (reference sign lines, terminology consistent with the claims). For configuration see the recommended MCP table in the README.
Practical Guide to Novelty Search (Prior Art)
Select a search system according to the data scope (for item-by-item hard information on endpoints/field codes/authentication/rate limiting see references.md, here only selection guidance is given）：
| Scope | System | Key Points |
|---|---|---|
| Chinese patents (authoritative) | CNIPA Patent Search and Analysis | Free but requires login, no public API, advanced fields + legal status filtering |
| Global free | Google Patents | URL parameter search; for large-scale use, use BigQuery public datasets |
| PCT/cross-lingual | WIPO PATENTSCOPE | Field codes + CLIR, search foreign-language prior art in Chinese |
| European machine-readable | EPO OPS API | OAuth2 + CQL, traffic-light throttling |
| Patents ↔ papers | The Lens API | Patents and academic literature integrated, free authorization available |
| United States | USPTO（data.uspto.gov） | PatentSearch API, endpoint has migrated to ODP |
| Non-patent literature | OpenAlex | Supplements paper-type prior art (for access specifications see m01) |
Script capability boundaries (honest declaration, to avoid reading it as "all seven sources can be queried programmatically"): In the table above,
scripts/patent_search.pythe only one that can trulyretrieve data programmaticallyis OpenAlex (paper-type NPL, not a patent database); the The Lens / EPO OPS / USPTO ODP scripts onlyconstruct request bodies(they require your own credentials to initiate; without credentials, tested 401);CNIPA / Google Patents / WIPO PATENTSCOPE have no scripts and require manual web login or BigQuery search. That is, real prior art searches in patent databases still rely mainly on manual web pages/institutional accounts; the scripts are NPL supplements + request scaffolding when credentials are available.
- Search evidence (hit document numbers/dates/relevant passages) is archived with the disclosure; FTO/invalidity conclusions must be determined by a patent agent/lawyer, and this skill does not draw legal conclusions.
Runnable assets (scripts/ and templates/, all verified with python runs/curl tests)
scripts/patent_search.py: prior art search assistance. OpenAlex/worksdoes NPL (non-patent literature) search(from 2026 a free key is required, passed through via--api-key/environment variableOPENALEX_API_KEY, access specifications see m01 source of truth;per_pagelimit 200), and for The Lens / EPO OPS / USPTO ODP constructs request bodies(these three require your own credentials; all tested 401 = authentication required).Note: the scripts themselves do not directly query patent databases; actual patent database searches must be done manually on the web or initiated with credentials (see "Script capability boundaries" above).python scripts/patent_search.py "关键词" --from-year 2015 --per-page 10 --mailto you@x.com --api-key $OPENALEX_API_KEYpython scripts/patent_search.py --print-adapters(prints patent database request templates)python scripts/patent_search.py "关键词" --free-urls --cpc H01M --before 2020-01-01(main novelty search path without an API key: generates "click-to-use" advanced search links for CNIPA pss-system / Google Patents / Lens / WIPO, with Google Patents carrying before:priority to pin the priority date and CPC narrowing—filling the gap of being unable to obtain patent database results without credentials)python scripts/patent_search.py --selftest(offline self-test, no network)
scripts/copyright_source_prep.py: software copyright source code material preparation. Generates submission text according to the rules "50 lines/page, ≤60 pages submit all otherwise first 30 + last 30 pages, header contains full name + version, comments desensitized".Desensitization covers emails/mobile numbers/secret assignments/PEM private keys/IPv4/long base64-hex strings; at the end of output reports the hit count + explicitly states "regex coarse screening only, completeness not guaranteed, manual review required"(does not give the illusion of "thoroughly desensitized"); page count additionally reports "effective code line count" (excluding FILE marker lines/blank lines, to avoid inflated page counts misjudging whether 60 pages are enough).python scripts/copyright_source_prep.py --src <代码目录> --name "全称" --version V1.0 --out submit_source.txtpython scripts/copyright_source_prep.py --selftest
templates/disclosure_template.md: technical disclosure template.templates/claims_template.md: claims draft (method + apparatus + medium combination layout).templates/specification_template.md: specification draft (in Examination Guidelines order).templates/copyright_checklist.md: software copyright material checklist.
Outputs
Software copyright: full set of draft materials (set templates/copyright_checklist.md) + source code preparation (copyright_source_prep.py) + screenshot preparation suggestions.
Patent: patentability analysis + disclosure (disclosure_template.md) + claims draft (claims_template.md) + specification draft (specification_template.md) + search evidence (patent_search.py) + drawing list + "requires agent review" annotation.
Persisted artifact names (CONVENTIONS §6.1, downstream orchestrator/a08 schedules by name): patent ip/disclosure_draft.md + ip/claims_draft.md + ip/specification_draft.md; software copyright ip/copyright_package/。
Interfaces
Technical content is taken from m05/a03/a04/m07; the software copyright functional description and the patent background technology/summary of the invention can reuse the corresponding paragraphs of the paper (m07)—the patent's "technical problem to be solved/beneficial effects" are highly homologous with the paper's Introduction/Results, and the software copyright functional description can also draw on the paper's methods and results paragraphs. Figures are handed over to m11 (for patent figure specifications see the "Patent Figure Specifications" section in m11 references; black-and-white line drawings + figure number marking specifications); keep consistent with the paper/system (a07); materials go into db09. Retrieval and ownership risks are reported to a10. Before delivery, pass the a08 (light-self-review) self-check gate.
For the real endpoints/parameters of retrieval tools, key points of drafting specifications, and known pitfalls, see references.md.