[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DB4VQC5XS7FFCM322D9CG4":3,"skill-same:01M6DB4VQC5XS7FFCM322D9CG4":80},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":14,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6DB4VQC5XS7FFCM322D9CG4","claude-prompt-forge",null,"Prompt-forging skill for Claude Code and long autonomous Claude sessions — the prompt analogue of grill-me-extensive. Builds orchestration, session, unit, and handoff prompts with resume-don't-restart preambles, both-states evidence contracts, AND-gate completion, hard safety bans, and unit sentinels so work survives compaction and resists false greens. Use when writing or hardening a multi-phase Claude prompt, when a prior prompt caused restarts or false completion, or when the user says forge a prompt, prompt for Claude Code, make this prompt robust, orchestration prompt, session prompt, or handoff prompt.","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\u002Fclaude-prompt-forge\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"claude prompt forge","forge","prompt","session","false","me","grill","gate","resume","grill-me","evidence","use","writing","autonomous","work","Safety","hardening","code","sessions","orchestration","2026-11-10 10:12:30",false,"---\nname: \"claude-prompt-forge\"\ndescription: \"Prompt-forging skill for Claude Code and long autonomous Claude sessions — the prompt analogue of grill-me-extensive. Builds orchestration, session, unit, and handoff prompts with resume-don't-restart preambles, both-states evidence contracts, AND-gate completion, hard safety bans, and unit sentinels so work survives compaction and resists false greens. Use when writing or hardening a multi-phase Claude prompt, when a prior prompt caused restarts or false completion, or when the user says forge a prompt, prompt for Claude Code, make this prompt robust, orchestration prompt, session prompt, or handoff prompt.\"\n---\n\nForge prompts that drive Claude (especially Claude Code) through multi-phase autonomous work without restarting completed gates, trusting uncontrolled zeros, or claiming success from partial evidence.\n\nThis skill is the prompt analogue of `grill-me-extensive`. Where grill-me-extensive scopes a program by walking decisions, this skill produces the **instrument** that executes a decided program. Read `references\u002Fprompt-anatomy.md` for the full anatomy, `references\u002Ffailure-patterns.md` for the measured failure modes each rule prevents, and `references\u002Fdiscovery-surface.md` when forging prompts that discover tools, MCPs, skills, or capacity upgrades (multi-registry + maturity flags + concrete borrow lines).\n\n## When to use\n\n- Writing or hardening an orchestration \u002F session \u002F unit prompt for Claude Code\n- Turning a decision log or backlog into a paste-ready Claude prompt\n- Fixing a prompt that caused restart-of-completed-work, false greens, or fragment overwrites\n- Producing prompts for fan-out units, harvest units, or review units\n\nDo **not** use for ordinary one-shot questions, casual chat, or prompts that do not need durability across context loss.\n\n## The 8-section method\n\nProduce prompts in this order. Omit a section only when it is genuinely inapplicable — never because it is long.\n\n### 1. ROLE AND DELIVERABLE (who + what only)\n\nState who Claude is in this turn and the single deliverable class. Ban pretence of access Claude does not have.\n\n```\nYou are the [architect | implementer | reviewer | miner] for [program].\nYou produce [design + executable prompts | code + receipts | ranked shortlist].\nYou do NOT [claim measurements you did not run | re-derive banked facts | re-open settled decisions].\n```\n\n### 2. RESUME-DON'T-RESTART PREAMBLE\n\nName every completed gate, measurement, and artifact that must **not** be redone. Restarting completed work is the single most expensive failure mode in long programs.\n\n```\nDO NOT redo: [294-option selection, Gate 1, Wave-1 merges, measured envelope X].\nTreat these as given. If your plan requires re-deriving them, your plan is wrong unless you produce a NEW measurement that supersedes them.\n```\n\n### 3. GROUND TRUTH (measured, banked)\n\nList facts that were measured on the estate. Tag confidence. Forbid re-derivation.\n\n- Numbers, paths, run IDs, policy IDs, commit SHAs\n- Working envelopes (concurrency, stagger, node type)\n- Verified absences (with the detector that proved absence)\n\n### 4. BINDING DECISIONS (settled, do not re-litigate)\n\nOwner-directed or grill-converged decisions. Re-opening them without new evidence is a defect.\n\n### 5. HARD SAFETY BOUNDARIES (prohibitions)\n\nState as bans, not preferences:\n\n- Paths \u002F branches \u002F peers never to touch\n- Commands never to run (`sync-from-live`, force-push, `--no-verify`, credential rotation without owner)\n- Data classes that stay local\n- Fragment-overwrite ban (see failure patterns)\n\n### 6. EVIDENCE AND COMPLETION CONTRACT\n\nMandate the proof standard. Every completion claim needs:\n\n| requirement | meaning |\n|---|---|\n| **Both-states** | Detector fires on known-broken AND is silent on known-good. Silent in both states measures nothing. |\n| **AND-gate** | Exit 0 AND artifact exists AND size ≥ floor AND schema\u002Fsentinel validates AND no forbidden path changed. Exit alone is SEVERED, not SUCCESS. |\n| **Mutation** | Reintroduce a representative defect in an isolated fixture; suite goes red; revert. |\n| **Freshness** | Cached green carries a timestamp; stale green is UNKNOWN. |\n| **Agent self-report** | A lead, never evidence. |\n\nRequire named artifacts, atomic writes, and a `RESUME.json` (or equivalent) at every wave boundary so the program survives compaction.\n\n### 7. PHASED WORK (numbered, ordered, gated)\n\nBreak work into phases with explicit entry\u002Fexit criteria. Put gates **before** the work they protect (e.g. monitor ships before fan-out beyond smoke). Prefer:\n\n**ADOPT → EXTEND → WIRE → CONSOLIDATE → PROVE → BUILD**\n\nMechanical questions go to code; agents get judgment only.\n\nWhen the program is about discovering tools, MCPs, skills, or capacity upgrades, include a **discovery-surface** phase (or required lens set) per `references\u002Fdiscovery-surface.md`: GitHub-native structural search + parallel registries (package, MCP dirs, HF, early-signal social, vendor changelogs), maturity flags, concrete borrow lines, and inventory dedup. Do not forge a discovery program that only does keyword GitHub search.\n\n### 8. OUTPUT \u002F UNIT CONTRACT\n\nFor every unit that writes an artifact:\n\n1. Write the full analysis to an **exact path**.\n2. End with a line that is exactly `UNIT-COMPLETE: {id}` (or the program's sentinel).\n3. If blocked, still write a partial file + sentinel + `BLOCKER` section — never invent contents.\n4. Aim under a stated tool-call budget; write the one artifact once.\n\nCalibrated confidence on claims: almost-certain (90–99%) · very likely (80–90%) · likely (55–80%) · roughly even (45–55%) · unlikely · very unlikely. Write `UNVERIFIED` **inline** next to the claim, with the settling experiment named.\n\n## Question policy (encode in the prompt)\n\n- At most **one** consolidated decision packet per session segment.\n- Ask only when the answer cannot be derived mechanically, changes architecture\u002Fcapability\u002Fsecurity\u002Firreversibility, and has genuinely non-equivalent options.\n- No per-turn micro-questions. No permission theater for recommend-and-proceed work.\n- Foundation-first: the 1–2 framing questions that reframe downstream work come before detail questions.\n\n## Anti-patterns to ban inside the forged prompt\n\n| anti-pattern | rule |\n|---|---|\n| Fragment trap | Never copy a generated MODIFY excerpt over a live file. Require complete files, exact patches with preimage hashes, or structural edits on anchors that occur exactly once. |\n| Use-vs-mention | \"Does this string appear\" ≠ \"does this key exist in the parsed object\". Ask the structure. |\n| Doneness vs completeness | Writer finished ≠ work finished ≠ run reached terminal state. Require the run's own terminal state. |\n| Timeout believed but null | Re-read the submitted run object; assert timeout non-null. |\n| Agents for mechanical work | Classification, diff, census → code. Agents for judgment only. |\n| Uncontrolled zero | Validate every detector against known-present and known-broken before trusting absence. |\n| Restart completed gates | Name them in the preamble; treat re-derivation as a defect. |\n| GitHub-only discovery | When the program discovers tools\u002FMCPs\u002Fskills\u002Fcapacity, require the multi-registry discovery surface (see `references\u002Fdiscovery-surface.md`). |\n| Star \u002F download tourism | Candidate ranking needs maintenance signal, license, tests\u002Fexamples, and a concrete borrow line — popularity is weak signal only. |\n| Silent WIP promotion | Pre-1.0 \u002F RFC \u002F changelog-only items must carry an explicit maturity flag; they cannot enter production TIER-0 without owner risk acceptance. |\n| Re-propose existing skills | Cross-ref Phase 0 inventory and live skills; duplicates merge or skip, never reappear as top-gems. |\n\n## Modes (state which you are forging)\n\n- **orchestration** — multi-phase program prompt for a full Claude Code session\n- **unit** — single fan-out \u002F mine \u002F review unit with strict output contract\n- **handoff** — bridge prompt that reconstructs state for a new session without restart\n- **hardening** — take an existing weak prompt and rewrite it to this standard\n- **substrate** — design + executable prompts for infrastructure (monitors, governors, loops)\n\nDefaults: \"write the next Claude prompt\" → orchestration. \"prompt for each worker\" → unit. \"resume this program\" → handoff. \"this prompt failed \u002F caused rework\" → hardening.\n\n## Process\n\n1. **Scout** the decision log, state-of-the-world, backlog, and prior prompts. Prefer measured numbers over narrative.\n2. **Bank** ground truth and binding decisions into sections 3–4.\n3. **Encode** safety bans and evidence contract before phases.\n4. **Order** phases with gates first; prefer adopt\u002Fextend\u002Fwire over build. If discovery is in scope, include the multi-registry discovery surface from `references\u002Fdiscovery-surface.md`.\n5. **Write** the prompt long and specific — working program prompts run to thousands of words with numbered phases. Brevity that omits a contract is a defect.\n6. **Self-check** against `references\u002Ffailure-patterns.md` and, when discovery is in scope, `references\u002Fdiscovery-surface.md` before delivery.\n7. Optionally deliver a ≤200-word note of what changed vs the previous prompt and why.\n\n## Deliverable shape\n\n```markdown\n# PROMPT — [name]\n\n**Target:** Claude Code | Claude | …\n**Attach:** [files]\n**Mode:** orchestration | unit | handoff | …\n\n## 0. Who you are and what you produce\n## 1. Resume-don't-restart\n## 2. Ground truth (measured)\n## 3. Binding decisions\n## 4. Hard safety boundaries\n## 5. Evidence and completion contract\n## 6. Phased work\n## 7. Output \u002F unit contract\n## 8. Question policy\n```\n\nA forged prompt is not a summary of the problem. It is the instrument that makes the next session correct by default.\n\nStub template: `assets\u002Forchestration-prompt-stub.md`.","Forge prompts that drive Claude (especially Claude Code) through multi-phase autonomous work without restarting completed gates, trusting uncontrolled zeros, or claiming success from partial evidence.\n\nThis skill is the prompt analogue of `grill-me-extensive`. Where grill-me-extensive scopes a program by walking decisions, this skill produces the **instrument** that executes a decided program. Read `references\u002Fprompt-anatomy.md` for the full anatomy, `references\u002Ffailure-patterns.md` for the measured failure modes each rule prevents, and `references\u002Fdiscovery-surface.md` when forging prompts that discover tools, MCPs, skills, or capacity upgrades (multi-registry + maturity flags + concrete borrow lines).\n\n## When to use\n\n- Writing or hardening an orchestration \u002F session \u002F unit prompt for Claude Code\n- Turning a decision log or backlog into a paste-ready Claude prompt\n- Fixing a prompt that caused restart-of-completed-work, false greens, or fragment overwrites\n- Producing prompts for fan-out units, harvest units, or review units\n\nDo **not** use for ordinary one-shot questions, casual chat, or prompts that do not need durability across context loss.\n\n## The 8-section method\n\nProduce prompts in this order. Omit a section only when it is genuinely inapplicable — never because it is long.\n\n### 1. ROLE AND DELIVERABLE (who + what only)\n\nState who Claude is in this turn and the single deliverable class. Ban pretence of access Claude does not have.\n\n```\nYou are the [architect | implementer | reviewer | miner] for [program].\nYou produce [design + executable prompts | code + receipts | ranked shortlist].\nYou do NOT [claim measurements you did not run | re-derive banked facts | re-open settled decisions].\n```\n\n### 2. RESUME-DON'T-RESTART PREAMBLE\n\nName every completed gate, measurement, and artifact that must **not** be redone. Restarting completed work is the single most expensive failure mode in long programs.\n\n```\nDO NOT redo: [294-option selection, Gate 1, Wave-1 merges, measured envelope X].\nTreat these as given. If your plan requires re-deriving them, your plan is wrong unless you produce a NEW measurement that supersedes them.\n```\n\n### 3. GROUND TRUTH (measured, banked)\n\nList facts that were measured on the estate. Tag confidence. Forbid re-derivation.\n\n- Numbers, paths, run IDs, policy IDs, commit SHAs\n- Working envelopes (concurrency, stagger, node type)\n- Verified absences (with the detector that proved absence)\n\n### 4. BINDING DECISIONS (settled, do not re-litigate)\n\nOwner-directed or grill-converged decisions. Re-opening them without new evidence is a defect.\n\n### 5. HARD SAFETY BOUNDARIES (prohibitions)\n\nState as bans, not preferences:\n\n- Paths \u002F branches \u002F peers never to touch\n- Commands never to run (`sync-from-live`, force-push, `--no-verify`, credential rotation without owner)\n- Data classes that stay local\n- Fragment-overwrite ban (see failure patterns)\n\n### 6. EVIDENCE AND COMPLETION CONTRACT\n\nMandate the proof standard. Every completion claim needs:\n\n| requirement | meaning |\n|---|---|\n| **Both-states** | Detector fires on known-broken AND is silent on known-good. Silent in both states measures nothing. |\n| **AND-gate** | Exit 0 AND artifact exists AND size ≥ floor AND schema\u002Fsentinel validates AND no forbidden path changed. Exit alone is SEVERED, not SUCCESS. |\n| **Mutation** | Reintroduce a representative defect in an isolated fixture; suite goes red; revert. |\n| **Freshness** | Cached green carries a timestamp; stale green is UNKNOWN. |\n| **Agent self-report** | A lead, never evidence. |\n\nRequire named artifacts, atomic writes, and a `RESUME.json` (or equivalent) at every wave boundary so the program survives compaction.\n\n### 7. PHASED WORK (numbered, ordered, gated)\n\nBreak work into phases with explicit entry\u002Fexit criteria. Put gates **before** the work they protect (e.g. monitor ships before fan-out beyond smoke). Prefer:\n\n**ADOPT → EXTEND → WIRE → CONSOLIDATE → PROVE → BUILD**\n\nMechanical questions go to code; agents get judgment only.\n\nWhen the program is about discovering tools, MCPs, skills, or capacity upgrades, include a **discovery-surface** phase (or required lens set) per `references\u002Fdiscovery-surface.md`: GitHub-native structural search + parallel registries (package, MCP dirs, HF, early-signal social, vendor changelogs), maturity flags, concrete borrow lines, and inventory dedup. Do not forge a discovery program that only does keyword GitHub search.\n\n### 8. OUTPUT \u002F UNIT CONTRACT\n\nFor every unit that writes an artifact:\n\n1. Write the full analysis to an **exact path**.\n2. End with a line that is exactly `UNIT-COMPLETE: {id}` (or the program's sentinel).\n3. If blocked, still write a partial file + sentinel + `BLOCKER` section — never invent contents.\n4. Aim under a stated tool-call budget; write the one artifact once.\n\nCalibrated confidence on claims: almost-certain (90–99%) · very likely (80–90%) · likely (55–80%) · roughly even (45–55%) · unlikely · very unlikely. Write `UNVERIFIED` **inline** next to the claim, with the settling experiment named.\n\n## Question policy (encode in the prompt)\n\n- At most **one** consolidated decision packet per session segment.\n- Ask only when the answer cannot be derived mechanically, changes architecture\u002Fcapability\u002Fsecurity\u002Firreversibility, and has genuinely non-equivalent options.\n- No per-turn micro-questions. No permission theater for recommend-and-proceed work.\n- Foundation-first: the 1–2 framing questions that reframe downstream work come before detail questions.\n\n## Anti-patterns to ban inside the forged prompt\n\n| anti-pattern | rule |\n|---|---|\n| Fragment trap | Never copy a generated MODIFY excerpt over a live file. Require complete files, exact patches with preimage hashes, or structural edits on anchors that occur exactly once. |\n| Use-vs-mention | \"Does this string appear\" ≠ \"does this key exist in the parsed object\". Ask the structure. |\n| Doneness vs completeness | Writer finished ≠ work finished ≠ run reached terminal state. Require the run's own terminal state. |\n| Timeout believed but null | Re-read the submitted run object; assert timeout non-null. |\n| Agents for mechanical work | Classification, diff, census → code. Agents for judgment only. |\n| Uncontrolled zero | Validate every detector against known-present and known-broken before trusting absence. |\n| Restart completed gates | Name them in the preamble; treat re-derivation as a defect. |\n| GitHub-only discovery | When the program discovers tools\u002FMCPs\u002Fskills\u002Fcapacity, require the multi-registry discovery surface (see `references\u002Fdiscovery-surface.md`). |\n| Star \u002F download tourism | Candidate ranking needs maintenance signal, license, tests\u002Fexamples, and a concrete borrow line — popularity is weak signal only. |\n| Silent WIP promotion | Pre-1.0 \u002F RFC \u002F changelog-only items must carry an explicit maturity flag; they cannot enter production TIER-0 without owner risk acceptance. |\n| Re-propose existing skills | Cross-ref Phase 0 inventory and live skills; duplicates merge or skip, never reappear as top-gems. |\n\n## Modes (state which you are forging)\n\n- **orchestration** — multi-phase program prompt for a full Claude Code session\n- **unit** — single fan-out \u002F mine \u002F review unit with strict output contract\n- **handoff** — bridge prompt that reconstructs state for a new session without restart\n- **hardening** — take an existing weak prompt and rewrite it to this standard\n- **substrate** — design + executable prompts for infrastructure (monitors, governors, loops)\n\nDefaults: \"write the next Claude prompt\" → orchestration. \"prompt for each worker\" → unit. \"resume this program\" → handoff. \"this prompt failed \u002F caused rework\" → hardening.\n\n## Process\n\n1. **Scout** the decision log, state-of-the-world, backlog, and prior prompts. Prefer measured numbers over narrative.\n2. **Bank** ground truth and binding decisions into sections 3–4.\n3. **Encode** safety bans and evidence contract before phases.\n4. **Order** phases with gates first; prefer adopt\u002Fextend\u002Fwire over build. If discovery is in scope, include the multi-registry discovery surface from `references\u002Fdiscovery-surface.md`.\n5. **Write** the prompt long and specific — working program prompts run to thousands of words with numbered phases. Brevity that omits a contract is a defect.\n6. **Self-check** against `references\u002Ffailure-patterns.md` and, when discovery is in scope, `references\u002Fdiscovery-surface.md` before delivery.\n7. Optionally deliver a ≤200-word note of what changed vs the previous prompt and why.\n\n## Deliverable shape\n\n```markdown\n# PROMPT — [name]\n\n**Target:** Claude Code | Claude | …\n**Attach:** [files]\n**Mode:** orchestration | unit | handoff | …\n\n## 0. Who you are and what you produce\n## 1. Resume-don't-restart\n## 2. Ground truth (measured)\n## 3. Binding decisions\n## 4. Hard safety boundaries\n## 5. Evidence and completion contract\n## 6. Phased work\n## 7. Output \u002F unit contract\n## 8. Question policy\n```\n\nA forged prompt is not a summary of the problem. It is the instrument that makes the next session correct by default.\n\nStub template: `assets\u002Forchestration-prompt-stub.md`.",{"name":5,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5",".agents\u002Fskills\u002Fclaude-prompt-forge","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill claude-prompt-forge",{"tool":66,"command":67},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill claude-prompt-forge",{"tool":69,"command":70},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill claude-prompt-forge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclaude-prompt-forge\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"resources\u002Fimplementation-playbook.md","REFERENCE","参考文档",17070,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002FCopia de auth-implementation-patterns\u002Fresources\u002Fimplementation-playbook.md",[81,102,129,155,169,184],{"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":87,"publishedAt":49},"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",[],[88,89,90,91,92,93,94,95,96,40,97,98,99,100,101],"clarify requirements","clarify","requirements","risk","options","task","prompts","goal","scanning","context","repo","injection","execution","file",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":109,"publishedAt":49},"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",[108],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[110,111,112,113,114,115,116,117,118,119,120,121,122,123,40,124,125,126,127,128],"openmm md","how","decision","pick","linux","analyze","tool","stack","open","NVIDIA","gpu","license","workflow","windows","free","molecular dynamics","local","do","MCP",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":141,"publishedAt":49},"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",[135,138],{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[142,143,144,145,146,33,147,148,149,150,111,151,152,153,154],"review","visual","visual review","pages","web","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":49},"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",[],[157,162,163,164,165,166,167,168],"setup","report","project","installation","project setup","issues","state",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":49},"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",[175],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[171,177,93,178,179,180,40,181,43,182,183],"start issue","issue","ready","work on issue","user","work on","development",{"skillNo":185,"name":162,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":49},"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",[],[162,164,126,190,166,191],"files","interactive"]