[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79B3RWG5FXW87SMN462P2RG":3,"skill-same:01M79B3RWG5FXW87SMN462P2RG":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M79B3RWG5FXW87SMN462P2RG","capability-evolve",null,"Changes how an installed aos capability behaves for THIS user and records it in their MOD.md so it survives every upgrade. Use when the user asks to reschedule, retune, retone or otherwise adjust an installed capability (\"make the steward run at 22:00\", a threshold, a preference), when they say a tweak should be for everyone, or when a hand-edited render needs capturing back. Do NOT use to change the shipped source for all users — it classifies that and hands it to capability-contribute — and not to install, upgrade or remove, which are their own skills.","AlmogBaku\u002Faos","AlmogBaku","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F98982?v=4","01M79AYYMZE5E1BEVEP6P829C4","Almog Baku","01M79AYYP0D19RBK33EBYYR3F8",5,"MIT","https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Ffront\u002Fskills\u002Fcapability-evolve\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: capability-evolve\ndescription: Changes how an installed aos capability behaves for THIS user and records\n  it in their MOD.md so it survives every upgrade. Use when the user asks to reschedule,\n  retune, retone or otherwise adjust an installed capability (\"make the steward run\n  at 22:00\", a threshold, a preference), when they say a tweak should be for everyone,\n  or when a hand-edited render needs capturing back. Do NOT use to change the shipped\n  source for all users — it classifies that and hands it to capability-contribute\n  — and not to install, upgrade or remove, which are their own skills.\nmetadata:\n  aos:\n    origin: capability-lifecycle@0.7.0\n---\n# capability-evolve\n\nNot in context yet? Load the `capability-lifecycle` skill first — the map, the\ncontract, the overlay doctrine, and the Experience rules. This is the overlay's\nwrite side — the single front door for every \"change this capability\" ask; the classify\nstep routes what isn't yours. **Default fate of every change: the user's MOD, silently.**\nMOD states current desired state, so every write is an *edit in place*, never an\nappended record (the `capability-lifecycle` skill's `reference\u002Foverlay.md`).\n\n1. Identify the capability and artifacts (`aos-cap show \u003Cid>`); restate the\n   desired change in one line.\n2. **Read the current MOD.md first**, then classify (if the change adds or moves a\n   skill's files, `capability-lifecycle`'s `reference\u002Fnaming.md` binds the names and where\n   references may point — a reference to another skill or agent is written as a slot,\n   `{{skill: \u003Cid>}}`, never as a computed name):\n   - an ONBOARDING question covers it → update that typed answer in the frontmatter;\n   - a prose statement already covers the subject → rewrite that statement (never add a\n     second one that contradicts it — \"office hours: none\" replaces \"office hours\n     Thursday 17:00–18:00\", it does not follow it);\n   - the change restores the shipped default → delete the entry; MOD only states\n     differences;\n   - nothing covers the subject yet → add one imperative statement;\n   - actually an upstream bug or explicitly for *everyone* → the capability-contribute\n     skill owns it: it changes the shipped source (building mode, approval-gated). Say so\n     and hand over — nothing lands in MOD.\n3. Write the MOD.md change **first** (the `capability-lifecycle` skill's\n   `reference\u002Foverlay.md`, Capture and fold —\n   the MOD statement lands before anything depends on it), then apply to the render: seed\n   `\u003Caos_home>\u002Frendered\u002F.staging\u002F\u003Cid>\u002F` with a copy of the live `rendered\u002F\u003Cid>\u002F` (leaving\n   bytecode behind), apply the change there, and gate it like any re-render — the diff of\n   live against staged, then `aos-cap swap \u003Cid>` or `aos-cap discard \u003Cid>` (and any native\n   artifacts per the cheat-sheet — the `capability-lifecycle` skill's\n   `reference\u002Fharness-\u003Charness-runtime>.md`, load it now; native\n   edit verbs where they exist), through the STAGE→GATE→EXECUTE phases.\n4. `aos-cap rehash \u003Cid>` — refresh the recorded hashes in place so `verify`\n   stays clean; the persist hook commits `personal\u002F` (dated message). From now on\n   capability-upgrade re-applies this change on every upgrade. (New artifacts, jobs,\n   or keys → a full `aos-cap record` with the complete set from `aos-cap show`.)\n5. Confirm: \"recorded in your MOD.md — survives every upgrade.\"\n6. Promotion check — **signal-gated, never reflexive** (the judgment, tests,\n   threshold ladder, and etiquette live in the `capability-lifecycle` skill's\n   `reference\u002Foverlay.md`, Promote and retire).\n   An offer fires only on: objectively-broken workaround · forced mechanism override\n   (the change fought the template beyond its `{{mod}}` slots) · the user asked.\n   At most one one-liner offer, at the conversation's end, once per statement ever;\n   a \"no\" is recorded and never re-asked. Yes → hand to capability-contribute\n   with the statement. **Never open a PR or file an issue yourself — every upstream\n   write needs the user's explicit yes (contract).**\n\nCapture mode (drift found by `verify` or by noticing a hand-edit): same steps, but step 3's\n**second half** is skipped — the render already carries the change, so there is nothing to apply.\n**Step 3's MOD.md write still happens, and it is the whole point of capture mode**: the edit\nexists on disk and nowhere in the overlay, so the next upgrade would silently drop it. Skip the\nwrite and step 5's \"recorded in your MOD.md — survives every upgrade\" is a lie\n(the `capability-lifecycle` skill's `reference\u002Foverlay.md`, \"Capture and fold\").\n","# capability-evolve\n\nNot in context yet? Load the `capability-lifecycle` skill first — the map, the\ncontract, the overlay doctrine, and the Experience rules. This is the overlay's\nwrite side — the single front door for every \"change this capability\" ask; the classify\nstep routes what isn't yours. **Default fate of every change: the user's MOD, silently.**\nMOD states current desired state, so every write is an *edit in place*, never an\nappended record (the `capability-lifecycle` skill's `reference\u002Foverlay.md`).\n\n1. Identify the capability and artifacts (`aos-cap show \u003Cid>`); restate the\n   desired change in one line.\n2. **Read the current MOD.md first**, then classify (if the change adds or moves a\n   skill's files, `capability-lifecycle`'s `reference\u002Fnaming.md` binds the names and where\n   references may point — a reference to another skill or agent is written as a slot,\n   `{{skill: \u003Cid>}}`, never as a computed name):\n   - an ONBOARDING question covers it → update that typed answer in the frontmatter;\n   - a prose statement already covers the subject → rewrite that statement (never add a\n     second one that contradicts it — \"office hours: none\" replaces \"office hours\n     Thursday 17:00–18:00\", it does not follow it);\n   - the change restores the shipped default → delete the entry; MOD only states\n     differences;\n   - nothing covers the subject yet → add one imperative statement;\n   - actually an upstream bug or explicitly for *everyone* → the capability-contribute\n     skill owns it: it changes the shipped source (building mode, approval-gated). Say so\n     and hand over — nothing lands in MOD.\n3. Write the MOD.md change **first** (the `capability-lifecycle` skill's\n   `reference\u002Foverlay.md`, Capture and fold —\n   the MOD statement lands before anything depends on it), then apply to the render: seed\n   `\u003Caos_home>\u002Frendered\u002F.staging\u002F\u003Cid>\u002F` with a copy of the live `rendered\u002F\u003Cid>\u002F` (leaving\n   bytecode behind), apply the change there, and gate it like any re-render — the diff of\n   live against staged, then `aos-cap swap \u003Cid>` or `aos-cap discard \u003Cid>` (and any native\n   artifacts per the cheat-sheet — the `capability-lifecycle` skill's\n   `reference\u002Fharness-\u003Charness-runtime>.md`, load it now; native\n   edit verbs where they exist), through the STAGE→GATE→EXECUTE phases.\n4. `aos-cap rehash \u003Cid>` — refresh the recorded hashes in place so `verify`\n   stays clean; the persist hook commits `personal\u002F` (dated message). From now on\n   capability-upgrade re-applies this change on every upgrade. (New artifacts, jobs,\n   or keys → a full `aos-cap record` with the complete set from `aos-cap show`.)\n5. Confirm: \"recorded in your MOD.md — survives every upgrade.\"\n6. Promotion check — **signal-gated, never reflexive** (the judgment, tests,\n   threshold ladder, and etiquette live in the `capability-lifecycle` skill's\n   `reference\u002Foverlay.md`, Promote and retire).\n   An offer fires only on: objectively-broken workaround · forced mechanism override\n   (the change fought the template beyond its `{{mod}}` slots) · the user asked.\n   At most one one-liner offer, at the conversation's end, once per statement ever;\n   a \"no\" is recorded and never re-asked. Yes → hand to capability-contribute\n   with the statement. **Never open a PR or file an issue yourself — every upstream\n   write needs the user's explicit yes (contract).**\n\nCapture mode (drift found by `verify` or by noticing a hand-edit): same steps, but step 3's\n**second half** is skipped — the render already carries the change, so there is nothing to apply.\n**Step 3's MOD.md write still happens, and it is the whole point of capture mode**: the edit\nexists on disk and nowhere in the overlay, so the next upgrade would silently drop it. Skip the\nwrite and step 5's \"recorded in your MOD.md — survives every upgrade\" is a lie\n(the `capability-lifecycle` skill's `reference\u002Foverlay.md`, \"Capture and fold\").\n",{"name":5,"metadata":24,"description":7},{"aos":25},{"origin":26},"capability-lifecycle@0.7.0","main","31f4199ef67a0cedbdab2404eb9012d0c6e60c79","tests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Ffront\u002Fskills\u002Fcapability-evolve",2,"https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos","https:\u002F\u002Fgithub.com\u002FAlmogBaku","http:\u002F\u002Fwww.AlmogBaku.com","LLM hacker","2026-11-15 03:54:12",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add AlmogBaku\u002Faos --skill capability-evolve",{"tool":42,"command":43},"bunx","bunx skills add AlmogBaku\u002Faos --skill capability-evolve",{"tool":45,"command":46},"pnpm","pnpm dlx skills add AlmogBaku\u002Faos --skill capability-evolve","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Ffront\u002Fskills\u002Fcapability-evolve\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7DZT1MJJHC87HQVK2D6RRFW","wt-update","Updates an existing commitment when the user reports progress: completion, a new deadline, a stall, or abandonment. Use when the user says \"I did that\", \"finished X\", \"still waiting on Y\", \"push that to next week\", \"I started it\", or \"forget it, I'm not doing X\". Finds the matching open action, applies the change, and routes any knowledge the report carries to the knowledge base. Do NOT use to file a new commitment (that is wt-capture) or to find time for one (wt-schedule).","https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Fhome\u002Frendered\u002Fwork-tracker\u002Fskills\u002Fwt-update\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7DZSY8XSXBMD53Y5QKRX6CD","wt-steward","Maintains an existing commitments backlog: overdue, about to expire, stalled, and repeatedly-rescheduled commitments, and someday items gone cold. Use when the nightly cron job fires or the user asks to review or tidy their backlog ('review my backlog', 'what's gone stale on my list'). Does not capture or schedule new work — that happens when the user speaks, through wt-capture and wt-schedule.","https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Fhome\u002Frendered\u002Fwork-tracker\u002Fskills\u002Fwt-steward\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7DZST40GEJQ67KZSTG1PM93","wt-schedule","Estimates a commitment, links it to its project, and blocks time for it on the user's calendar. Use when the user asks to find time for something — \"when can I do this?\", \"find me two hours for the CFP\", \"block time for that tomorrow\", \"I want to work on it today\" — and immediately after wt-capture files a commitment that needs real hours. Do NOT use for a commitment that needs only a deadline or a reminder, and do NOT use to change what the user committed to — that is wt-update.","https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Fhome\u002Frendered\u002Fwork-tracker\u002Fskills\u002Fwt-schedule\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7DZSMTQT1CCMQ3MK984C7FS","wt-capture","Records something the user has said they must do themselves: classifies the commitment as next, waiting, someday or trivial, writes it as an action page in their commitments base, and hands off to wt-schedule when it needs real hours. Use when the user commits to work of their own — \"I need to find time to…\", \"I have to…\", \"remind me to…\", \"help me remember…\", \"put that on my list\", \"I should … at some point\". Do NOT use when the user asks the assistant to do the work (\"write the CFP\", \"research X\", \"email Sam\") — that is a request to act now, not a commitment to track. Do NOT use for thoughts, facts or notes carrying no commitment; those are knowledge and belong to kb-capture.","https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Fhome\u002Frendered\u002Fwork-tracker\u002Fskills\u002Fwt-capture\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7DZSG76N1GGR9C82RFK37RJ","work-tracker","Answers questions about the user's own commitments by querying their commitments base, explains the four statuses (next, waiting, someday, done), routes a request to the right work-tracker skill, and states who may change what without asking. Use when the user asks what they should be working on, what is overdue, what they are waiting on, or how their task tracking works, and no narrower work-tracker skill matches. Do NOT use to file a commitment the user just made (that is wt-capture), to find time for one (wt-schedule), or to report progress on one (wt-update).","https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Fhome\u002Frendered\u002Fwork-tracker\u002Fskills\u002Fwork-tracker\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7DZSBWW4AQ7J1BTZHCJERTJ","kb","Explains how the user's knowledge bases are laid out and which kb skill handles a given job — the tree, the one queue, expiry, links, base health, maintenance. Use when the user asks how their knowledge base works, what state a base is in, why something was or was not kept, or wants base maintenance run, and no narrower kb skill matches. Do NOT use to file something the user just said (that is kb-capture), to answer a question from stored knowledge (that is kb-recall), or to pick a destination base for a write already in hand (that is kb-route).","https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Fhome\u002Frendered\u002Fkb\u002Fskills\u002Fkb\u002FSKILL.md",[],[]]