[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DC57RSTF5QV9KEVM907J35":3,"skill-same:01M6DC57RSTF5QV9KEVM907J35":88},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":14,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M6DC57RSTF5QV9KEVM907J35","windows-virtualization-conflict-triage",null,"Use when Hyper-V, VBS, VMware Workstation, vmware-vmx, vmrun, Docker, or WSL conflict on a Windows host and you need a safe diagnosis before changing host virtualization settings.","Prekzursil\u002Fagent-skills-toolchain","Prekzursil","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54636077?v=4","01M6DACZ1PCQHD99SCR1YXG28B","Andrei Mihai Visalon","01M6DACZ670WZF535V3WYYSS4Z",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwindows-virtualization-conflict-triage\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"triage","windows","conflict","windows virtualization conflict triage","safe","docker","settings","use","host","diagnosis","2026-11-10 10:12:30",false,"---\nname: windows-virtualization-conflict-triage\ndescription: Use when Hyper-V, VBS, VMware Workstation, vmware-vmx, vmrun, Docker, or WSL conflict on a Windows host and you need a safe diagnosis before changing host virtualization settings.\n---\n\n# Windows Virtualization Conflict Triage\n\n## Overview\n\nDiagnose virtualization conflicts from the host outward. Verify whether Hyper-V or VBS is active, classify the VMware failure mode, and only then decide between coexistence, import fallback, or host reconfiguration.\n\n## Reference Map\n\n- Read [references\u002Fconflict-map.md](references\u002Fconflict-map.md) to classify the host stack.\n- Read [references\u002Ffallback-matrix.md](references\u002Ffallback-matrix.md) for OVA, raw-disk, and host-change fallback choices.\n\n## Required Discovery\n\n1. Determine whether Hyper-V or VBS is active.\n2. Capture the exact VMware failure mode: import failure, `vmware-vmx` crash, guest-tools issue, or `vmrun` guest-auth issue.\n3. Separate host-level launch failure from guest-level boot failure.\n4. Decide whether an OVA fallback or staged import is sufficient before touching host settings.\n\n## Preferred Flow\n\n1. Read host virtualization status.\n2. Reproduce the VMware failure with logs.\n3. Check whether a different import path avoids the failure.\n4. Treat host setting changes as a deliberate maintenance window, not an inline experiment.\n\n## Stop Rules\n\n- Do not disable Hyper-V or VBS without capturing current host state and rollback steps.\n- Do not treat `vmrun` guest-auth failure as proof that the guest never booted.\n- Do not keep iterating on raw VMX edits when an OVA path is cleaner.\n\n## Common Mistakes\n\n- Mixing host and guest failures into one diagnosis.\n- Forgetting that Docker Desktop and WSL also depend on the host virtualization stack.\n- Assuming an imported VM is invalid when the real problem is host coexistence.\n","# Windows Virtualization Conflict Triage\n\n## Overview\n\nDiagnose virtualization conflicts from the host outward. Verify whether Hyper-V or VBS is active, classify the VMware failure mode, and only then decide between coexistence, import fallback, or host reconfiguration.\n\n## Reference Map\n\n- Read [references\u002Fconflict-map.md](references\u002Fconflict-map.md) to classify the host stack.\n- Read [references\u002Ffallback-matrix.md](references\u002Ffallback-matrix.md) for OVA, raw-disk, and host-change fallback choices.\n\n## Required Discovery\n\n1. Determine whether Hyper-V or VBS is active.\n2. Capture the exact VMware failure mode: import failure, `vmware-vmx` crash, guest-tools issue, or `vmrun` guest-auth issue.\n3. Separate host-level launch failure from guest-level boot failure.\n4. Decide whether an OVA fallback or staged import is sufficient before touching host settings.\n\n## Preferred Flow\n\n1. Read host virtualization status.\n2. Reproduce the VMware failure with logs.\n3. Check whether a different import path avoids the failure.\n4. Treat host setting changes as a deliberate maintenance window, not an inline experiment.\n\n## Stop Rules\n\n- Do not disable Hyper-V or VBS without capturing current host state and rollback steps.\n- Do not treat `vmrun` guest-auth failure as proof that the guest never booted.\n- Do not keep iterating on raw VMX edits when an OVA path is cleaner.\n\n## Common Mistakes\n\n- Mixing host and guest failures into one diagnosis.\n- Forgetting that Docker Desktop and WSL also depend on the host virtualization stack.\n- Assuming an imported VM is invalid when the real problem is host coexistence.\n",{"name":5,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5",".agents\u002Fskills\u002Fwindows-virtualization-conflict-triage","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill windows-virtualization-conflict-triage",{"tool":46,"command":47},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill windows-virtualization-conflict-triage",{"tool":49,"command":50},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill windows-virtualization-conflict-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwindows-virtualization-conflict-triage\u002FSKILL.md",true,[54,60,66,70,74,80,84],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"agents\u002Fopenai.yaml","REFERENCE","参考文档",301,"https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwindows-virtualization-conflict-triage\u002Fagents\u002Fopenai.yaml",{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"LICENSE.txt","LICENSE","许可证",11357,"https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt",{"path":67,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fconflict-map.md",366,"https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwindows-virtualization-conflict-triage\u002Freferences\u002Fconflict-map.md",{"path":71,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Ffallback-matrix.md",274,"https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwindows-virtualization-conflict-triage\u002Freferences\u002Ffallback-matrix.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Fbundle-artifact.sh","SCRIPT","脚本",1517,"https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002Fscripts\u002Fbundle-artifact.sh",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Finit-artifact.sh",9924,"https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002Fscripts\u002Finit-artifact.sh",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fshadcn-components.tar.gz",19967,"https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002Fscripts\u002Fshadcn-components.tar.gz",[89,110,140,167,181,197],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":29},"01M6DF7D7478R55P46REYH4QAC","clarify-requirements","Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fworkspace-hooks\u002Fskills\u002Fclarify-requirements\u002FSKILL.md",[],[96,97,98,99,100,101,102,103,104,26,105,106,107,108,109],"clarify requirements","clarify","requirements","risk","options","task","prompts","goal","scanning","context","repo","injection","execution","file",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":121,"publishedAt":29},"01M6DF79CA4BHJS66J8EZDBPWJ","openmm-md","Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein \u002F protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fmcp\u002Fopenmm-md-mcp\u002Fskill\u002Fopenmm-md\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[122,123,124,125,126,127,128,129,130,131,132,133,134,20,26,135,136,137,138,139],"openmm md","how","decision","pick","linux","analyze","tool","stack","open","NVIDIA","gpu","license","workflow","free","molecular dynamics","local","do","MCP",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":152,"publishedAt":29},"01M6DF76C1MG85VEWP8VZCBNMN","visual-review","Take screenshots of web pages and UI using Playwright for visual review and iteration","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fvisual-review\u002FSKILL.md",[146,149],{"categoryNo":147,"categoryName":148,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":150,"categoryName":151,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000008","测试与质量",[153,154,155,156,157,158,159,160,161,162,123,163,164,165,166],"review","visual","visual review","pages","web","false","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":29},"01M6DF73AQVCBZKEN0YXEX9FXP","status","Diagnostic status report — shows metaswarm installation state, project setup, and potential issues","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstatus\u002FSKILL.md",[],[169,174,175,176,177,178,179,180],"setup","report","project","installation","project setup","issues","state",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":188,"publishedAt":29},"01M6DF6X6C2XB0P6GX76P7TTYV","start","Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstart\u002FSKILL.md",[187],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},[183,189,101,190,191,192,26,193,194,195,196],"start issue","issue","ready","work on issue","user","work","work on","development",{"skillNo":198,"name":174,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":29},"01M6DF6QMJ9AJKFKHHKRT005PQ","Interactive project setup — detects your project, configures metaswarm, writes project-local files","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fsetup\u002FSKILL.md",[],[174,176,137,203,178,204],"files","interactive"]