nature-paper-to-patent

Name: nature-paper-to-patent
Author: Yuan1z0825

1.9kinstalls1.8kforks

How to install nature-paper-to-patent?

yuan1z0825/nature-skills/nature-paper-to-patent

$npx -y skills add Yuan1z0825/nature-skills --skill nature-paper-to-patent

Installs into the current project.

Summary

Convert scientific papers, theses, technical reports, source code, figures, inventor notes, or research manuscripts into evidence-grounded Chinese invention patent drafts and attorney-facing technical disclosure materials. Use when an AI agent must mine patent points, draft or re

Files · 1

View on GitHub

SKILL.md

1	# Paper to Chinese Patent
2
3	Use this file as the router for the patent-drafting workflow. Do not draft the
4	application directly from the paper abstract or contribution list.
5
6	## 1. Load the workflow
7
8	Read `manifest.yaml`, then read every file under `always_load`.
9
10	Detect these axes from the user's files and request:
11
12	- `source_format`: selectable PDF, scanned PDF, pasted text, or mixed project;
13	- `task_mode`: full draft, claim set, disclosure analysis, technical
14	disclosure, disclosure iteration, or paper-patent audit;
15	- `invention_type`: algorithm/software, apparatus/system, process/material, or mixed.
16
17	State the detected values in one short line. Load only the matching fragments
18	declared in the manifest. Load detailed references only when their condition
19	applies.
20
21	## 2. Preserve source grounding
22
23	Create stable source IDs before drafting:
24
25	- `P001...` for paper text blocks;
26	- `E001...` for equations;
27	- `F001...` for source figures;
28	- `C001...` for source-code or supplementary evidence.
29
30	Every material feature in a formal claim must map to one or more source IDs.
31	Use only `explicit`, `inherent`, `needs-confirmation`, or `unsupported` as
32	support states. Exclude `unsupported` features from formal claims.
33
34	Never infer inventorship, ownership, unpublished implementation details,
35	publication dates, prior-art conclusions, or legal sufficiency. Use
36	`[TO CONFIRM: specific question]` outside formal claims when facts are missing.
37
38	## 3. Draft through stage gates
39
40	For `full-draft`, `claim-set`, `disclosure-analysis`, and `paper-patent-audit`,
41	complete the stages in `static/core/workflow.md` in order. Persist the
42	intermediate artifacts specified there. Do not move to formal claims until the
43	source map, terminology ledger, inventories, evidence ledger, and invention
44	concept pass their gates.
45
46	For `technical-disclosure`, follow the ordered prompt references in
47	`static/fragments/task/technical-disclosure.md`. For `disclosure-iteration`,
48	follow `static/fragments/task/disclosure-iteration.md` and preserve the prior
49	draft instead of restarting the formal application workflow.
50
51	For a full application, draft claims first, then align the specification,
52	figures, embodiments, and abstract to the claim terminology and step order.
53
54	## 4. Produce Chinese formal documents
55
56	Agent-facing analysis may use the user's preferred language. Produce formal
57	Chinese patent deliverables in Chinese when the task is a formal application
58	package:
59
60	- 权利要求书;
61	- 说明书;
62	- 说明书摘要;
63	- 摘要附图;
64	- figure labels and descriptions.
65
66	For `technical-disclosure` and `disclosure-iteration`, produce the Chinese
67	technical disclosure (`技术交底书`) as timestamped Markdown plus matching DOCX,
68	with Mermaid system/process diagrams rendered through `scripts/disclosure/`.
69
70	For algorithmic inventions, retain source-supported core formulas, define every
71	symbol, explain each formula's technical operation, and render formulas as
72	native editable Office Math in DOCX. Do not use plain LaTeX strings as the
73	visible formula.
74
75	Generate the main flowchart from the ordered steps of the principal method
76	claim. Its final node must name the concrete domain output, such as a defect
77	detection result, target pose, state estimate, or control instruction. Reuse
78	the same main figure as the abstract figure and a specification figure.
79
80	## 5. Validate before delivery
81
82	For formal application packages, populate the structured draft described in
83	`references/draft-schema.md`, then run:
84
85	```bash
86	python scripts/validate_patent_draft.py draft.json
87	python scripts/build_patent_package.py draft.json --output-dir outputs --prefix patent
88	```
89
90	Resolve all validation `ERROR` findings. Review every `WARNING` against the
91	source. Label the result `incomplete draft` when a required quality threshold
92	in `static/core/output-contract.md` is not met.
93
94	For technical disclosures, run the internal checks in
95	`references/disclosure/disclosure_self_check.md`, render Mermaid/Word outputs
96	with `scripts/disclosure/mermaid_render.py`, and resolve formula, parameter,
97	prior-art URL, and chapter-consistency issues before delivery.
98
99	The generated package is a drafting aid for inventor and patent-professional
100	review, not a patentability opinion, infringement opinion, or filing guarantee.

