[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FDMERKAR8RD26ZR17PRC70":3,"skill-same:01M7FDMERKAR8RD26ZR17PRC70":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},"01M7FDMERKAR8RD26ZR17PRC70","embodiment-description",null,"Write detailed embodiment descriptions for patent specifications. Use when user says \"撰写实施例\", \"write embodiment\", \"实施例描述\", \"detailed description\", or wants to describe how to practice an invention.","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\u002Fskills-codex\u002Fembodiment-description\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: embodiment-description\ndescription: \"Write detailed embodiment descriptions for patent specifications. Use when user says \\\"撰写实施例\\\", \\\"write embodiment\\\", \\\"实施例描述\\\", \\\"detailed description\\\", or wants to describe how to practice an invention.\"\nargument-hint: \"[claims-path-or-embodiment-details]\"\nallowed-tools: Bash(*), Read, Write, Edit, Grep, Glob\n---\n\n# Embodiment Description\n\nWrite detailed embodiments for: **$ARGUMENTS**\n\nEmbodiments describe HOW to make and use the invention -- they are the patent equivalent of experiment sections, but describe the invention rather than evaluating it empirically.\n\n## Constants\n\n- `MIN_EMBODIMENTS = 1` — At least one complete embodiment required\n- `MAX_EMBODIMENTS = 3` — Practical limit; more embodiments strengthen enablement\n- `EMBODIMENT_STYLE = detailed` — `detailed` (full working example) or `outline` (sketch)\n- `REFERENCE_NUMERAL_PREFIX = 100` — Starting reference numeral for first figure's components\n\n## Inputs\n\n1. `patent\u002FINVENTION_DISCLOSURE.md` — invention decomposition (core\u002Fsupporting\u002Foptional features)\n2. `patent\u002FCLAIMS.md` — drafted claims that the embodiments must support\n3. User-provided figures (if any) in any directory\n4. `patent\u002Ffigures\u002Fnumeral_index.md` if it exists (from `\u002Ffigure-description`)\n\n## Workflow\n\n### Step 1: Plan Embodiments\n\nFor each claim category (method, system, etc.), plan at least one embodiment:\n\n| Embodiment | Covers Claims | Type | Key Variations |\n|-----------|--------------|------|----------------|\n| 1 | Claims 1, X | Best mode \u002F preferred | [primary implementation] |\n| 2 | Claims 2, 3 | Alternative | [different parameters\u002Fmaterials] |\n| 3 | Claims 4, 5 | Additional alternative | [different configuration] |\n\n### Step 2: Write Each Embodiment\n\nFor each embodiment, write a detailed description following this structure:\n\n**Opening paragraph**:\n\"In one embodiment, [invention summary with reference to what is being described].\"\n\n**Component\u002Fstep-by-step description**:\n\nFor method embodiments:\n- Describe each step in order\n- Reference figure numerals: \"As shown in FIG. 1, at step 202, the processor 102 receives the input data 104...\"\n- Include specific parameters, ranges, and conditions\n- Describe what happens at each decision point\n\nFor system\u002Fapparatus embodiments:\n- Describe each component\n- Reference figure numerals: \"Referring to FIG. 1, the system 100 comprises a processor 102, a memory 104, and a communication interface 106...\"\n- Describe interconnections between components\n- Describe operation of the system step-by-step\n\n**Variations and alternatives**:\n- \"In some embodiments, the processor 102 may be a GPU, an FPGA, or an ASIC.\"\n- \"In another embodiment, the memory 104 may be replaced with a distributed storage system.\"\n- \"The parameters described above are exemplary; other values within the range [X, Y] are also contemplated.\"\n\nThese variations are critical -- they support broader claim interpretation.\n\n### Step 3: Reference Numeral Integration\n\nEnsure consistent reference numeral usage:\n\n1. Every component mentioned must have a numeral\n2. Numeral must appear first in parentheses after the component name: \"the processor (102)\"\n3. Subsequent references: \"the processor 102\" (no parentheses)\n4. Numbering follows figure series: 100-series for FIG. 1, 200-series for FIG. 2\n\n**Format**:\n- First mention: \"the processor (102)\"\n- Later in same embodiment: \"the processor 102\"\n- Cross-figure: \"the processor 102 (shown in both FIG. 1 and FIG. 2)\"\n\n### Step 4: Claim Support Verification\n\nFor each claim element, verify it appears in at least one embodiment:\n\n| Claim Element | Embodiment | Reference Numeral | Description Paragraph |\n|---------------|-----------|-------------------|----------------------|\n| [element] | [which] | [numeral] | [paragraph reference] |\n\nIf any claim element lacks embodiment support, add the necessary description.\n\n### Step 5: Software\u002FAlgorithm Embodiments (if applicable)\n\nFor method\u002Fsoftware inventions, include:\n- Pseudocode or algorithmic description (NOT actual code)\n- Flowchart description tied to figures\n- Data structure descriptions\n- Interface specifications\n\nExample:\n```\nIn one embodiment, the method comprises the following steps:\nAt step 202, the processor 102 receives input data from the input device 108.\nAt step 204, the processor 102 extracts feature vectors from the input data using a convolutional neural network.\nAt step 206, the processor 102 applies the attention mechanism 110 to the feature vectors...\n```\n\n### Step 6: Output\n\nEmbodiment sections are written to `patent\u002Fspecification\u002Fdetailed_description.md` (or appended to the specification structure).\n\nEach embodiment section should be self-contained but cross-reference other embodiments when describing alternatives.\n\n## Key Rules\n\n- Embodiments must teach a POSITA to make and use the invention without undue experimentation.\n- Include at least one \"best mode\" embodiment (US requirement).\n- Multiple embodiments strengthen the specification against enablement challenges.\n- Describe the invention, do NOT evaluate it empirically (\"The embodiment achieves 95% accuracy\" is wrong; \"The processor classifies the input data\" is correct).\n- **CRITICAL — NO experimental data, test results, accuracy percentages, detection rates, precision values, or comparative performance data.** These belong in papers, not patents. The embodiment teaches HOW to make and use, not HOW WELL it performs.\n- WRONG: \"传感器对直径超过150μm的金属颗粒实现了100%的检测精度，即使在检测限处仍保持94%的高精度。\"\n- RIGHT: \"当不锈钢颗粒通过间隙传感区域时，谐振频率下降。颗粒直径越大，频率偏移幅度越大。\"\n- Do NOT include tables of experimental results, graphs of measurement data, or comparisons with prior art performance.\n- **CRITICAL — An embodiment is NOT an experiment.** Do NOT describe \"repeated experiments\", \"accuracy evaluation\", \"precision testing\", \"calibration experiments\", or \"comparison with reference methods\". An embodiment describes ONE way to make and use the invention — it is a recipe, not a test report.\n- Do NOT copy experimental sections from source papers verbatim. Transform the experimental setup into a manufacturing\u002Foperation description.\n- If the source material is a paper, extract ONLY: (1) what was built, (2) what materials\u002Fparameters were used, (3) how it operates. Ignore all test methodology, results, and performance metrics.\n- Include specific parameters where possible, but frame them as exemplary, not limiting.\n- Reference numerals must be consistent with the figures.\n- Do NOT use subjective language (\"excellent\", \"surprising\", \"superior\").\n","# Embodiment Description\n\nWrite detailed embodiments for: **$ARGUMENTS**\n\nEmbodiments describe HOW to make and use the invention -- they are the patent equivalent of experiment sections, but describe the invention rather than evaluating it empirically.\n\n## Constants\n\n- `MIN_EMBODIMENTS = 1` — At least one complete embodiment required\n- `MAX_EMBODIMENTS = 3` — Practical limit; more embodiments strengthen enablement\n- `EMBODIMENT_STYLE = detailed` — `detailed` (full working example) or `outline` (sketch)\n- `REFERENCE_NUMERAL_PREFIX = 100` — Starting reference numeral for first figure's components\n\n## Inputs\n\n1. `patent\u002FINVENTION_DISCLOSURE.md` — invention decomposition (core\u002Fsupporting\u002Foptional features)\n2. `patent\u002FCLAIMS.md` — drafted claims that the embodiments must support\n3. User-provided figures (if any) in any directory\n4. `patent\u002Ffigures\u002Fnumeral_index.md` if it exists (from `\u002Ffigure-description`)\n\n## Workflow\n\n### Step 1: Plan Embodiments\n\nFor each claim category (method, system, etc.), plan at least one embodiment:\n\n| Embodiment | Covers Claims | Type | Key Variations |\n|-----------|--------------|------|----------------|\n| 1 | Claims 1, X | Best mode \u002F preferred | [primary implementation] |\n| 2 | Claims 2, 3 | Alternative | [different parameters\u002Fmaterials] |\n| 3 | Claims 4, 5 | Additional alternative | [different configuration] |\n\n### Step 2: Write Each Embodiment\n\nFor each embodiment, write a detailed description following this structure:\n\n**Opening paragraph**:\n\"In one embodiment, [invention summary with reference to what is being described].\"\n\n**Component\u002Fstep-by-step description**:\n\nFor method embodiments:\n- Describe each step in order\n- Reference figure numerals: \"As shown in FIG. 1, at step 202, the processor 102 receives the input data 104...\"\n- Include specific parameters, ranges, and conditions\n- Describe what happens at each decision point\n\nFor system\u002Fapparatus embodiments:\n- Describe each component\n- Reference figure numerals: \"Referring to FIG. 1, the system 100 comprises a processor 102, a memory 104, and a communication interface 106...\"\n- Describe interconnections between components\n- Describe operation of the system step-by-step\n\n**Variations and alternatives**:\n- \"In some embodiments, the processor 102 may be a GPU, an FPGA, or an ASIC.\"\n- \"In another embodiment, the memory 104 may be replaced with a distributed storage system.\"\n- \"The parameters described above are exemplary; other values within the range [X, Y] are also contemplated.\"\n\nThese variations are critical -- they support broader claim interpretation.\n\n### Step 3: Reference Numeral Integration\n\nEnsure consistent reference numeral usage:\n\n1. Every component mentioned must have a numeral\n2. Numeral must appear first in parentheses after the component name: \"the processor (102)\"\n3. Subsequent references: \"the processor 102\" (no parentheses)\n4. Numbering follows figure series: 100-series for FIG. 1, 200-series for FIG. 2\n\n**Format**:\n- First mention: \"the processor (102)\"\n- Later in same embodiment: \"the processor 102\"\n- Cross-figure: \"the processor 102 (shown in both FIG. 1 and FIG. 2)\"\n\n### Step 4: Claim Support Verification\n\nFor each claim element, verify it appears in at least one embodiment:\n\n| Claim Element | Embodiment | Reference Numeral | Description Paragraph |\n|---------------|-----------|-------------------|----------------------|\n| [element] | [which] | [numeral] | [paragraph reference] |\n\nIf any claim element lacks embodiment support, add the necessary description.\n\n### Step 5: Software\u002FAlgorithm Embodiments (if applicable)\n\nFor method\u002Fsoftware inventions, include:\n- Pseudocode or algorithmic description (NOT actual code)\n- Flowchart description tied to figures\n- Data structure descriptions\n- Interface specifications\n\nExample:\n```\nIn one embodiment, the method comprises the following steps:\nAt step 202, the processor 102 receives input data from the input device 108.\nAt step 204, the processor 102 extracts feature vectors from the input data using a convolutional neural network.\nAt step 206, the processor 102 applies the attention mechanism 110 to the feature vectors...\n```\n\n### Step 6: Output\n\nEmbodiment sections are written to `patent\u002Fspecification\u002Fdetailed_description.md` (or appended to the specification structure).\n\nEach embodiment section should be self-contained but cross-reference other embodiments when describing alternatives.\n\n## Key Rules\n\n- Embodiments must teach a POSITA to make and use the invention without undue experimentation.\n- Include at least one \"best mode\" embodiment (US requirement).\n- Multiple embodiments strengthen the specification against enablement challenges.\n- Describe the invention, do NOT evaluate it empirically (\"The embodiment achieves 95% accuracy\" is wrong; \"The processor classifies the input data\" is correct).\n- **CRITICAL — NO experimental data, test results, accuracy percentages, detection rates, precision values, or comparative performance data.** These belong in papers, not patents. The embodiment teaches HOW to make and use, not HOW WELL it performs.\n- WRONG: \"传感器对直径超过150μm的金属颗粒实现了100%的检测精度，即使在检测限处仍保持94%的高精度。\"\n- RIGHT: \"当不锈钢颗粒通过间隙传感区域时，谐振频率下降。颗粒直径越大，频率偏移幅度越大。\"\n- Do NOT include tables of experimental results, graphs of measurement data, or comparisons with prior art performance.\n- **CRITICAL — An embodiment is NOT an experiment.** Do NOT describe \"repeated experiments\", \"accuracy evaluation\", \"precision testing\", \"calibration experiments\", or \"comparison with reference methods\". An embodiment describes ONE way to make and use the invention — it is a recipe, not a test report.\n- Do NOT copy experimental sections from source papers verbatim. Transform the experimental setup into a manufacturing\u002Foperation description.\n- If the source material is a paper, extract ONLY: (1) what was built, (2) what materials\u002Fparameters were used, (3) how it operates. Ignore all test methodology, results, and performance metrics.\n- Include specific parameters where possible, but frame them as exemplary, not limiting.\n- Reference numerals must be consistent with the figures.\n- Do NOT use subjective language (\"excellent\", \"surprising\", \"superior\").\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Bash(*), Read, Write, Edit, Grep, Glob","[claims-path-or-embodiment-details]","main","18193d71ea3441d7c033dbf195b8a7c75ac96f75","packages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fskills-codex\u002Fembodiment-description",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 embodiment-description",{"tool":40,"command":41},"bunx","bunx skills add CZX-LBJ\u002Fdeepseek-science --skill embodiment-description",{"tool":43,"command":44},"pnpm","pnpm dlx skills add CZX-LBJ\u002Fdeepseek-science --skill embodiment-description","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fskills-codex\u002Fembodiment-description\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",[],[]]