[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FCZW55MF684TYH2SR5GNS5":3,"skill-same:01M7FCZW55MF684TYH2SR5GNS5":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},"01M7FCZW55MF684TYH2SR5GNS5","formula-derivation",null,"Structures and derives research formulas when the user wants to 推导公式, build a theory line, organize assumptions, turn scattered equations into a coherent derivation, or rewrite theory notes into a paper-ready formula document. Use when the derivation target is not yet fully fixed, the main object still needs to be chosen, or the user needs a coherent derivation package rather than a finished theorem proof.","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\u002Fformula-derivation\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: formula-derivation\ndescription: Structures and derives research formulas when the user wants to 推导公式, build a theory line, organize assumptions, turn scattered equations into a coherent derivation, or rewrite theory notes into a paper-ready formula document. Use when the derivation target is not yet fully fixed, the main object still needs to be chosen, or the user needs a coherent derivation package rather than a finished theorem proof.\nargument-hint: \"[problem-goal-current-formulas-or-notes]\"\nallowed-tools: Read, Write, Edit, Grep, Glob, Skill(lean-formalize)\n---\n\n# Formula Derivation: Research Theory Line Construction\n\nBuild an honest derivation package, not a fake polished theorem story.\n\n## Constants\n\n- DEFAULT_DERIVATION_DOC = `DERIVATION_PACKAGE.md` in project root\n- STATUS = `COHERENT AS STATED | COHERENT AFTER REFRAMING \u002F EXTRA ASSUMPTION | NOT YET COHERENT`\n\n## Context: $ARGUMENTS\n\n## Goal\n\nProduce exactly one of:\n1. a coherent derivation package for the original target\n2. a reframed derivation package with corrected object \u002F assumptions \u002F scope\n3. a blocker report explaining why the current notes cannot yet support a coherent derivation\n\n## Inputs\n\nExtract and normalize:\n- the target phenomenon, formula, relation, or theory line\n- the intended role of the derivation:\n  - exact identity \u002F algebra\n  - proposition \u002F local theorem\n  - approximation\n  - mechanism interpretation\n- explicit assumptions\n- notation and definitions\n- any user-provided formula chain, sketch, messy notes, or current draft\n- nearby local theory files if the request points to them\n- desired output style if specified:\n  - internal alignment note\n  - paper-style theory draft\n  - blocker report\n\nIf the target, object, notation, or assumptions are ambiguous, state the exact interpretation you are using before deriving anything.\n\n## Workflow\n\n### Step 1: Gather Derivation Context\nDetermine the target derivation file with this priority:\n1. a file path explicitly specified by the user\n2. a derivation draft already referenced in local notes\n3. `DERIVATION_PACKAGE.md` in project root as the default target\n\nRead the relevant local context:\n- the chosen target derivation file, if it already exists\n- any local theory notes, formula drafts, appendix notes, or files explicitly mentioned by the user\n\nExtract:\n- target formula \u002F theory goal\n- current formula chain\n- assumptions\n- notation\n- known blockers\n- desired output mode\n\n### Step 2: Freeze the Target\nState explicitly:\n- what is being explained, derived, or supported\n- whether the immediate goal is:\n  - identity \u002F algebra\n  - proposition\n  - approximation\n  - interpretation\n- what the derivation is expected to output in the end\n\nDo not start symbolic manipulation before this is fixed.\n\n### Step 3: Choose the Invariant Object\nIdentify the single quantity or conceptual object that should organize the derivation.\n\nTypical possibilities include:\n- objective \u002F utility \u002F loss\n- total cost \u002F energy \u002F welfare\n- conserved quantity \u002F state variable\n- expected metric \u002F effective rate \u002F effective cost\n\nIf the current notes start from a narrower quantity, decide explicitly whether it is:\n- the true top-level object\n- a proxy\n- a local slice\n- an approximation\n\nDo not let a convenient proxy silently replace the actual conceptual object.\n\n### Step 4: Normalize Assumptions and Notation\nRestate:\n- all assumptions\n- all symbols\n- regime boundaries or special cases\n- which quantities are fixed, adaptive, or state dependent\n\nIdentify:\n- hidden assumptions\n- undefined notation\n- scope ambiguities\n- whether the current formula chain already mixes exact steps with approximations\n\nPreserve the user's original notation unless a cleanup is necessary for coherence.\nIf you adopt a cleaner internal formulation, keep that as a derivation device rather than silently replacing the user's target.\n\n### Step 5: Classify the Derivation Steps\nFor every nontrivial step, determine whether it is:\n- **identity**: exact algebraic reformulation\n- **proposition**: a claim requiring conditions\n- **approximation**: model simplification or surrogate\n- **interpretation**: prose-level meaning of a formula\n\nNever merge these categories without signaling the transition.\nIf one part is only interpretive, do not present it as if it were mathematically proved.\n\n### Step 6: Build a Derivation Map\nChoose a derivation strategy, for example:\n- definition -> substitution -> simplification\n- primitive law -> intermediate variable -> target expression\n- global quantity -> perturbation -> decomposition\n- exact model -> approximation -> interpretable closed form\n- general dynamic object -> simplified slice -> local theorem -> return to general case\n\nThen write a derivation map:\n- target formula or theory line\n- required intermediate identities or lemmas\n- which assumptions each nontrivial step uses\n- where approximations enter\n- where special-case and general-case regimes diverge or collapse\n\nIf the derivation needs a decomposition, derive it from the chosen global quantity.\nDo not make a split appear magically from one local variable itself.\n\n### Step 7: Write the Derivation Document\nWrite to the chosen target derivation file.\n\nIf the target derivation file already exists:\n- read it first\n- update the relevant section\n- do not blindly duplicate prior content\n\nIf the user does not specify a target, default to `DERIVATION_PACKAGE.md` in project root.\n\nDo NOT write directly into paper sections or appendix `.tex` files unless the user explicitly asks for that target.\n\nThe derivation package must include:\n- target\n- status\n- invariant object\n- assumptions\n- notation\n- derivation strategy\n- derivation map\n- main derivation steps\n- remarks \u002F interpretations\n- boundaries and non-claims\n\nWriting rules:\n- do not hide gaps with words like \"clearly\", \"obviously\", or \"similarly\"\n- define every symbol before use\n- mark approximations explicitly\n- separate derivation body from remarks\n- if the true object is dynamic or state dependent but a simpler slice is analyzed, say so explicitly\n- if a formula line is only heuristic, label it honestly\n\n### Step 8: Final Verification\nBefore finishing the target derivation file, verify:\n- the target is explicit\n- the invariant object is stable across the derivation\n- every assumption used is stated\n- each formula step is correctly labeled as identity \u002F proposition \u002F approximation \u002F interpretation\n- the derivation does not silently switch objects\n- special cases and general cases still belong to one theory line\n- boundaries and non-claims are stated\n\nIf the derivation still lacks a coherent object, stable assumptions, or an honest path from premises to result, downgrade the status and write a blocker report instead of forcing a clean story.\n\n## Required File Structure\n\nWrite the target derivation file using this structure:\n\n```md\n# Derivation Package\n\n## Target\n[what is being derived or explained]\n\n## Status\nCOHERENT AS STATED \u002F COHERENT AFTER REFRAMING \u002F NOT YET COHERENT\n\n## Invariant Object\n[top-level quantity organizing the derivation]\n\n## Assumptions\n- ...\n\n## Notation\n- ...\n\n## Derivation Strategy\n[chosen route and why]\n\n## Derivation Map\n1. Target depends on ...\n2. Intermediate step A uses ...\n3. Approximation enters at ...\n\n## Main Derivation\nStep 1. ...\nStep 2. ...\n...\n\n## Remarks and Interpretation\n- ...\n\n## Boundaries and Non-Claims\n- ...\n\n## Open Risks\n- ...\n```\n\n## Output Modes\n\n### If the derivation is coherent as stated\nWrite the full structure above with a clean derivation package.\n\n### If the notes are close but not coherent yet\nWrite:\n- the exact mismatch\n- the corrected invariant object, assumption, or scope\n- the reframed derivation package\n\n### If the derivation cannot be made coherent honestly\nWrite:\n- `Status: NOT YET COHERENT`\n- the exact blocker:\n  - missing object\n  - unstable assumptions\n  - notation conflict\n  - unsupported approximation\n  - theorem-level claim without enough conditions\n- what extra assumption, reframe, or intermediate derivation would be needed\n\n## Relationship to `proof-writer`\n\nUse `formula-derivation` when the user says things like:\n- “我不知道怎么起这条推导主线”\n- “这个公式到底该从哪个量出发”\n- “帮我把理论搭顺”\n- “把说明文档变成可写进论文的公式文档”\n- “这几段公式之间逻辑不通”\n\nUse `proof-writer` only after:\n- the exact claim is fixed\n- the assumptions are stable\n- the notation is settled\n- and the task is now to prove or refute that claim rigorously\n\nOnce a precise claim and its hypotheses are available, use\n[`\u002Flean-formalize`](..\u002Flean-formalize\u002FSKILL.md) when the user requests Lean or a\nspecific proof obligation benefits from formal implementation and checking;\nroutine algebraic derivations do not require it.\n\n## Chat Response\n\nAfter writing the target derivation file, respond briefly with:\n- status\n- whether the target survived unchanged or had to be reframed\n- what file was updated\n\n## Key Rules\n\n- Never fabricate a coherent derivation if the object, assumptions, or scope do not support one.\n- Prefer reframing the derivation over overclaiming.\n- Separate assumptions, identities, propositions, approximations, and interpretations.\n- Keep one invariant object across special and general cases whenever possible.\n- Treat simplified constant-parameter cases as analysis slices, not as the conceptual main object.\n- If uncertainty remains, mark it explicitly in `Open Risks`; do not hide it in polished prose.\n- Coherence matters more than elegance.\n","# Formula Derivation: Research Theory Line Construction\n\nBuild an honest derivation package, not a fake polished theorem story.\n\n## Constants\n\n- DEFAULT_DERIVATION_DOC = `DERIVATION_PACKAGE.md` in project root\n- STATUS = `COHERENT AS STATED | COHERENT AFTER REFRAMING \u002F EXTRA ASSUMPTION | NOT YET COHERENT`\n\n## Context: $ARGUMENTS\n\n## Goal\n\nProduce exactly one of:\n1. a coherent derivation package for the original target\n2. a reframed derivation package with corrected object \u002F assumptions \u002F scope\n3. a blocker report explaining why the current notes cannot yet support a coherent derivation\n\n## Inputs\n\nExtract and normalize:\n- the target phenomenon, formula, relation, or theory line\n- the intended role of the derivation:\n  - exact identity \u002F algebra\n  - proposition \u002F local theorem\n  - approximation\n  - mechanism interpretation\n- explicit assumptions\n- notation and definitions\n- any user-provided formula chain, sketch, messy notes, or current draft\n- nearby local theory files if the request points to them\n- desired output style if specified:\n  - internal alignment note\n  - paper-style theory draft\n  - blocker report\n\nIf the target, object, notation, or assumptions are ambiguous, state the exact interpretation you are using before deriving anything.\n\n## Workflow\n\n### Step 1: Gather Derivation Context\nDetermine the target derivation file with this priority:\n1. a file path explicitly specified by the user\n2. a derivation draft already referenced in local notes\n3. `DERIVATION_PACKAGE.md` in project root as the default target\n\nRead the relevant local context:\n- the chosen target derivation file, if it already exists\n- any local theory notes, formula drafts, appendix notes, or files explicitly mentioned by the user\n\nExtract:\n- target formula \u002F theory goal\n- current formula chain\n- assumptions\n- notation\n- known blockers\n- desired output mode\n\n### Step 2: Freeze the Target\nState explicitly:\n- what is being explained, derived, or supported\n- whether the immediate goal is:\n  - identity \u002F algebra\n  - proposition\n  - approximation\n  - interpretation\n- what the derivation is expected to output in the end\n\nDo not start symbolic manipulation before this is fixed.\n\n### Step 3: Choose the Invariant Object\nIdentify the single quantity or conceptual object that should organize the derivation.\n\nTypical possibilities include:\n- objective \u002F utility \u002F loss\n- total cost \u002F energy \u002F welfare\n- conserved quantity \u002F state variable\n- expected metric \u002F effective rate \u002F effective cost\n\nIf the current notes start from a narrower quantity, decide explicitly whether it is:\n- the true top-level object\n- a proxy\n- a local slice\n- an approximation\n\nDo not let a convenient proxy silently replace the actual conceptual object.\n\n### Step 4: Normalize Assumptions and Notation\nRestate:\n- all assumptions\n- all symbols\n- regime boundaries or special cases\n- which quantities are fixed, adaptive, or state dependent\n\nIdentify:\n- hidden assumptions\n- undefined notation\n- scope ambiguities\n- whether the current formula chain already mixes exact steps with approximations\n\nPreserve the user's original notation unless a cleanup is necessary for coherence.\nIf you adopt a cleaner internal formulation, keep that as a derivation device rather than silently replacing the user's target.\n\n### Step 5: Classify the Derivation Steps\nFor every nontrivial step, determine whether it is:\n- **identity**: exact algebraic reformulation\n- **proposition**: a claim requiring conditions\n- **approximation**: model simplification or surrogate\n- **interpretation**: prose-level meaning of a formula\n\nNever merge these categories without signaling the transition.\nIf one part is only interpretive, do not present it as if it were mathematically proved.\n\n### Step 6: Build a Derivation Map\nChoose a derivation strategy, for example:\n- definition -> substitution -> simplification\n- primitive law -> intermediate variable -> target expression\n- global quantity -> perturbation -> decomposition\n- exact model -> approximation -> interpretable closed form\n- general dynamic object -> simplified slice -> local theorem -> return to general case\n\nThen write a derivation map:\n- target formula or theory line\n- required intermediate identities or lemmas\n- which assumptions each nontrivial step uses\n- where approximations enter\n- where special-case and general-case regimes diverge or collapse\n\nIf the derivation needs a decomposition, derive it from the chosen global quantity.\nDo not make a split appear magically from one local variable itself.\n\n### Step 7: Write the Derivation Document\nWrite to the chosen target derivation file.\n\nIf the target derivation file already exists:\n- read it first\n- update the relevant section\n- do not blindly duplicate prior content\n\nIf the user does not specify a target, default to `DERIVATION_PACKAGE.md` in project root.\n\nDo NOT write directly into paper sections or appendix `.tex` files unless the user explicitly asks for that target.\n\nThe derivation package must include:\n- target\n- status\n- invariant object\n- assumptions\n- notation\n- derivation strategy\n- derivation map\n- main derivation steps\n- remarks \u002F interpretations\n- boundaries and non-claims\n\nWriting rules:\n- do not hide gaps with words like \"clearly\", \"obviously\", or \"similarly\"\n- define every symbol before use\n- mark approximations explicitly\n- separate derivation body from remarks\n- if the true object is dynamic or state dependent but a simpler slice is analyzed, say so explicitly\n- if a formula line is only heuristic, label it honestly\n\n### Step 8: Final Verification\nBefore finishing the target derivation file, verify:\n- the target is explicit\n- the invariant object is stable across the derivation\n- every assumption used is stated\n- each formula step is correctly labeled as identity \u002F proposition \u002F approximation \u002F interpretation\n- the derivation does not silently switch objects\n- special cases and general cases still belong to one theory line\n- boundaries and non-claims are stated\n\nIf the derivation still lacks a coherent object, stable assumptions, or an honest path from premises to result, downgrade the status and write a blocker report instead of forcing a clean story.\n\n## Required File Structure\n\nWrite the target derivation file using this structure:\n\n```md\n# Derivation Package\n\n## Target\n[what is being derived or explained]\n\n## Status\nCOHERENT AS STATED \u002F COHERENT AFTER REFRAMING \u002F NOT YET COHERENT\n\n## Invariant Object\n[top-level quantity organizing the derivation]\n\n## Assumptions\n- ...\n\n## Notation\n- ...\n\n## Derivation Strategy\n[chosen route and why]\n\n## Derivation Map\n1. Target depends on ...\n2. Intermediate step A uses ...\n3. Approximation enters at ...\n\n## Main Derivation\nStep 1. ...\nStep 2. ...\n...\n\n## Remarks and Interpretation\n- ...\n\n## Boundaries and Non-Claims\n- ...\n\n## Open Risks\n- ...\n```\n\n## Output Modes\n\n### If the derivation is coherent as stated\nWrite the full structure above with a clean derivation package.\n\n### If the notes are close but not coherent yet\nWrite:\n- the exact mismatch\n- the corrected invariant object, assumption, or scope\n- the reframed derivation package\n\n### If the derivation cannot be made coherent honestly\nWrite:\n- `Status: NOT YET COHERENT`\n- the exact blocker:\n  - missing object\n  - unstable assumptions\n  - notation conflict\n  - unsupported approximation\n  - theorem-level claim without enough conditions\n- what extra assumption, reframe, or intermediate derivation would be needed\n\n## Relationship to `proof-writer`\n\nUse `formula-derivation` when the user says things like:\n- “我不知道怎么起这条推导主线”\n- “这个公式到底该从哪个量出发”\n- “帮我把理论搭顺”\n- “把说明文档变成可写进论文的公式文档”\n- “这几段公式之间逻辑不通”\n\nUse `proof-writer` only after:\n- the exact claim is fixed\n- the assumptions are stable\n- the notation is settled\n- and the task is now to prove or refute that claim rigorously\n\nOnce a precise claim and its hypotheses are available, use\n[`\u002Flean-formalize`](..\u002Flean-formalize\u002FSKILL.md) when the user requests Lean or a\nspecific proof obligation benefits from formal implementation and checking;\nroutine algebraic derivations do not require it.\n\n## Chat Response\n\nAfter writing the target derivation file, respond briefly with:\n- status\n- whether the target survived unchanged or had to be reframed\n- what file was updated\n\n## Key Rules\n\n- Never fabricate a coherent derivation if the object, assumptions, or scope do not support one.\n- Prefer reframing the derivation over overclaiming.\n- Separate assumptions, identities, propositions, approximations, and interpretations.\n- Keep one invariant object across special and general cases whenever possible.\n- Treat simplified constant-parameter cases as analysis slices, not as the conceptual main object.\n- If uncertainty remains, mark it explicitly in `Open Risks`; do not hide it in polished prose.\n- Coherence matters more than elegance.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Read, Write, Edit, Grep, Glob, Skill(lean-formalize)","[problem-goal-current-formulas-or-notes]","main","18193d71ea3441d7c033dbf195b8a7c75ac96f75","packages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fformula-derivation",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 formula-derivation",{"tool":40,"command":41},"bunx","bunx skills add CZX-LBJ\u002Fdeepseek-science --skill formula-derivation",{"tool":43,"command":44},"pnpm","pnpm dlx skills add CZX-LBJ\u002Fdeepseek-science --skill formula-derivation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fformula-derivation\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",[],[]]