[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DCKH6BW61R9AVPH99P49CG":3,"skill-same:01M6DCKH6BW61R9AVPH99P49CG":75},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6DCKH6BW61R9AVPH99P49CG","forge-discipline",null,"Use when you want to turn a named behavioral pattern (a gem, a fresh arXiv finding, or a matured instinct) into an INSTALLED, self-tested Claude Code hook in one pass. This is a BEHAVIOR forge, not a tool forge - it forges hooks\u002Ftripwires (things the harness runs deterministically), not MCP tools. Given a pattern spec it scaffolds the hook plus any tripwire, state schema, and skill stub it needs, generates and runs a chaos\u002FGameDay self-test that PROVES the hook fires on its trigger, stays silent otherwise, and fails open on garbage, then stages everything in a review queue with the exact one-line install instruction. It NEVER auto-wires settings.json or the dispatcher manifest - the human reviews and applies the one line.","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\u002Fplatform\u002Frouting\u002Ffixtures\u002Fhome\u002F.agents\u002Fskills\u002Fforge-discipline\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"discipline","forge discipline","forge","auto","review","fresh","human","pattern","self","settings.json","hooks","never","dispatcher","MCP","gameday","install","open","tripwire","review queue","code","2026-11-10 10:12:30",false,"---\nname: forge-discipline\ndescription: Use when you want to turn a named behavioral pattern (a gem, a fresh arXiv finding, or a matured instinct) into an INSTALLED, self-tested Claude Code hook in one pass. This is a BEHAVIOR forge, not a tool forge - it forges hooks\u002Ftripwires (things the harness runs deterministically), not MCP tools. Given a pattern spec it scaffolds the hook plus any tripwire, state schema, and skill stub it needs, generates and runs a chaos\u002FGameDay self-test that PROVES the hook fires on its trigger, stays silent otherwise, and fails open on garbage, then stages everything in a review queue with the exact one-line install instruction. It NEVER auto-wires settings.json or the dispatcher manifest - the human reviews and applies the one line.\n---\n\n# Discipline-Forge\n\nThe durable moat is not which cross-domain analogy you borrow today (those deprecate\nthe moment the field mines the same paper). The moat is **owning the pipeline that\nturns any named behavioral pattern into an installed, self-tested discipline in one\npass.** This generalizes the instinct→skill evolution one step further: instead of\nmaturing an observed regularity into an *advisory* skill, it forges an *enforced*\nhook that the harness runs deterministically — and refuses to call it \"installed\"\nuntil a fault-injection self-test proves it actually fires.\n\nThis forges **behaviors** (hooks\u002Ftripwires). A tool-forge forges **tools** (things\nthe model chooses to call). Different artifact, different home: forged behaviors land\nin `~\u002F.claude\u002Fhooks\u002F...` and fold into the dispatcher or `settings.json`.\n\n## SAFETY: review before install (read this first)\n\n`forge.py` **never edits your live `settings.json` or `_dispatch\u002Fmanifest.json`.** A\nforged discipline is staged in a review queue with its passing self-test and a single\nready-to-apply line. **You** read it and apply that line by hand. This mirrors the\nauto-skill-authoring discipline (the forge proposes; the human installs) and means a\nforged hook can never silently start blocking your tools or injecting context.\n\nEvery forged hook also fails open (any error → exit 0; a gate never blocks on error)\nand ships a kill-switch: an env var `FORGE_\u003CNAME>_OFF=1` and a `.disabled` file.\n\n## The pattern spec\n\nA discipline is described by a small spec (CLI flags or a `--spec file.json`):\n\n### The one-pass pipeline (what `forge.py` does)\n### How forged hooks compose with the dispatcher \u002F manifest\n### Where this sits in the instinct → skill path\n### Usage\n### Inject discipline (Stop): surface uncaptured TODO\u002FFIXME markers. Folds as 1 manifest line.\n### Gate discipline (PreToolUse): block git push --force. Installs as a settings.json entry.\n### Inspect without staging:  add --dry-run\n### Full result as JSON:      add --json\n### Trigger kinds\n### Files\n### Quality bar\n","# Discipline-Forge\n\nThe durable moat is not which cross-domain analogy you borrow today (those deprecate\nthe moment the field mines the same paper). The moat is **owning the pipeline that\nturns any named behavioral pattern into an installed, self-tested discipline in one\npass.** This generalizes the instinct→skill evolution one step further: instead of\nmaturing an observed regularity into an *advisory* skill, it forges an *enforced*\nhook that the harness runs deterministically — and refuses to call it \"installed\"\nuntil a fault-injection self-test proves it actually fires.\n\nThis forges **behaviors** (hooks\u002Ftripwires). A tool-forge forges **tools** (things\nthe model chooses to call). Different artifact, different home: forged behaviors land\nin `~\u002F.claude\u002Fhooks\u002F...` and fold into the dispatcher or `settings.json`.\n\n## SAFETY: review before install (read this first)\n\n`forge.py` **never edits your live `settings.json` or `_dispatch\u002Fmanifest.json`.** A\nforged discipline is staged in a review queue with its passing self-test and a single\nready-to-apply line. **You** read it and apply that line by hand. This mirrors the\nauto-skill-authoring discipline (the forge proposes; the human installs) and means a\nforged hook can never silently start blocking your tools or injecting context.\n\nEvery forged hook also fails open (any error → exit 0; a gate never blocks on error)\nand ships a kill-switch: an env var `FORGE_\u003CNAME>_OFF=1` and a `.disabled` file.\n\n## The pattern spec\n\nA discipline is described by a small spec (CLI flags or a `--spec file.json`):\n\n### The one-pass pipeline (what `forge.py` does)\n### How forged hooks compose with the dispatcher \u002F manifest\n### Where this sits in the instinct → skill path\n### Usage\n### Inject discipline (Stop): surface uncaptured TODO\u002FFIXME markers. Folds as 1 manifest line.\n### Gate discipline (PreToolUse): block git push --force. Installs as a settings.json entry.\n### Inspect without staging:  add --dry-run\n### Full result as JSON:      add --json\n### Trigger kinds\n### Files\n### Quality bar\n",{"name":5,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5","platform\u002Frouting\u002Ffixtures\u002Fhome\u002F.agents\u002Fskills\u002Fforge-discipline","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill forge-discipline",{"tool":61,"command":62},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill forge-discipline",{"tool":64,"command":65},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill forge-discipline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Fplatform\u002Frouting\u002Ffixtures\u002Fhome\u002F.agents\u002Fskills\u002Fforge-discipline\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Foriginal-prompt.org","REFERENCE","参考文档",7611,"https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fljg-roundtable\u002Freferences\u002Foriginal-prompt.org",[76,98,123,149,163,179],{"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":44},"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",[],[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"clarify requirements","clarify","requirements","risk","options","task","prompts","goal","scanning","use","context","repo","injection","execution","file",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":105,"publishedAt":44},"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",[104],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[106,107,108,109,110,111,112,113,40,114,115,116,117,118,92,119,120,121,122,37],"openmm md","how","decision","pick","linux","analyze","tool","stack","NVIDIA","gpu","license","workflow","windows","free","molecular dynamics","local","do",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":135,"publishedAt":44},"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",[129,132],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[28,136,137,138,139,140,141,142,143,144,107,145,146,147,148],"visual","visual review","pages","web","false","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":44},"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",[],[151,156,157,158,159,160,161,162],"setup","report","project","installation","project setup","issues","state",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":170,"publishedAt":44},"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",[169],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[165,171,88,172,173,174,92,175,176,177,178],"start issue","issue","ready","work on issue","user","work","work on","development",{"skillNo":180,"name":156,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":44},"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",[],[156,158,121,185,160,186],"files","interactive"]