[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C6F11AF22B54CAVMP10CF4":3,"skill-same:01M7C6F11AF22B54CAVMP10CF4":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7C6F11AF22B54CAVMP10CF4","Sum Factory",null,"Start or run a factory from a markdown settings file. Use when the user asks to start a factory, run one, or say where a factory lives.","douglasjarquin\u002Fsum","douglasjarquin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8209?v=4","01M7C6DQ5Z97NVESG77SPX0RPQ","Douglas Jarquin","01M7C6DQ6F4ZNGTGYG17MP16TH",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdouglasjarquin\u002Fsum\u002Fblob\u002Fmain\u002Fsum\u002Fskills\u002Ffactory\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Sum Factory\ndescription: Start or run a factory from a markdown settings file. Use when the user asks to start a factory, run one, or say where a factory lives.\n---\n\n# Factory\n\n## When to use it\n\nThe user asked to start a factory, run a factory, or tell you where one lives.\nSoftware and copy use this same skill.\nThe difference is a markdown settings file.\n\n## Required inputs and access\n\nThe Factory settings in the Sum clone at `skills\u002Fsum-factory\u002Ffactories\u002F\u003Cname>.md`.\nA confirmed copy, when one exists, at `\u002Fworkspace\u002Fsum\u002Ffactories\u002F\u003Cname>.md`.\nNotion, when the floor is a Notion page.\nSpiral, when the confirmed settings say to call it.\nThe Sum Dispatch and Sum Persist skills, once a run is actually approved.\n\n## Sequence of work\n\nAsk one question at a time. Save the answer under `\u002Fworkspace\u002Fsum\u002Ffactories\u002F` before you ask the next. Recommend from a file or a page you read. Do not invent lanes or tools.\n\n1. Name the factory. `copy` and `software` already have recommendation files.\n2. Where does it live? Text files, or a Notion page? If they name a page, fetch it.\n3. What are the lanes, in order? On Notion, read the status options and say the names you saw. Ask them to confirm that order.\n4. Which lanes does a pass pick up, and what should happen there? Ask which lanes are theirs alone.\n\nFor copy, read `skills\u002Fsum-factory\u002Ffactories\u002Fcopy.md` in the clone and offer it as the recommendation. Still ask. If the Notion page shows different lanes, say what you saw and ask which order to keep.\n\nWrite the confirmed answers to `\u002Fworkspace\u002Fsum\u002Ffactories\u002F\u003Cname>.md`. Read the file back.\n\nA run comes after that confirmation, as its own request.\n\n- `runner: software` means follow the software settings file. That lane requires the separately preserved compatible legacy installation pinned in the software settings, including its installed helper; this HC instruction checkout cannot run it. Do not tick it from this chat. Dispatch a worker only when the user asked you to run it there.\n- `runner: directive` means dispatch one worker. The brief is the confirmed settings file plus the piece URL or path they named. The worker does only the pickup lanes, then stops. You do not call Spiral in this chat.\n\nOn a Notion floor, a piece URL is the reliable trigger. Search does not see a status property.\n\n## How to validate the result\n\nThe settings file exists and matches what the user confirmed.\nA start did not call Spiral and did not move a piece.\nA run left the coordinator chat free of the lane work.\nThe worker report names the piece, the command, and the status it set.\n\n## What to return\n\nOn a start: the settings path, the lanes you saw, and the action they confirmed.\nOn a run: the task id, the worker, and the piece or issue it took.\nThen stop.\n\n## What requires approval\n\nStarting a factory, confirming the settings, and each run.\nA recommendation file is not approval.\nA piece sitting in Ready is not approval until they ask for a run.\nDo not post. Do not set Approved. The user merges. The Bot never merges.\n","# Factory\n\n## When to use it\n\nThe user asked to start a factory, run a factory, or tell you where one lives.\nSoftware and copy use this same skill.\nThe difference is a markdown settings file.\n\n## Required inputs and access\n\nThe Factory settings in the Sum clone at `skills\u002Fsum-factory\u002Ffactories\u002F\u003Cname>.md`.\nA confirmed copy, when one exists, at `\u002Fworkspace\u002Fsum\u002Ffactories\u002F\u003Cname>.md`.\nNotion, when the floor is a Notion page.\nSpiral, when the confirmed settings say to call it.\nThe Sum Dispatch and Sum Persist skills, once a run is actually approved.\n\n## Sequence of work\n\nAsk one question at a time. Save the answer under `\u002Fworkspace\u002Fsum\u002Ffactories\u002F` before you ask the next. Recommend from a file or a page you read. Do not invent lanes or tools.\n\n1. Name the factory. `copy` and `software` already have recommendation files.\n2. Where does it live? Text files, or a Notion page? If they name a page, fetch it.\n3. What are the lanes, in order? On Notion, read the status options and say the names you saw. Ask them to confirm that order.\n4. Which lanes does a pass pick up, and what should happen there? Ask which lanes are theirs alone.\n\nFor copy, read `skills\u002Fsum-factory\u002Ffactories\u002Fcopy.md` in the clone and offer it as the recommendation. Still ask. If the Notion page shows different lanes, say what you saw and ask which order to keep.\n\nWrite the confirmed answers to `\u002Fworkspace\u002Fsum\u002Ffactories\u002F\u003Cname>.md`. Read the file back.\n\nA run comes after that confirmation, as its own request.\n\n- `runner: software` means follow the software settings file. That lane requires the separately preserved compatible legacy installation pinned in the software settings, including its installed helper; this HC instruction checkout cannot run it. Do not tick it from this chat. Dispatch a worker only when the user asked you to run it there.\n- `runner: directive` means dispatch one worker. The brief is the confirmed settings file plus the piece URL or path they named. The worker does only the pickup lanes, then stops. You do not call Spiral in this chat.\n\nOn a Notion floor, a piece URL is the reliable trigger. Search does not see a status property.\n\n## How to validate the result\n\nThe settings file exists and matches what the user confirmed.\nA start did not call Spiral and did not move a piece.\nA run left the coordinator chat free of the lane work.\nThe worker report names the piece, the command, and the status it set.\n\n## What to return\n\nOn a start: the settings path, the lanes you saw, and the action they confirmed.\nOn a run: the task id, the worker, and the piece or issue it took.\nThen stop.\n\n## What requires approval\n\nStarting a factory, confirming the settings, and each run.\nA recommendation file is not approval.\nA piece sitting in Ready is not approval until they ask for a run.\nDo not post. Do not set Approved. The user merges. The Bot never merges.\n",{"name":5,"description":7},"main","43dd4d5ee88606cd80c27c01d20b9c60c668cee6","sum\u002Fskills\u002Ffactory","https:\u002F\u002Fgithub.com\u002Fdouglasjarquin\u002Fsum","https:\u002F\u002Fdouglasjarquin.github.io\u002Fsum\u002F","https:\u002F\u002Fgithub.com\u002Fdouglasjarquin","https:\u002F\u002Fwww.douglasjarquin.com\u002F","2026-11-13 11:43:39",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add douglasjarquin\u002Fsum --skill \"Sum Factory\"",{"tool":38,"command":39},"bunx","bunx skills add douglasjarquin\u002Fsum --skill \"Sum Factory\"",{"tool":41,"command":42},"pnpm","pnpm dlx skills add douglasjarquin\u002Fsum --skill \"Sum Factory\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdouglasjarquin\u002Fsum\u002Fblob\u002Fmain\u002Fsum\u002Fskills\u002Ffactory\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7C6GGRMTWCDRD8DVPNA4VA4","verify","Verify a repository through its project-root VERIFY.md contract - run the canonical `mise run verify`, record candidate-bound evidence, and report manual scenarios truthfully. Works in any clone without sum or Herdr.","https:\u002F\u002Fgithub.com\u002Fdouglasjarquin\u002Fsum\u002Fblob\u002Fmain\u002Ftools\u002Fverify\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7C6FZWZRDQRTE63Q2K6X8MR","maintain-verification","Keep a repository's VERIFY.md and feature maps honest when behavior changes - audit stale tasks, paths, links, and coverage claims, find the features a change touches, record a no-map-change rationale for internal changes, and keep authored map edits separate from run results. Works in any clone without sum or Herdr.","https:\u002F\u002Fgithub.com\u002Fdouglasjarquin\u002Fsum\u002Fblob\u002Fmain\u002Ftools\u002Fverify\u002Fskills\u002Fmaintain-verification\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7C6FWFT35JXSWTR1VAESG2W","evidence","Capture truthful before\u002Fafter evidence for one mapped scenario - real screenshots, short screencasts, CLI transcripts, or HTTP responses from the base and the candidate builds - and compare them into one manifest. Works in any clone without sum or Herdr.","https:\u002F\u002Fgithub.com\u002Fdouglasjarquin\u002Fsum\u002Fblob\u002Fmain\u002Ftools\u002Fverify\u002Fskills\u002Fevidence\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7C6FQHE72AQ1TJF4TSGK8DJ","create-verification","Bootstrap or extend a repository's project-local verification - the VERIFY.md contract, a `verify` mise task built from checks the project already declares, a feature-map index with seed feature files, and the vendored verify\u002Fmaintain skills - then prove the generated instructions by running them once. Works in any clone without sum or Herdr.","https:\u002F\u002Fgithub.com\u002Fdouglasjarquin\u002Fsum\u002Fblob\u002Fmain\u002Ftools\u002Fverify\u002Fskills\u002Fcreate-verification\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7C6FM6M6TKQXY7WC73B92GW","Sum Verify","Run a distinct coordinator verification of a worker result. Use when a worker reports a candidate or findings, before treating that report as done.","https:\u002F\u002Fgithub.com\u002Fdouglasjarquin\u002Fsum\u002Fblob\u002Fmain\u002Fsum\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7C6FHBAZMMT02E1CKXVNZNC","Sum Sweep","Put standing sweeps on a dedicated Sweep worker plus routine. Use for inbox digests and similar repeating work, not for the weekday Inbox status.","https:\u002F\u002Fgithub.com\u002Fdouglasjarquin\u002Fsum\u002Fblob\u002Fmain\u002Fsum\u002Fskills\u002Fsweep\u002FSKILL.md",[],[]]