[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DBB941EZ55BMZC7PVMVWC2":3,"skill-same:01M6DBB941EZ55BMZC7PVMVWC2":59},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M6DBB941EZ55BMZC7PVMVWC2","dr-plan",null,"Use when someone asks to \"create a DR plan\", \"disaster recovery\", \"business continuity\", or \"RTO RPO\" — generates a product\u002Fservice-scoped Disaster Recovery plan with numeric RTO\u002FRPO targets, ranked disaster scenarios, recovery procedures, manual workarounds, and a testing schedule. Not for step-by-step restoration runbooks.","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\u002Fdr-plan\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"plan","dr plan","testing","recovery plan","create","product","recovery","rto","rpo","schedule","business","use","continuity","disaster recovery","service","2026-11-10 10:12:30",false,"---\nname: dr-plan\ndescription: Use when someone asks to \"create a DR plan\", \"disaster recovery\", \"business continuity\", or \"RTO RPO\" — generates a product\u002Fservice-scoped Disaster Recovery plan with numeric RTO\u002FRPO targets, ranked disaster scenarios, recovery procedures, manual workarounds, and a testing schedule. Not for step-by-step restoration runbooks.\n---\n\n\u003C!-- Source: cherry-picked from https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco (skills\u002Fdr-plan, \"pmstudio-dr\") on 27.08.2026 per grill decision G-11\u002F11B. De-branded and generalized; coco pmstudio document ecosystem and reference files not ported. -->\n\n# DR Plan — Disaster Recovery Plan\n\n## Purpose\n\nGenerates a Disaster Recovery plan scoped to a specific product or service. For SaaS products (where the vendor owns infrastructure), the plan focuses on what YOUR organization controls: data exports, integration failover, access recovery, communication, and business continuity — not rebuilding the vendor's infrastructure.\n\n## Process\n\n### Step 1: Read Context\n\nRead whatever project context exists: architecture notes, PRDs\u002Fspecs, system diagrams, data flows, vendor\u002Fintegration documentation, and any existing incident response plan (reference it for the communication section).\n\n### Step 2: Determine Product Type\n\n| Type | DR Focus |\n|------|----------|\n| **SaaS (you are the customer)** | Vendor dependency, data portability, alternative workflows |\n| **Self-hosted** | Infrastructure recovery, backup\u002Frestore, failover |\n| **Hybrid** | Both vendor and self-hosted components |\n\nAdjust scope accordingly. For SaaS, skip infrastructure sections (the vendor's problem); add vendor SLA and data portability sections.\n\n### Step 3: Ask Discovery Questions\n\nOnly ask what can't be inferred:\n\n1. **Business criticality tier?** (Tier 1 critical \u002F Tier 2 important \u002F Tier 3 standard)\n2. **Maximum tolerable downtime?** (becomes RTO)\n3. **Maximum tolerable data loss?** (becomes RPO)\n4. **Manual workarounds if the product is down?** (e.g., \"we can use Excel for 48 hours\")\n5. **Vendor SLA?** (uptime commitment, support response times, data export capabilities)\n6. **Backup strategy?** (What exports where? How often?)\n\n### Step 4: Generate DR Plan\n\n**Output:** `DR-Plan-{ProductName}-{Date}` as a self-contained HTML or Markdown document with clean typography (print-friendly if HTML).\n\n**11 sections:**\n\n1. **Purpose & Scope** — product, instances covered, what the plan does\u002Fdoesn't cover, relationship to the vendor's own DR plan.\n2. **Service Classification** — criticality tier with justification; data classification; regulatory\u002Fcompliance requirements; business impact of downtime (per hour\u002Fday).\n3. **RTO\u002FRPO Targets** — per-component table: Component | RTO | RPO | Justification (e.g. core platform 4h\u002F24h per vendor SLA; SSO 1h\u002FN\u002FA because users are locked out).\n4. **Disaster Scenarios** — ranked by likelihood × impact: vendor platform outage (most likely), data corruption, access loss (SSO\u002Flicense\u002Fpermissions), integration failure, security breach, vendor business failure. For each: description, likelihood, impact, detection method.\n5. **Recovery Procedures** — per-scenario: trigger condition (how you know it's happening), immediate actions (first 15 minutes), short-term recovery (first 4 hours), full recovery (to meet RTO), verification checklist.\n6. **Communication Plan** — who to notify per scenario and severity; templates; vendor communication (support ticket + account manager); stakeholder update cadence during outage.\n7. **Dependencies** — external systems required for recovery; vendor contacts and escalation; SLA commitments and how to invoke them; third-party services (SSO provider, email, etc.).\n8. **Data Backup & Restoration** — what is backed up (by vendor, by you); frequency and retention; storage location; step-by-step restoration procedure; data validation after restore.\n9. **Manual Workarounds** — which business processes continue without the product; fallback procedures (Excel\u002FSharePoint\u002Fpaper); how long the workaround is sustainable; data reconciliation procedure when the product is restored.\n10. **Testing Schedule** — DR test cadence (annually minimum, semi-annually recommended); test scenarios (tabletop, partial recovery, full recovery); last test date and results; next scheduled test; success criteria.\n11. **Review & Maintenance** — review cadence (semi-annually or after any DR event); approval chain; version history; distribution list.\n\n### Step 5: Present for Review\n\nShow the plan outline with key decisions highlighted (RTO\u002FRPO targets, scenario prioritization, manual workaround availability) and ask for approval before writing the full document.\n\n## Critical Rules\n\n1. **RTO\u002FRPO must be numbers, not words.** \"As fast as possible\" is not an RTO. Push for specific hours.\n2. **Vendor DR is not your DR.** The vendor's uptime SLA is an input to your plan, not a substitute for it. Your plan covers what happens on your side.\n3. **Manual workarounds are critical.** For every scenario, document what the business does while the product is down. No workaround = a risk to flag.\n4. **Data portability is DR.** If you can't get data out of the product, you can't recover from vendor failure. Document export capabilities.\n5. **Test the plan.** A plan that's never been tested is a wish list. Include a testing schedule and success criteria.\n","\u003C!-- Source: cherry-picked from https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco (skills\u002Fdr-plan, \"pmstudio-dr\") on 27.08.2026 per grill decision G-11\u002F11B. De-branded and generalized; coco pmstudio document ecosystem and reference files not ported. -->\n\n# DR Plan — Disaster Recovery Plan\n\n## Purpose\n\nGenerates a Disaster Recovery plan scoped to a specific product or service. For SaaS products (where the vendor owns infrastructure), the plan focuses on what YOUR organization controls: data exports, integration failover, access recovery, communication, and business continuity — not rebuilding the vendor's infrastructure.\n\n## Process\n\n### Step 1: Read Context\n\nRead whatever project context exists: architecture notes, PRDs\u002Fspecs, system diagrams, data flows, vendor\u002Fintegration documentation, and any existing incident response plan (reference it for the communication section).\n\n### Step 2: Determine Product Type\n\n| Type | DR Focus |\n|------|----------|\n| **SaaS (you are the customer)** | Vendor dependency, data portability, alternative workflows |\n| **Self-hosted** | Infrastructure recovery, backup\u002Frestore, failover |\n| **Hybrid** | Both vendor and self-hosted components |\n\nAdjust scope accordingly. For SaaS, skip infrastructure sections (the vendor's problem); add vendor SLA and data portability sections.\n\n### Step 3: Ask Discovery Questions\n\nOnly ask what can't be inferred:\n\n1. **Business criticality tier?** (Tier 1 critical \u002F Tier 2 important \u002F Tier 3 standard)\n2. **Maximum tolerable downtime?** (becomes RTO)\n3. **Maximum tolerable data loss?** (becomes RPO)\n4. **Manual workarounds if the product is down?** (e.g., \"we can use Excel for 48 hours\")\n5. **Vendor SLA?** (uptime commitment, support response times, data export capabilities)\n6. **Backup strategy?** (What exports where? How often?)\n\n### Step 4: Generate DR Plan\n\n**Output:** `DR-Plan-{ProductName}-{Date}` as a self-contained HTML or Markdown document with clean typography (print-friendly if HTML).\n\n**11 sections:**\n\n1. **Purpose & Scope** — product, instances covered, what the plan does\u002Fdoesn't cover, relationship to the vendor's own DR plan.\n2. **Service Classification** — criticality tier with justification; data classification; regulatory\u002Fcompliance requirements; business impact of downtime (per hour\u002Fday).\n3. **RTO\u002FRPO Targets** — per-component table: Component | RTO | RPO | Justification (e.g. core platform 4h\u002F24h per vendor SLA; SSO 1h\u002FN\u002FA because users are locked out).\n4. **Disaster Scenarios** — ranked by likelihood × impact: vendor platform outage (most likely), data corruption, access loss (SSO\u002Flicense\u002Fpermissions), integration failure, security breach, vendor business failure. For each: description, likelihood, impact, detection method.\n5. **Recovery Procedures** — per-scenario: trigger condition (how you know it's happening), immediate actions (first 15 minutes), short-term recovery (first 4 hours), full recovery (to meet RTO), verification checklist.\n6. **Communication Plan** — who to notify per scenario and severity; templates; vendor communication (support ticket + account manager); stakeholder update cadence during outage.\n7. **Dependencies** — external systems required for recovery; vendor contacts and escalation; SLA commitments and how to invoke them; third-party services (SSO provider, email, etc.).\n8. **Data Backup & Restoration** — what is backed up (by vendor, by you); frequency and retention; storage location; step-by-step restoration procedure; data validation after restore.\n9. **Manual Workarounds** — which business processes continue without the product; fallback procedures (Excel\u002FSharePoint\u002Fpaper); how long the workaround is sustainable; data reconciliation procedure when the product is restored.\n10. **Testing Schedule** — DR test cadence (annually minimum, semi-annually recommended); test scenarios (tabletop, partial recovery, full recovery); last test date and results; next scheduled test; success criteria.\n11. **Review & Maintenance** — review cadence (semi-annually or after any DR event); approval chain; version history; distribution list.\n\n### Step 5: Present for Review\n\nShow the plan outline with key decisions highlighted (RTO\u002FRPO targets, scenario prioritization, manual workaround availability) and ask for approval before writing the full document.\n\n## Critical Rules\n\n1. **RTO\u002FRPO must be numbers, not words.** \"As fast as possible\" is not an RTO. Push for specific hours.\n2. **Vendor DR is not your DR.** The vendor's uptime SLA is an input to your plan, not a substitute for it. Your plan covers what happens on your side.\n3. **Manual workarounds are critical.** For every scenario, document what the business does while the product is down. No workaround = a risk to flag.\n4. **Data portability is DR.** If you can't get data out of the product, you can't recover from vendor failure. Document export capabilities.\n5. **Test the plan.** A plan that's never been tested is a wish list. Include a testing schedule and success criteria.\n",{"name":5,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5",".agents\u002Fskills\u002Fdr-plan","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill dr-plan",{"tool":51,"command":52},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill dr-plan",{"tool":54,"command":55},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill dr-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdr-plan\u002FSKILL.md",true,[],[60,81,112,139,153,169],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":34},"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",[],[67,68,69,70,71,72,73,74,75,30,76,77,78,79,80],"clarify requirements","clarify","requirements","risk","options","task","prompts","goal","scanning","context","repo","injection","execution","file",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":34},"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",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[93,94,95,96,97,98,99,100,101,102,103,104,105,106,30,107,108,109,110,111],"openmm md","how","decision","pick","linux","analyze","tool","stack","open","NVIDIA","gpu","license","workflow","windows","free","molecular dynamics","local","do","MCP",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":124,"publishedAt":34},"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",[118,121],{"categoryNo":119,"categoryName":120,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":122,"categoryName":123,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000008","测试与质量",[125,126,127,128,129,130,131,132,133,134,94,135,136,137,138],"review","visual","visual review","pages","web","false","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":34},"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",[],[141,146,147,148,149,150,151,152],"setup","report","project","installation","project setup","issues","state",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":34},"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",[159],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},[155,161,72,162,163,164,30,165,166,167,168],"start issue","issue","ready","work on issue","user","work","work on","development",{"skillNo":170,"name":146,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":34},"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",[],[146,148,109,175,150,176],"files","interactive"]