[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FD68M1ECZXJWSWCC7R924A":3,"skill-same:01M7FD68M1ECZXJWSWCC7R924A":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7FD68M1ECZXJWSWCC7R924A","patent-novelty-check",null,"Assess patent novelty and non-obviousness against prior art. Use when user says \"专利查新\", \"patent novelty\", \"可专利性评估\", \"patentability check\", or wants to evaluate if an invention is patentable.","CZX-LBJ\u002Fdeepseek-science","CZX-LBJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F204594689?v=4","01M7FC59WQ9PFXT04MKGJDCFFT","czx","01M7FC59XB2GW0BKWN9JTDBQS7",1,"MIT","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fpatent-novelty-check\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: patent-novelty-check\ndescription: \"Assess patent novelty and non-obviousness against prior art. Use when user says \\\"专利查新\\\", \\\"patent novelty\\\", \\\"可专利性评估\\\", \\\"patentability check\\\", or wants to evaluate if an invention is patentable.\"\nargument-hint: \"[invention-description-or-brief-path]\"\nallowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, mcp__codex__codex\n---\n\n# Patent Novelty and Non-Obviousness Check\n\nAssess patentability of: **$ARGUMENTS**\n\nAdapted from `\u002Fnovelty-check` for patent legal standards. Research novelty is NOT the same as patent novelty.\n\n## Constants\n\n- `REVIEWER_MODEL = gpt-6-astra` — Model used via Codex MCP for cross-model examiner verification\n- `NOVELTY_STANDARD = patent` — Always use legal patentability standard, not research contribution standard\n\n## Inputs\n\n1. Invention description from `$ARGUMENTS`\n2. `patent\u002FPRIOR_ART_REPORT.md` (output of `\u002Fprior-art-search`)\n3. `patent\u002FINVENTION_BRIEF.md` if exists\n\n## Shared References\n\nLoad `..\u002Fshared-references\u002Fpatent-writing-principles.md` for novelty\u002Fnon-obviousness standards.\nLoad `..\u002Fshared-references\u002Fpatent-format-us.md` for 102\u002F103 analysis framework.\n\n## Workflow\n\n### Step 1: Define Claim Elements\n\nFrom the invention description, extract the key claim elements that would define the invention's scope:\n1. List the technical features that make the invention novel\n2. Identify which features are known from prior art vs. inventive\n3. Draft preliminary claim language for 2-3 independent claims (method + system)\n\n### Step 2: Anticipation Analysis (Novelty)\n\nFor each preliminary claim, test against EACH prior art reference in `PRIOR_ART_REPORT.md`:\n\n**Single-reference test**: Does any single reference disclose ALL claim elements?\n\n| Claim Element | Ref 1 | Ref 2 | Ref 3 | ... |\n|--------------|-------|-------|-------|-----|\n| Feature A | Yes\u002FNo + evidence | | | |\n| Feature B | Yes\u002FNo + evidence | | | |\n| Feature C | Yes\u002FNo + evidence | | | |\n| Feature D | Yes\u002FNo + evidence | | | |\n\n**Verdict per reference**:\n- ANTICIPATED: One reference discloses every element → claim is not novel\n- NOT ANTICIPATED: At least one element missing from every single reference → claim is novel\n\n### Step 3: Obviousness Analysis (Inventive Step)\n\nIf the invention is novel (passes Step 2), test for obviousness:\n\n**Two\u002Fthree-reference combination test**: Can 2-3 references be combined to render the claim obvious?\n\nFor each combination of the top references:\n1. **Primary reference**: Which reference is closest to the claimed invention?\n2. **Secondary reference(s)**: Which reference(s) teach the missing element(s)?\n3. **Motivation to combine**: Would a POSITA have reason to combine these references?\n   - Explicit suggestion in the references themselves?\n   - Same field, same problem?\n   - Common design incentive?\n   - Known technique for improving similar devices?\n\nFormat as a matrix:\n\n| Combination | Primary | Secondary | Missing Elements | Motivation to Combine | Obvious? |\n|-------------|---------|-----------|-----------------|----------------------|----------|\n| Ref1 + Ref2 | Ref1 | Ref2 | Feature D | Same field, similar problem | Yes\u002FNo |\n\n### Step 4: Cross-Model Examiner Verification\n\nCall `REVIEWER_MODEL` via `mcp__codex__codex` with xhigh reasoning:\n\n```\nmcp__codex__codex:\n  model: gpt-6-astra\n  config: {\"model_reasoning_effort\": \"xhigh\"}\n  prompt: |\n    You are a senior patent examiner at the [USPTO\u002FCNIPA\u002FEPO].\n    Examine the following invention for patentability.\n\n    INVENTION: [invention description + preliminary claims]\n\n    PRIOR ART: [prior art references with key teachings]\n\n    Please analyze:\n    1. Anticipation (novelty): Does any single reference anticipate any claim?\n    2. Obviousness: Can any combination of references render claims obvious?\n    3. Claim scope: Are the claims broad enough to be valuable?\n    4. Recommended amendments if any claim is rejected.\n    Be rigorous and cite specific references.\n```\n\n### Step 5: Jurisdiction-Specific Assessment\n\nFor each target jurisdiction, provide a patentability assessment:\n\n**Under 35 USC 102\u002F103 (US)**:\n- Novelty: PASS \u002F FAIL (cite specific reference if fail)\n- Non-obviousness: PASS \u002F FAIL (cite combination if fail)\n\n**Under Article 22 CN Patent Law (CN)**:\n- 新颖性 (Novelty): 通过 \u002F 未通过\n- 创造性 (Inventive Step): 通过 \u002F 未通过\n\n**Under Article 54\u002F56 EPC (EP)**:\n- Novelty: PASS \u002F FAIL\n- Inventive step: PASS \u002F FAIL (problem-solution approach)\n\n### Step 6: Output\n\nWrite `patent\u002FNOVELTY_ASSESSMENT.md`:\n\n```markdown\n## Patentability Assessment\n\n### Invention Summary\n[description]\n\n### Overall Assessment\n[PATENTABLE \u002F PATENTABLE WITH AMENDMENTS \u002F NOT PATENTABLE]\n\n### Anticipation Analysis\n[claim-by-claim matrix against each reference]\n\n### Obviousness Analysis\n[combination analysis with motivation to combine]\n\n### Cross-Model Examiner Review\n[summary of GPT-6-Astra examiner feedback]\n\n### Recommended Claim Amendments\n[If claims need modification to overcome prior art, suggest specific amendments]\n\n### Risk Factors\n[What could cause rejection during actual prosecution?]\n```\n\n## Key Rules\n\n- Patent novelty is absolute: any public disclosure before the priority date counts as prior art, worldwide.\n- Research novelty (\"has anyone published this?\") is NOT the same as patent novelty (\"does any single reference teach every claim element?\").\n- Obviousness requires BOTH: (1) a combination of references AND (2) a motivation to combine them.\n- Never assume the invention is patentable just because no identical patent exists.\n- The assessment is advisory only -- actual prosecution may reveal different prior art.\n- If `mcp__codex__codex` is not available, skip cross-model examiner review and note it in the output.\n","# Patent Novelty and Non-Obviousness Check\n\nAssess patentability of: **$ARGUMENTS**\n\nAdapted from `\u002Fnovelty-check` for patent legal standards. Research novelty is NOT the same as patent novelty.\n\n## Constants\n\n- `REVIEWER_MODEL = gpt-6-astra` — Model used via Codex MCP for cross-model examiner verification\n- `NOVELTY_STANDARD = patent` — Always use legal patentability standard, not research contribution standard\n\n## Inputs\n\n1. Invention description from `$ARGUMENTS`\n2. `patent\u002FPRIOR_ART_REPORT.md` (output of `\u002Fprior-art-search`)\n3. `patent\u002FINVENTION_BRIEF.md` if exists\n\n## Shared References\n\nLoad `..\u002Fshared-references\u002Fpatent-writing-principles.md` for novelty\u002Fnon-obviousness standards.\nLoad `..\u002Fshared-references\u002Fpatent-format-us.md` for 102\u002F103 analysis framework.\n\n## Workflow\n\n### Step 1: Define Claim Elements\n\nFrom the invention description, extract the key claim elements that would define the invention's scope:\n1. List the technical features that make the invention novel\n2. Identify which features are known from prior art vs. inventive\n3. Draft preliminary claim language for 2-3 independent claims (method + system)\n\n### Step 2: Anticipation Analysis (Novelty)\n\nFor each preliminary claim, test against EACH prior art reference in `PRIOR_ART_REPORT.md`:\n\n**Single-reference test**: Does any single reference disclose ALL claim elements?\n\n| Claim Element | Ref 1 | Ref 2 | Ref 3 | ... |\n|--------------|-------|-------|-------|-----|\n| Feature A | Yes\u002FNo + evidence | | | |\n| Feature B | Yes\u002FNo + evidence | | | |\n| Feature C | Yes\u002FNo + evidence | | | |\n| Feature D | Yes\u002FNo + evidence | | | |\n\n**Verdict per reference**:\n- ANTICIPATED: One reference discloses every element → claim is not novel\n- NOT ANTICIPATED: At least one element missing from every single reference → claim is novel\n\n### Step 3: Obviousness Analysis (Inventive Step)\n\nIf the invention is novel (passes Step 2), test for obviousness:\n\n**Two\u002Fthree-reference combination test**: Can 2-3 references be combined to render the claim obvious?\n\nFor each combination of the top references:\n1. **Primary reference**: Which reference is closest to the claimed invention?\n2. **Secondary reference(s)**: Which reference(s) teach the missing element(s)?\n3. **Motivation to combine**: Would a POSITA have reason to combine these references?\n   - Explicit suggestion in the references themselves?\n   - Same field, same problem?\n   - Common design incentive?\n   - Known technique for improving similar devices?\n\nFormat as a matrix:\n\n| Combination | Primary | Secondary | Missing Elements | Motivation to Combine | Obvious? |\n|-------------|---------|-----------|-----------------|----------------------|----------|\n| Ref1 + Ref2 | Ref1 | Ref2 | Feature D | Same field, similar problem | Yes\u002FNo |\n\n### Step 4: Cross-Model Examiner Verification\n\nCall `REVIEWER_MODEL` via `mcp__codex__codex` with xhigh reasoning:\n\n```\nmcp__codex__codex:\n  model: gpt-6-astra\n  config: {\"model_reasoning_effort\": \"xhigh\"}\n  prompt: |\n    You are a senior patent examiner at the [USPTO\u002FCNIPA\u002FEPO].\n    Examine the following invention for patentability.\n\n    INVENTION: [invention description + preliminary claims]\n\n    PRIOR ART: [prior art references with key teachings]\n\n    Please analyze:\n    1. Anticipation (novelty): Does any single reference anticipate any claim?\n    2. Obviousness: Can any combination of references render claims obvious?\n    3. Claim scope: Are the claims broad enough to be valuable?\n    4. Recommended amendments if any claim is rejected.\n    Be rigorous and cite specific references.\n```\n\n### Step 5: Jurisdiction-Specific Assessment\n\nFor each target jurisdiction, provide a patentability assessment:\n\n**Under 35 USC 102\u002F103 (US)**:\n- Novelty: PASS \u002F FAIL (cite specific reference if fail)\n- Non-obviousness: PASS \u002F FAIL (cite combination if fail)\n\n**Under Article 22 CN Patent Law (CN)**:\n- 新颖性 (Novelty): 通过 \u002F 未通过\n- 创造性 (Inventive Step): 通过 \u002F 未通过\n\n**Under Article 54\u002F56 EPC (EP)**:\n- Novelty: PASS \u002F FAIL\n- Inventive step: PASS \u002F FAIL (problem-solution approach)\n\n### Step 6: Output\n\nWrite `patent\u002FNOVELTY_ASSESSMENT.md`:\n\n```markdown\n## Patentability Assessment\n\n### Invention Summary\n[description]\n\n### Overall Assessment\n[PATENTABLE \u002F PATENTABLE WITH AMENDMENTS \u002F NOT PATENTABLE]\n\n### Anticipation Analysis\n[claim-by-claim matrix against each reference]\n\n### Obviousness Analysis\n[combination analysis with motivation to combine]\n\n### Cross-Model Examiner Review\n[summary of GPT-6-Astra examiner feedback]\n\n### Recommended Claim Amendments\n[If claims need modification to overcome prior art, suggest specific amendments]\n\n### Risk Factors\n[What could cause rejection during actual prosecution?]\n```\n\n## Key Rules\n\n- Patent novelty is absolute: any public disclosure before the priority date counts as prior art, worldwide.\n- Research novelty (\"has anyone published this?\") is NOT the same as patent novelty (\"does any single reference teach every claim element?\").\n- Obviousness requires BOTH: (1) a combination of references AND (2) a motivation to combine them.\n- Never assume the invention is patentable just because no identical patent exists.\n- The assessment is advisory only -- actual prosecution may reveal different prior art.\n- If `mcp__codex__codex` is not available, skip cross-model examiner review and note it in the output.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, mcp__codex__codex","[invention-description-or-brief-path]","main","18193d71ea3441d7c033dbf195b8a7c75ac96f75","packages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fpatent-novelty-check",0,"https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science","https:\u002F\u002Fgithub.com\u002FCZX-LBJ","一个没事喜欢随便写点代码的小菜鸡\r\n","2026-10-22 09:48:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add CZX-LBJ\u002Fdeepseek-science --skill patent-novelty-check",{"tool":40,"command":41},"bunx","bunx skills add CZX-LBJ\u002Fdeepseek-science --skill patent-novelty-check",{"tool":43,"command":44},"pnpm","pnpm dlx skills add CZX-LBJ\u002Fdeepseek-science --skill patent-novelty-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fpatent-novelty-check\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7FEEKSNMRMKW6JEK93PFDFY","bio-free-energy-calculations","Performs alchemical free-energy calculations including relative binding free energy (RBFE \u002F FEP+) and absolute binding free energy (ABFE) via OpenFE, FEP+, GROMACS, AMBER pmemd, and OpenMM with explicit lambda scheduling, soft-core potentials, MBAR\u002FBAR analysis, cycle-closure validation, and protocol-appropriate enhanced sampling. Compares ML alternatives (Boltz-2 affinity, DeepDock). Use when ranking analogs by binding affinity beyond docking accuracy, performing prospective lead optimization, or validating SAR predictions.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Fbioskills\u002Fchemoinformatics\u002Ffree-energy-calculations\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7FEE5CTE5QK55CEMXNNVWY9","bio-conformer-generation","Generates 3D conformer ensembles using RDKit ETKDGv3 with knowledge-enhanced distance geometry, MMFF94\u002FUFF force-field optimization, CREST + GFN2-xTB semi-empirical refinement, and macrocycle-aware torsion preferences. Provides explicit decision rules for single vs ensemble conformer use, RMSD pruning, energy windows, conformer count, and force-field choice. Use when preparing 3D ligands for docking, generating descriptor input for 3D QSAR, or sampling macrocycle\u002Fpeptide conformational ensembles.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Fbioskills\u002Fchemoinformatics\u002Fconformer-generation\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7FEDNGFEMFWD1MSEDR5H7CY","bio-admet-prediction","Predicts ADMET properties using ADMETlab 3.0 (119 platform features, including 77 prediction models with modeled-endpoint uncertainty), ADMET-AI, DeepChem MolNet, and chemprop D-MPNN with explicit handling of OECD QSAR principles, applicability domain assessment, calibration, hERG\u002FCYP\u002FAMES endpoints, and PAINS \u002F Lipinski \u002F Ro5 \u002F Veber \u002F BBB druglikeness filters. Use when filtering compounds for drug-likeness, prioritizing leads by predicted safety, or building an in-house ADMET QSAR model.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Fbioskills\u002Fchemoinformatics\u002Fadmet-prediction\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7FED69GFB54FRF7AV5066DN","writing-systems-papers","Paragraph-level structural blueprint for 10-12 page systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides page allocation, paragraph templates, and writing patterns. Use when user says \"写系统论文\", \"systems paper structure\", \"OSDI paper\", \"SOSP paper\", or wants fine-grained structural guidance for a systems conference submission.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fwriting-systems-papers\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7FECVVDWZ0X0VEDTCE4B4DZ","wiki-enrich","Fill in the per-paper TODO sections of research-wiki\u002Fpapers\u002F\u003Cslug>.md pages that literature-ingest skills leave as bare scaffolds. Use when user says 'enrich wiki', 'fill paper TODOs', 'wiki body 補完', '把 paper 摘要寫進 wiki', 'research-wiki 自動填', or after a batch ingest that left papers\u002F as TODO scaffolds.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fwiki-enrich\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7FECD4BCJ2MTSBDDSE3ZAJ5","web-debug-search","Search GitHub, Stack Exchange, Chinese technical communities, official documentation, and general developer web sources for software errors, compatibility problems, API usage questions, and real-world workarounds. Use for debugging and discovery only; results are not paper-citation evidence.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fweb-debug-search\u002FSKILL.md",[],[]]