[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79B4Y5E46RFH90DRWX4VCJC":3,"skill-same:01M79B4Y5E46RFH90DRWX4VCJC":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},"01M79B4Y5E46RFH90DRWX4VCJC","capability-remove",null,"Removes an installed aos capability exactly, walking its lockfile entry backwards — jobs, symlinks, marker blocks, config keys, agents it created, its tool — and leaving the user's MOD.md in place so a re-install returns personalized. Use when the user says \"remove\", \"uninstall\", or \"get rid of\" and names an installed capability. Do NOT use to undo one setting or turn off a single cron job — that is capability-evolve — and not to retire something upstream, which is capability-contribute.","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-remove\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: capability-remove\ndescription: Removes an installed aos capability exactly, walking its lockfile entry\n  backwards — jobs, symlinks, marker blocks, config keys, agents it created, its tool\n  — and leaving the user's MOD.md in place so a re-install returns personalized. Use\n  when the user says \"remove\", \"uninstall\", or \"get rid of\" and names an installed\n  capability. Do NOT use to undo one setting or turn off a single cron job — that\n  is capability-evolve — and not to retire something upstream, which is capability-contribute.\nmetadata:\n  aos:\n    origin: capability-lifecycle@0.7.0\n---\n# capability-remove\n\nNot in context yet? Load the `capability-lifecycle` skill first — the map, the\ncontract, and the Experience rules.\n\n1. `aos-cap show \u003Cid>` → the entry: artifacts, `links` and `uses_links` (including the\n   capability's tool binary, recorded as an artifact), `cron_owned`, config keys,\n   env variable names, scripts.\n2. Scope: removing the capability entirely, or *from one harness* while it\n   stays installed elsewhere? **Per-harness removal**: run step 4 for that harness only\n   and skip its render deletion (the render is shared — it stays), then re-`record` the\n   reduced set (start from `aos-cap show`, drop that harness's links\u002Fartifacts\u002Fjobs,\n   keep everything else), then step 6's verify scoped to that harness. The lockfile\n   entry and the MOD file both stay. Skip step 5. Step 3's dependents check still applies **scoped to this harness** (a\n   capability installed here that depends on this one). Note the lockfile's\n   `cron_owned` is a flat id list with no harness dimension (§5.5), so identify\n   *this* harness's jobs by introspecting the harness, not by reading the lockfile.\n   **Whole removal** continues below.\n3. Dependents check: another entry in `aos-cap list` whose manifest\n   `depends.capabilities` or `uses` names this one → say so; stop unless the user insists\n   (then remove dependents first). A dependent's `uses_links` point into this render, so\n   removing it first is what keeps them from dangling.\n4. Un-write per the cheat-sheet's Removal section (load\n   the `capability-lifecycle` skill's `reference\u002Fharness-\u003Charness-runtime>.md` now), in its\n   stated order — typically: jobs →\n   skill symlinks (delete the `links` and `uses_links`; then send **only**\n   `\u003Caos_home>\u002Frendered\u002F\u003Cid>\u002F` to the OS trash — `gio trash`, `trash-put`, or the\n   platform's own; never `rm -rf`, never anything under `personal\u002F`, and never the\n   `MOD.md` — recoverable from the trash) → marker blocks → config keys → `.env` lines (ask\n   first) → agents this capability created and nothing else uses (never an adopted one —\n   contract) → scripts\u002Fhooks (revoke each hook's consent record first) →\n   its tool (`uv tool uninstall`). A recorded link into `\u003Caos_home>\u002Fvendor` is a referenced\n   third-party skill: unlink it, and offer to drop the vendor clone only if no other entry\n   links into it.\n   **Its machine-local state under `\u003Caos_home>\u002F.aos\u002F` is not in the lockfile, so nothing walks\n   it backwards** — removing kb leaves `kb-principal.yml` and `kb-registry.yaml` behind.\n   Offer to delete them, and say what each is: the principal list (who authors writes on\n   this machine) and the registry (the list of every base). Both are the user's, not the\n   capability's — an unasked deletion loses answers they gave; a re-install would adopt the\n   old values silently, which is right often enough to be worth asking about.\n5. Tell the user their MOD.md stays: \"your answers survive — in your personal repo,\n   reinstalling brings it back personalized.\"\n6. Verify: re-introspect until no `metadata.aos.origin`, `aos:` names, marker\n   blocks, or links into `rendered\u002F\u003Cid>\u002F` remain; `aos-cap remove \u003Cid>`; friendly close.\n","# capability-remove\n\nNot in context yet? Load the `capability-lifecycle` skill first — the map, the\ncontract, and the Experience rules.\n\n1. `aos-cap show \u003Cid>` → the entry: artifacts, `links` and `uses_links` (including the\n   capability's tool binary, recorded as an artifact), `cron_owned`, config keys,\n   env variable names, scripts.\n2. Scope: removing the capability entirely, or *from one harness* while it\n   stays installed elsewhere? **Per-harness removal**: run step 4 for that harness only\n   and skip its render deletion (the render is shared — it stays), then re-`record` the\n   reduced set (start from `aos-cap show`, drop that harness's links\u002Fartifacts\u002Fjobs,\n   keep everything else), then step 6's verify scoped to that harness. The lockfile\n   entry and the MOD file both stay. Skip step 5. Step 3's dependents check still applies **scoped to this harness** (a\n   capability installed here that depends on this one). Note the lockfile's\n   `cron_owned` is a flat id list with no harness dimension (§5.5), so identify\n   *this* harness's jobs by introspecting the harness, not by reading the lockfile.\n   **Whole removal** continues below.\n3. Dependents check: another entry in `aos-cap list` whose manifest\n   `depends.capabilities` or `uses` names this one → say so; stop unless the user insists\n   (then remove dependents first). A dependent's `uses_links` point into this render, so\n   removing it first is what keeps them from dangling.\n4. Un-write per the cheat-sheet's Removal section (load\n   the `capability-lifecycle` skill's `reference\u002Fharness-\u003Charness-runtime>.md` now), in its\n   stated order — typically: jobs →\n   skill symlinks (delete the `links` and `uses_links`; then send **only**\n   `\u003Caos_home>\u002Frendered\u002F\u003Cid>\u002F` to the OS trash — `gio trash`, `trash-put`, or the\n   platform's own; never `rm -rf`, never anything under `personal\u002F`, and never the\n   `MOD.md` — recoverable from the trash) → marker blocks → config keys → `.env` lines (ask\n   first) → agents this capability created and nothing else uses (never an adopted one —\n   contract) → scripts\u002Fhooks (revoke each hook's consent record first) →\n   its tool (`uv tool uninstall`). A recorded link into `\u003Caos_home>\u002Fvendor` is a referenced\n   third-party skill: unlink it, and offer to drop the vendor clone only if no other entry\n   links into it.\n   **Its machine-local state under `\u003Caos_home>\u002F.aos\u002F` is not in the lockfile, so nothing walks\n   it backwards** — removing kb leaves `kb-principal.yml` and `kb-registry.yaml` behind.\n   Offer to delete them, and say what each is: the principal list (who authors writes on\n   this machine) and the registry (the list of every base). Both are the user's, not the\n   capability's — an unasked deletion loses answers they gave; a re-install would adopt the\n   old values silently, which is right often enough to be worth asking about.\n5. Tell the user their MOD.md stays: \"your answers survive — in your personal repo,\n   reinstalling brings it back personalized.\"\n6. Verify: re-introspect until no `metadata.aos.origin`, `aos:` names, marker\n   blocks, or links into `rendered\u002F\u003Cid>\u002F` remain; `aos-cap remove \u003Cid>`; friendly close.\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-remove",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-remove",{"tool":42,"command":43},"bunx","bunx skills add AlmogBaku\u002Faos --skill capability-remove",{"tool":45,"command":46},"pnpm","pnpm dlx skills add AlmogBaku\u002Faos --skill capability-remove","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Ffront\u002Fskills\u002Fcapability-remove\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",[],[]]