[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M791VRW2087ENBKRP3S01WVM":3,"skill-same:01M791VRW2087ENBKRP3S01WVM":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M791VRW2087ENBKRP3S01WVM","network-planning",null,"Plan OpenFE components, atom mappings, ligand networks, and RBFE\u002FRHFE alchemical networks before execution.","VectorSpaceLab\u002FAREX-Skill","VectorSpaceLab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F180637102?v=4","01M7538C5WPSJGWF7KHR4EFZ9F","01M7538C6R2GFP53NPXTCZNBRT",351,"MIT","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fopenfe\u002Fsub-skills\u002Fnetwork-planning\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: network-planning\ndescription: \"Plan OpenFE components, atom mappings, ligand networks, and\n  RBFE\u002FRHFE alchemical networks before execution.\"\ndisable-model-invocation: true\nmetadata:\n  disco-role: operating\nlicense: MIT\n---\n\n# Network Planning\n\nUse this sub-skill when a task is about building OpenFE inputs before simulation: components, atom mappings, ligand networks, RBFE\u002FRHFE alchemical networks, or deciding whether to use API planning, CLI planning, or manual network construction.\n\n## Start Here\n\n1. Validate ligand\u002Fprotein inputs with [validate_ligand_inputs.py](scripts\u002Fvalidate_ligand_inputs.py) before planning or diagnosing mapper failures.\n2. Use [API Reference](references\u002Fapi-reference.md) for constructors, mapper\u002Fscorer choices, ligand network functions, and RBFE\u002FRHFE planner data flow.\n3. Use [Workflows](references\u002Fworkflows.md) for end-to-end planning recipes, difficult diagnostics, and protocol handoff decisions.\n4. Use [Data Formats](references\u002Fdata-formats.md) for SDF\u002FMOL2\u002FPDB\u002FPDBx, GraphML ligand networks, alchemical-network JSON, and transformation JSON expectations.\n5. Use [Troubleshooting](references\u002Ftroubleshooting.md) for missing optional dependencies, invalid ligand names, unmapped edges, disconnected networks, charged transformations, malformed files, and immutable objects.\n\n## Scope\n\nThis sub-skill covers:\n\n- `SmallMoleculeComponent`, `ProteinComponent`, `ProteinMembraneComponent`, `SolventComponent`, `ChemicalSystem`, `LigandAtomMapping`, and `LigandNetwork` construction concepts.\n- `LomapAtomMapper`, `KartografAtomMapper`, `PersesAtomMapper`, `lomap_scorers`, `perses_scorers`, and `openfe.setup.ligand_network_planning` functions.\n- `RBFEAlchemicalNetworkPlanner`, `RHFEAlchemicalNetworkPlanner`, and the `RelativeAlchemicalNetworkPlanner` data flow from ligands to `AlchemicalNetwork`, including the difference between Python planner defaults and CLI planning defaults.\n- Pre-execution route decisions: API vs CLI planning, topology choice, mapper\u002Fscorer tradeoffs, and when to hand a plan to protocol or CLI execution guidance.\n\nRoute elsewhere:\n\n- Protocol settings, OpenMM backend choices, adaptive settings details, and simulation configuration -> [protocols](..\u002Fprotocols\u002FSKILL.md).\n- CLI flag syntax, `openfe plan-*`, `openfe quickrun`, repeat job construction, and `gather*` command use -> [cli-workflows](..\u002Fcli-workflows\u002FSKILL.md).\n- Post-run estimates, uncertainties, failed edge summaries, and result aggregation -> [results-analysis](..\u002Fresults-analysis\u002FSKILL.md).\n\n## Safe Default Pattern\n\n- Do input checks first; do not run OpenMM while diagnosing planning failures.\n- Prefer unique, explicit ligand names before creating networks; duplicate or empty names can create ambiguous radial centers and duplicate transformation labels.\n- Start with a maximal network to debug mapper coverage, then choose minimal spanning, redundant minimal spanning, radial, or explicit edges based on campaign needs.\n- Treat OpenFE components, mappings, and networks as immutable; rebuild them from corrected inputs rather than mutating them in place.\n- For charged transformations, identify the affected ligand pairs during planning and hand protocol-setting decisions to [protocols](..\u002Fprotocols\u002FSKILL.md).\n","# Network Planning\n\nUse this sub-skill when a task is about building OpenFE inputs before simulation: components, atom mappings, ligand networks, RBFE\u002FRHFE alchemical networks, or deciding whether to use API planning, CLI planning, or manual network construction.\n\n## Start Here\n\n1. Validate ligand\u002Fprotein inputs with [validate_ligand_inputs.py](scripts\u002Fvalidate_ligand_inputs.py) before planning or diagnosing mapper failures.\n2. Use [API Reference](references\u002Fapi-reference.md) for constructors, mapper\u002Fscorer choices, ligand network functions, and RBFE\u002FRHFE planner data flow.\n3. Use [Workflows](references\u002Fworkflows.md) for end-to-end planning recipes, difficult diagnostics, and protocol handoff decisions.\n4. Use [Data Formats](references\u002Fdata-formats.md) for SDF\u002FMOL2\u002FPDB\u002FPDBx, GraphML ligand networks, alchemical-network JSON, and transformation JSON expectations.\n5. Use [Troubleshooting](references\u002Ftroubleshooting.md) for missing optional dependencies, invalid ligand names, unmapped edges, disconnected networks, charged transformations, malformed files, and immutable objects.\n\n## Scope\n\nThis sub-skill covers:\n\n- `SmallMoleculeComponent`, `ProteinComponent`, `ProteinMembraneComponent`, `SolventComponent`, `ChemicalSystem`, `LigandAtomMapping`, and `LigandNetwork` construction concepts.\n- `LomapAtomMapper`, `KartografAtomMapper`, `PersesAtomMapper`, `lomap_scorers`, `perses_scorers`, and `openfe.setup.ligand_network_planning` functions.\n- `RBFEAlchemicalNetworkPlanner`, `RHFEAlchemicalNetworkPlanner`, and the `RelativeAlchemicalNetworkPlanner` data flow from ligands to `AlchemicalNetwork`, including the difference between Python planner defaults and CLI planning defaults.\n- Pre-execution route decisions: API vs CLI planning, topology choice, mapper\u002Fscorer tradeoffs, and when to hand a plan to protocol or CLI execution guidance.\n\nRoute elsewhere:\n\n- Protocol settings, OpenMM backend choices, adaptive settings details, and simulation configuration -> [protocols](..\u002Fprotocols\u002FSKILL.md).\n- CLI flag syntax, `openfe plan-*`, `openfe quickrun`, repeat job construction, and `gather*` command use -> [cli-workflows](..\u002Fcli-workflows\u002FSKILL.md).\n- Post-run estimates, uncertainties, failed edge summaries, and result aggregation -> [results-analysis](..\u002Fresults-analysis\u002FSKILL.md).\n\n## Safe Default Pattern\n\n- Do input checks first; do not run OpenMM while diagnosing planning failures.\n- Prefer unique, explicit ligand names before creating networks; duplicate or empty names can create ambiguous radial centers and duplicate transformation labels.\n- Start with a maximal network to debug mapper coverage, then choose minimal spanning, redundant minimal spanning, radial, or explicit edges based on campaign needs.\n- Treat OpenFE components, mappings, and networks as immutable; rebuild them from corrected inputs rather than mutating them in place.\n- For charged transformations, identify the affected ligand pairs during planning and hand protocol-setting decisions to [protocols](..\u002Fprotocols\u002FSKILL.md).\n",{"name":5,"license":14,"metadata":23,"description":7,"disable-model-invocation":25},{"disco-role":24},"operating",true,"main","ac3fe1afa80fb9a09775ecfb2b6cc3ba850a2db6","skills\u002Frepositories\u002Frepo-skills\u002Fopenfe\u002Fsub-skills\u002Fnetwork-planning",27,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab","2026-09-03 10:25:21",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add VectorSpaceLab\u002FAREX-Skill --skill network-planning",{"tool":39,"command":40},"bunx","bunx skills add VectorSpaceLab\u002FAREX-Skill --skill network-planning",{"tool":42,"command":43},"pnpm","pnpm dlx skills add VectorSpaceLab\u002FAREX-Skill --skill network-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fopenfe\u002Fsub-skills\u002Fnetwork-planning\u002FSKILL.md",[46,52,56,60,64],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fapi-reference.md","REFERENCE","参考文档",10975,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fopenfe\u002Fsub-skills\u002Fnetwork-planning\u002Freferences\u002Fapi-reference.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fdata-formats.md",6580,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fopenfe\u002Fsub-skills\u002Fnetwork-planning\u002Freferences\u002Fdata-formats.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Ftroubleshooting.md",8071,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fopenfe\u002Fsub-skills\u002Fnetwork-planning\u002Freferences\u002Ftroubleshooting.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fworkflows.md",10347,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fopenfe\u002Fsub-skills\u002Fnetwork-planning\u002Freferences\u002Fworkflows.md",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"scripts\u002Fvalidate_ligand_inputs.py","SCRIPT","脚本",13665,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fopenfe\u002Fsub-skills\u002Fnetwork-planning\u002Fscripts\u002Fvalidate_ligand_inputs.py",[71,79,86,93,100,107],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M799NYSH1R3RVAHSM2D88Y84","passnet-triton-opt","Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block\u002Fgrid\u002Fwarp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-triton-opt\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M799NS5APEC0N1FZ7XZVW6BN","passnet-solve","END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-solve\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M799NNY9BKSM21V5R7QVTBJX","passnet-skill","PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under .\u002Fpass_dir\u002F, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-skill\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M799NHH6NP7Z1RK77KGXAN6S","passnet-pattern-fusion","Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()\u002Freplacement_args()\u002Freplacement_func() files, when a pass \"failed to match\", or when deciding how to fuse multiple kernels\u002Fops.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-pattern-fusion\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":18},"01M799ND2J4WNC2PGAZ0A06NDF","passnet-orchestrate","Round\u002Fbatch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep\u002Frevert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-orchestrate\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":18},"01M799N8SBTMY02ZDG2AZF5ZWE","passnet-feedback","Fast, deterministic feedback for PassNet work: pre-flight pattern\u002Fmatch verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-feedback\u002FSKILL.md",[],[]]