nature-paper-to-patent
Skill0 starsChanged 2 months agoMITView on GitHub
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 revise a Chinese technical disclosure (技术交底书), run prior-art comparison, convert Office project materials, map every claimed feature to source evidence, preserve core formulas as editable Office Math, generate claim-aligned flowcharts and methodology figures, compare a paper with an existing patent, audit support and consistency, or deliver Chinese DOCX patent/disclosure files.
7 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- denghuipan/nature-portfolio-skillsedited, first seen Nov 15, 2026
- Luooops/skillsedited, first seen Oct 13, 2026
- yanjumlinnb-boop/nature-skillsedited, first seen Oct 8, 2026
- Yuan1z0825/nature-skillsedited, first seen Aug 31, 2026
- zh123012/claude-skillsedited, first seen Jul 29, 2026
- Delagong950/nature-skillstheir own version, first seen Jul 6, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- Yuan1z0825/nature-skills★ 54k95% same
- yanjumlinnb-boop/nature-skills★ 1489% same
- denghuipan/nature-portfolio-skills★ 289% same
- Luooops/skills★ 195% same
- zh123012/claude-skills★ 199% same
Wrote their own version · 2
- Delagong950/nature-skills★ 4same name
- vcis-wangchenxu/agent_nature-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- journal-style-learnSkill
- nature-academic-searchSkill
- nature-citationSkill
- nature-dataSkill
- nature-downloaderSkill
- nature-experiment-logSkill
- nature-figure-prompt-onlySkill
- nature-figureSkill
- nature-image2pptSkill
- nature-literature-pipelineSkill
- nature-paper2pptSkill
- nature-paper-cardSkill
- nature-polishingSkill
- researchwriteSkill
- nature-readerSkill
- nature-ref-verifierSkill
- nature-responseSkill
- nature-reviewerSkill
- nature-sharedSkill
- nature-statisticsSkill
- nature-writingSkill
The file
We split this skill into the rules it gives an agent
9 rules. 2 are common, 2 are distinctive, and 5 are very specific to this project.
2
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Treat a source journal as metadata: preserve the source’s facts and structure.
- Distinctive: line 16
Keep this skill’s original source-processing workflow.
- Very specific: line 24
Only if journal fit or submission requirements are requested, read ../nature-shared/journal-formats/eswa.md.
- Common: line 29
Use this file as the router for the patent-drafting workflow.
- Very specific: line 34
Read manifest.yaml, then read every file under always_load.
- Common: line 49
Create stable source IDs before drafting:
- Very specific: line 56
Every material feature in a formal claim must map to one or more source IDs.
- Very specific: line 57
Use only explicit, inherent, needs-confirmation, or unsupported as support states.
- Very specific: line 60
Never infer inventorship, ownership, unpublished implementation details, publication dates, prior-art conclusions, or legal sufficiency.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Paper to Chinese Patent
Additional configured journals
For Applied Soft Computing (ASC), Engineering Applications of Artificial
Intelligence (EAAI), ISA Transactions, Knowledge-Based Systems (KBS),
Measurement, Neurocomputing, or IEEE Transactions on Reliability, use
../nature-shared/journal-formats/index.md to resolve the exact journal.
Treat a source journal as metadata: preserve the source’s facts and structure.
Load submission constraints only when target formatting or fit is requested.
Keep this skill’s original source-processing workflow.
ESWA journal context
Recognize Expert Systems with Applications (ESWA, Expert Syst. Appl.)
as the same journal, case-insensitively; distinguish similarly named titles.
Preserve patent conversion, evidence and jurisdiction requirements.
An ESWA source paper supplies technical material, not a patent-format contract.
Only if journal fit or submission requirements are requested, read
../nature-shared/journal-formats/eswa.md; otherwise keep this workflow
source-oriented without loading submission rules.
Use this file as the router for the patent-drafting workflow. Do not draft the application directly from the paper abstract or contribution list.
1. Load the workflow
Read manifest.yaml, then read every file under always_load.
Detect these axes from the user's files and request:
source_format: selectable PDF, scanned PDF, pasted text, or mixed project;task_mode: full draft, claim set, disclosure analysis, technical disclosure, disclosure iteration, or paper-patent audit;invention_type: algorithm/software, apparatus/system, process/material, or mixed.
State the detected values in one short line. Load only the matching fragments declared in the manifest. Load detailed references only when their condition applies.
2. Preserve source grounding
Create stable source IDs before drafting:
P001...for paper text blocks;E001...for equations;F001...for source figures;C001...for source-code or supplementary evidence.
Every material feature in a formal claim must map to one or more source IDs.
Use only explicit, inherent, needs-confirmation, or unsupported as
support states. Exclude unsupported features from formal claims.
Never infer inventorship, ownership, unpublished implementation details,
publication dates, prior-art conclusions, or legal sufficiency. Use
[TO CONFIRM: specific question] outside formal claims when facts are missing.
3. Draft through stage gates
For full-draft, claim-set, disclosure-analysis, and paper-patent-audit,
complete the stages in static/core/workflow.md in order. Persist the
intermediate artifacts specified there. Do not move to formal claims until the
source map, terminology ledger, inventories, evidence ledger, and invention
concept pass their gates.
For technical-disclosure, follow the ordered prompt references in
static/fragments/task/technical-disclosure.md. For disclosure-iteration,
follow static/fragments/task/disclosure-iteration.md and preserve the prior
draft instead of restarting the formal application workflow.
For a full application, draft claims first, then align the specification, figures, embodiments, and abstract to the claim terminology and step order.
4. Produce Chinese formal documents
Agent-facing analysis may use the user's preferred language. Produce formal Chinese patent deliverables in Chinese when the task is a formal application package:
- 权利要求书;
- 说明书;
- 说明书摘要;
- 摘要附图;
- figure labels and descriptions.
For technical-disclosure and disclosure-iteration, produce the Chinese
technical disclosure (技术交底书) as timestamped Markdown plus matching DOCX,
with Mermaid system/process diagrams rendered through scripts/disclosure/.
For algorithmic inventions, retain source-supported core formulas, define every symbol, explain each formula's technical operation, and render formulas as native editable Office Math in DOCX. Do not use plain LaTeX strings as the visible formula.
Generate the main flowchart from the ordered steps of the principal method claim. Its final node must name the concrete domain output, such as a defect detection result, target pose, state estimate, or control instruction. Reuse the same main figure as the abstract figure and a specification figure.
5. Validate before delivery
For formal application packages, populate the structured draft described in
references/draft-schema.md, then run:
python scripts/validate_patent_draft.py draft.json
python scripts/build_patent_package.py draft.json --output-dir outputs --prefix patentResolve all validation ERROR findings. Review every WARNING against the
source. Label the result incomplete draft when a required quality threshold
in static/core/output-contract.md is not met.
For technical disclosures, run the internal checks in
references/disclosure/disclosure_self_check.md, render Mermaid/Word outputs
with scripts/disclosure/mermaid_render.py, and resolve formula, parameter,
prior-art URL, and chapter-consistency issues before delivery.
The generated package is a drafting aid for inventor and patent-professional review, not a patentability opinion, infringement opinion, or filing guarantee.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