People who liked this also viewed

6 picks

Type

nature-paper-to-patent

1.9kinstalls1.8kforks

View on GitHub

How to install nature-paper-to-patent?

yuan1z0825/nature-skills/nature-paper-to-patent

$npx -y skills add Yuan1z0825/nature-skills --skill nature-paper-to-patent

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Paper to Chinese Patent
2
3	Use this file as the router for the patent-drafting workflow. Do not draft the
4	application directly from the paper abstract or contribution list.
5
6	## 1. Load the workflow
7
8	Read `manifest.yaml`, then read every file under `always_load`.
9
10	Detect these axes from the user's files and request:
11
12	- `source_format`: selectable PDF, scanned PDF, pasted text, or mixed project;
13	- `task_mode`: full draft, claim set, disclosure analysis, technical
14	disclosure, disclosure iteration, or paper-patent audit;
15	- `invention_type`: algorithm/software, apparatus/system, process/material, or mixed.
16
17	State the detected values in one short line. Load only the matching fragments
18	declared in the manifest. Load detailed references only when their condition
19	applies.
20
21	## 2. Preserve source grounding
22
23	Create stable source IDs before drafting:
24
25	- `P001...` for paper text blocks;
26	- `E001...` for equations;
27	- `F001...` for source figures;
28	- `C001...` for source-code or supplementary evidence.
29
30	Every material feature in a formal claim must map to one or more source IDs.
31	Use only `explicit`, `inherent`, `needs-confirmation`, or `unsupported` as
32	support states. Exclude `unsupported` features from formal claims.
33
34	Never infer inventorship, ownership, unpublished implementation details,
35	publication dates, prior-art conclusions, or legal sufficiency. Use
36	`[TO CONFIRM: specific question]` outside formal claims when facts are missing.
37
38	## 3. Draft through stage gates
39
40	For `full-draft`, `claim-set`, `disclosure-analysis`, and `paper-patent-audit`,
41	complete the stages in `static/core/workflow.md` in order. Persist the
42	intermediate artifacts specified there. Do not move to formal claims until the
43	source map, terminology ledger, inventories, evidence ledger, and invention
44	concept pass their gates.
45
46	For `technical-disclosure`, follow the ordered prompt references in
47	`static/fragments/task/technical-disclosure.md`. For `disclosure-iteration`,
48	follow `static/fragments/task/disclosure-iteration.md` and preserve the prior
49	draft instead of restarting the formal application workflow.
50
51	For a full application, draft claims first, then align the specification,
52	figures, embodiments, and abstract to the claim terminology and step order.
53
54	## 4. Produce Chinese formal documents
55
56	Agent-facing analysis may use the user's preferred language. Produce formal
57	Chinese patent deliverables in Chinese when the task is a formal application
58	package:
59
60	- 权利要求书;
61	- 说明书;
62	- 说明书摘要;
63	- 摘要附图;
64	- figure labels and descriptions.
65
66	For `technical-disclosure` and `disclosure-iteration`, produce the Chinese
67	technical disclosure (`技术交底书`) as timestamped Markdown plus matching DOCX,
68	with Mermaid system/process diagrams rendered through `scripts/disclosure/`.
69
70	For algorithmic inventions, retain source-supported core formulas, define every
71	symbol, explain each formula's technical operation, and render formulas as
72	native editable Office Math in DOCX. Do not use plain LaTeX strings as the
73	visible formula.
74
75	Generate the main flowchart from the ordered steps of the principal method
76	claim. Its final node must name the concrete domain output, such as a defect
77	detection result, target pose, state estimate, or control instruction. Reuse
78	the same main figure as the abstract figure and a specification figure.
79
80	## 5. Validate before delivery
81
82	For formal application packages, populate the structured draft described in
83	`references/draft-schema.md`, then run:
84
85	```bash
86	python scripts/validate_patent_draft.py draft.json
87	python scripts/build_patent_package.py draft.json --output-dir outputs --prefix patent
88	```
89
90	Resolve all validation `ERROR` findings. Review every `WARNING` against the
91	source. Label the result `incomplete draft` when a required quality threshold
92	in `static/core/output-contract.md` is not met.
93
94	For technical disclosures, run the internal checks in
95	`references/disclosure/disclosure_self_check.md`, render Mermaid/Word outputs
96	with `scripts/disclosure/mermaid_render.py`, and resolve formula, parameter,
97	prior-art URL, and chapter-consistency issues before delivery.
98
99	The generated package is a drafting aid for inventor and patent-professional
100	review, not a patentability opinion, infringement opinion, or filing guarantee.

People who liked this also viewed

6 picks

Type