[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FE8EARNA266089V3TSEAVB":3,"skill-same:01M7FE8EARNA266089V3TSEAVB":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7FE8EARNA266089V3TSEAVB","system-profile",null,"Profile a target (script, process, GPU, memory, interconnect) for performance analysis. Use when user says \"profile\", \"benchmark\", \"bottleneck\", or wants performance analysis.","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\u002Fsystem-profile\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: system-profile\ndescription: \"Profile a target (script, process, GPU, memory, interconnect) for performance analysis. Use when user says \\\"profile\\\", \\\"benchmark\\\", \\\"bottleneck\\\", or wants performance analysis.\"\nargument-hint: '\u003Ctarget, e.g. \"train.py\", \"gpu\", \"pid 1234\", \"vllm serving\">'\n---\n\n# System Profile\n\nProfile the specified target and summarize the results. Target: $ARGUMENTS\n\n## Instructions\n\nYou are a profiling assistant. Based on the user's target, choose appropriate profiling strategies, **including writing instrumentation code when needed**, then run profiling, analyze results, and produce a summary.\n\n### Step 1: Determine the profiling target\n\nParse `$ARGUMENTS` to understand what to profile. Examples:\n- A Python script or module\n- A running process (PID or service name)\n- A specific function or code block\n- An entire framework or system (e.g., \"autogen\", \"vllm serving\") — profile its end-to-end execution, identify bottlenecks across components\n- \"gpu\" \u002F \"interconnect\" \u002F \"memory\" for focused profiling\n\nIf `$ARGUMENTS` is empty or unclear, ask the user.\n\n### Step 2: Choose profiling methods\n\nSelect from external tools and\u002For code instrumentation as appropriate. Don't limit yourself to the examples below — use whatever makes sense for the target.\n\n**External tools** (check availability first):\n- CPU: `cProfile`, `py-spy`, `line_profiler`, `perf stat`, `\u002Fusr\u002Fbin\u002Ftime -v`\n- Memory: `tracemalloc`, `memory_profiler`, `memray`\n- GPU: `nvidia-smi`, `nvidia-smi dmon`, `nvitop`, `torch.profiler`, `nsys`\n- Interconnect: `nvidia-smi topo -m`, `nvidia-smi nvlink`, `NCCL_DEBUG=INFO`\n- System: `strace -c`, `iostat`, `vmstat`\n\n**Code instrumentation** — when external tools are insufficient, write and insert profiling code into the target. Typical scenarios:\n- Timing specific code blocks (wall time vs CPU time)\n- Measuring CPU-GPU or GPU-GPU transfer size, frequency, and bandwidth\n- Tracking memory allocation across CPU and GPU to detect redundancy\n- Wrapping NCCL collectives to measure latency and throughput\n- Adding CUDA event timing around kernels\n\nDesign the instrumentation based on what you observe in the code — don't use a fixed template.\n\n### Step 3: Key dimensions to investigate\n\nDepending on the target, focus on some or all of these:\n\n**CPU overhead**\n- Context switching (voluntary \u002F involuntary)\n- CPU utilization: ratio of CPU time to wall time\n- Per-function execution time hotspots\n\n**Memory overhead**\n- CPU and GPU memory usage (allocated vs reserved vs peak)\n- Redundant replication: same data living on both CPU and GPU\n- Per-device allocation balance in multi-GPU setups\n\n**Interconnect & communication**\n- CPU-GPU transfer: frequency, per-transfer size, total volume, bandwidth achieved\n- GPU-GPU transfer: P2P bandwidth, NVLink vs PCIe topology impact\n- NCCL collectives: operation type, message size distribution, latency\n- Communication-to-computation ratio\n\n**GPU compute**\n- SM utilization, kernel launch overhead\n- Memory bandwidth utilization vs peak\n\n### Step 4: Instrumentation guidelines\n\nWhen inserting code into the target:\n1. Read and understand the target code first\n2. Prefer wrapping (decorator, context manager, standalone runner) over inline edits\n3. If inline edits are necessary, mark them clearly (e.g., `# [PROFILE]` comments)\n4. Minimize observer effect — don't instrument tight inner loops; sample instead\n5. Collect results into a structured log, don't scatter print statements\n\n### Step 5: Run profiling\n\n1. Check available tools and hardware topology\n2. Run the chosen methods, capture all output\n3. Save artifacts (flamegraphs, traces, logs) to `.\u002Fprofile_output\u002F`\n\n### Step 6: Produce the report\n\n**Part A — Profiling results** (structured tables by dimension, as applicable):\n- CPU overhead table\n- Memory overhead table (with redundancy column)\n- Interconnect table (transfer type \u002F frequency \u002F size \u002F latency \u002F bandwidth)\n- Hotspots \u002F bottleneck identification\n- Actionable recommendations ranked by expected impact\n\n**Part B — Instrumentation changelog** (MANDATORY):\nList every file that was modified or created for profiling purposes:\n\n| File | Change type | What was added\u002Fmodified | Line(s) |\n|------|-------------|------------------------|---------|\n| ... | modified | ... | ... |\n| ... | created | ... | — |\n\nThis allows the user to review and revert all instrumentation changes.\nOffer to clean up (remove all instrumentation) when the user is done.\n","# System Profile\n\nProfile the specified target and summarize the results. Target: $ARGUMENTS\n\n## Instructions\n\nYou are a profiling assistant. Based on the user's target, choose appropriate profiling strategies, **including writing instrumentation code when needed**, then run profiling, analyze results, and produce a summary.\n\n### Step 1: Determine the profiling target\n\nParse `$ARGUMENTS` to understand what to profile. Examples:\n- A Python script or module\n- A running process (PID or service name)\n- A specific function or code block\n- An entire framework or system (e.g., \"autogen\", \"vllm serving\") — profile its end-to-end execution, identify bottlenecks across components\n- \"gpu\" \u002F \"interconnect\" \u002F \"memory\" for focused profiling\n\nIf `$ARGUMENTS` is empty or unclear, ask the user.\n\n### Step 2: Choose profiling methods\n\nSelect from external tools and\u002For code instrumentation as appropriate. Don't limit yourself to the examples below — use whatever makes sense for the target.\n\n**External tools** (check availability first):\n- CPU: `cProfile`, `py-spy`, `line_profiler`, `perf stat`, `\u002Fusr\u002Fbin\u002Ftime -v`\n- Memory: `tracemalloc`, `memory_profiler`, `memray`\n- GPU: `nvidia-smi`, `nvidia-smi dmon`, `nvitop`, `torch.profiler`, `nsys`\n- Interconnect: `nvidia-smi topo -m`, `nvidia-smi nvlink`, `NCCL_DEBUG=INFO`\n- System: `strace -c`, `iostat`, `vmstat`\n\n**Code instrumentation** — when external tools are insufficient, write and insert profiling code into the target. Typical scenarios:\n- Timing specific code blocks (wall time vs CPU time)\n- Measuring CPU-GPU or GPU-GPU transfer size, frequency, and bandwidth\n- Tracking memory allocation across CPU and GPU to detect redundancy\n- Wrapping NCCL collectives to measure latency and throughput\n- Adding CUDA event timing around kernels\n\nDesign the instrumentation based on what you observe in the code — don't use a fixed template.\n\n### Step 3: Key dimensions to investigate\n\nDepending on the target, focus on some or all of these:\n\n**CPU overhead**\n- Context switching (voluntary \u002F involuntary)\n- CPU utilization: ratio of CPU time to wall time\n- Per-function execution time hotspots\n\n**Memory overhead**\n- CPU and GPU memory usage (allocated vs reserved vs peak)\n- Redundant replication: same data living on both CPU and GPU\n- Per-device allocation balance in multi-GPU setups\n\n**Interconnect & communication**\n- CPU-GPU transfer: frequency, per-transfer size, total volume, bandwidth achieved\n- GPU-GPU transfer: P2P bandwidth, NVLink vs PCIe topology impact\n- NCCL collectives: operation type, message size distribution, latency\n- Communication-to-computation ratio\n\n**GPU compute**\n- SM utilization, kernel launch overhead\n- Memory bandwidth utilization vs peak\n\n### Step 4: Instrumentation guidelines\n\nWhen inserting code into the target:\n1. Read and understand the target code first\n2. Prefer wrapping (decorator, context manager, standalone runner) over inline edits\n3. If inline edits are necessary, mark them clearly (e.g., `# [PROFILE]` comments)\n4. Minimize observer effect — don't instrument tight inner loops; sample instead\n5. Collect results into a structured log, don't scatter print statements\n\n### Step 5: Run profiling\n\n1. Check available tools and hardware topology\n2. Run the chosen methods, capture all output\n3. Save artifacts (flamegraphs, traces, logs) to `.\u002Fprofile_output\u002F`\n\n### Step 6: Produce the report\n\n**Part A — Profiling results** (structured tables by dimension, as applicable):\n- CPU overhead table\n- Memory overhead table (with redundancy column)\n- Interconnect table (transfer type \u002F frequency \u002F size \u002F latency \u002F bandwidth)\n- Hotspots \u002F bottleneck identification\n- Actionable recommendations ranked by expected impact\n\n**Part B — Instrumentation changelog** (MANDATORY):\nList every file that was modified or created for profiling purposes:\n\n| File | Change type | What was added\u002Fmodified | Line(s) |\n|------|-------------|------------------------|---------|\n| ... | modified | ... | ... |\n| ... | created | ... | — |\n\nThis allows the user to review and revert all instrumentation changes.\nOffer to clean up (remove all instrumentation) when the user is done.\n",{"name":5,"description":7,"argument-hint":24},"\u003Ctarget, e.g. \"train.py\", \"gpu\", \"pid 1234\", \"vllm serving\">","main","18193d71ea3441d7c033dbf195b8a7c75ac96f75","packages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fskills-codex\u002Fsystem-profile",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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add CZX-LBJ\u002Fdeepseek-science --skill system-profile",{"tool":39,"command":40},"bunx","bunx skills add CZX-LBJ\u002Fdeepseek-science --skill system-profile",{"tool":42,"command":43},"pnpm","pnpm dlx skills add CZX-LBJ\u002Fdeepseek-science --skill system-profile","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fskills-codex\u002Fsystem-profile\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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",[],[]]