[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79B7TVB5WEWHC88YMV0XFDF":3,"skill-same:01M79B7TVB5WEWHC88YMV0XFDF":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},"01M79B7TVB5WEWHC88YMV0XFDF","wt-update",null,"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).","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\u002Fwt-update\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: wt-update\ndescription: 'Updates an existing commitment when the user reports progress: completion,\n  a new deadline, a stall, or abandonment. Use when the user says \"I did that\", \"finished\n  X\", \"still waiting on Y\", \"push that to next week\", \"I started it\", or \"forget it,\n  I''m not doing X\". Finds the matching open action, applies the change, and routes\n  any knowledge the report carries to the knowledge base. Do NOT use to file a new\n  commitment (that is wt-capture) or to find time for one (wt-schedule).'\nmetadata:\n  aos:\n    origin: work-tracker@0.1.5\n---\n# update\n\nThree steps. The third is the one an implementation forgets, and the one that keeps the whole\ndesign honest.\n\n## 1. Find what was meant\n\n```\nkb --base commitments find --where type=action --where status=next\n```\n\nThe open set is small, so match by title against what the user said. Add\n`--where status=waiting` when the report sounds like waiting (*\"still nothing from Robin\"*).\n\nGenuinely ambiguous between two actions → ask which. Guessing here writes the wrong page and\nthe user finds out later, if ever, which is worse than one short question.\n\nNothing matches → this is probably a new commitment. Hand to wt-capture rather than\ninventing a page here.\n\n## 2. Apply it\n\n`kb set` for every change — it validates against the base's schema and makes its own\nattributed commit:\n\n| The user says | Apply |\n|---|---|\n| *\"I did that\"*, *\"finished X\"* | `status=done` **and** `expires=\u003Ctoday + 90 days>` |\n| *\"I started it\"* | `since=\u003Ctoday>` — nothing else |\n| *\"still waiting on Robin\"* | `status=waiting waiting_on=Robin since=\u003Ctoday>` |\n| *\"push that to next week\"* | the new `due=` or `block=`, and `slipped` +1 |\n| *\"forget it, I'm not doing X\"* | `status=done` + a near `expires` — see below |\n\n```\nkb --base commitments set actions\u002Fwrite-the-cfp.md status=done expires=\u003CDATE>\n```\n\n**`since` moves on any progress report**, even one that changes nothing else. That is what\nkeeps stall detection honest: without it the steward nags about a commitment actively being\nworked on, and a nag that is wrong once gets the whole nightly report ignored.\n\n**Completion needs `expires` as well as `status: done`.** `expires` is the only lifetime rule\nkb has, so a done action without one lives forever — and a list with no exit is the graveyard\nthis capability exists to avoid. The user's retention window is 90 days.\n\n**Abandonment is a status, not a deletion.** *\"Forget it\"* still gets `done` plus a short\n`expires`: the record of having decided not to do something is worth the few weeks it costs,\nand deleting on the spot means the user cannot ask why it disappeared.\n\n## 3. Hand the outcome to kb\n\n*\"They want a pilot in Q4\"* is **knowledge**, not a commitment. It goes to the knowledge base\nas a capture, so it outlives the action when `expires` fires:\n\n```\nkb --base \u003Cthe user's knowledge base> capture --text \"Acme wants a pilot in Q4\" --source chat\n```\n\n**`--base` is not optional here, and omitting it is silent.** An unqualified `kb capture`\nresolves by walking up from the working directory, and you are working inside the commitments\nbase — so the knowledge lands in the base it was supposed to outlive, at exit 0, with a\ncheerful confirmation naming a file in the wrong tree. Name the knowledge base explicitly\n(kb-route picks it if you do not know which one); every other command in this capability\ncarries `--base commitments`, and this is the one that must not.\n\nThat lands in the knowledge base's `.kb\u002Fpending\u002F`, and kb's archiver promotes it to the\nproject page overnight — you do not write the wiki page yourself.\n\n**Without this step the never-the-only-copy rule is aspirational**, and `kb prune` starts\nlosing things: the action page said the call happened, the action page is gone, and what was\nactually agreed went with it. Everything else here is bookkeeping; this is the part that\nprotects the user's memory.\n\nA report that carries no knowledge needs nothing — most *\"I did that\"*s are exactly that.\nJudge whether a fact came with it, and prefer capturing over not: a redundant capture costs\none queue entry, a lost one costs the thing itself.\n","# update\n\nThree steps. The third is the one an implementation forgets, and the one that keeps the whole\ndesign honest.\n\n## 1. Find what was meant\n\n```\nkb --base commitments find --where type=action --where status=next\n```\n\nThe open set is small, so match by title against what the user said. Add\n`--where status=waiting` when the report sounds like waiting (*\"still nothing from Robin\"*).\n\nGenuinely ambiguous between two actions → ask which. Guessing here writes the wrong page and\nthe user finds out later, if ever, which is worse than one short question.\n\nNothing matches → this is probably a new commitment. Hand to wt-capture rather than\ninventing a page here.\n\n## 2. Apply it\n\n`kb set` for every change — it validates against the base's schema and makes its own\nattributed commit:\n\n| The user says | Apply |\n|---|---|\n| *\"I did that\"*, *\"finished X\"* | `status=done` **and** `expires=\u003Ctoday + 90 days>` |\n| *\"I started it\"* | `since=\u003Ctoday>` — nothing else |\n| *\"still waiting on Robin\"* | `status=waiting waiting_on=Robin since=\u003Ctoday>` |\n| *\"push that to next week\"* | the new `due=` or `block=`, and `slipped` +1 |\n| *\"forget it, I'm not doing X\"* | `status=done` + a near `expires` — see below |\n\n```\nkb --base commitments set actions\u002Fwrite-the-cfp.md status=done expires=\u003CDATE>\n```\n\n**`since` moves on any progress report**, even one that changes nothing else. That is what\nkeeps stall detection honest: without it the steward nags about a commitment actively being\nworked on, and a nag that is wrong once gets the whole nightly report ignored.\n\n**Completion needs `expires` as well as `status: done`.** `expires` is the only lifetime rule\nkb has, so a done action without one lives forever — and a list with no exit is the graveyard\nthis capability exists to avoid. The user's retention window is 90 days.\n\n**Abandonment is a status, not a deletion.** *\"Forget it\"* still gets `done` plus a short\n`expires`: the record of having decided not to do something is worth the few weeks it costs,\nand deleting on the spot means the user cannot ask why it disappeared.\n\n## 3. Hand the outcome to kb\n\n*\"They want a pilot in Q4\"* is **knowledge**, not a commitment. It goes to the knowledge base\nas a capture, so it outlives the action when `expires` fires:\n\n```\nkb --base \u003Cthe user's knowledge base> capture --text \"Acme wants a pilot in Q4\" --source chat\n```\n\n**`--base` is not optional here, and omitting it is silent.** An unqualified `kb capture`\nresolves by walking up from the working directory, and you are working inside the commitments\nbase — so the knowledge lands in the base it was supposed to outlive, at exit 0, with a\ncheerful confirmation naming a file in the wrong tree. Name the knowledge base explicitly\n(kb-route picks it if you do not know which one); every other command in this capability\ncarries `--base commitments`, and this is the one that must not.\n\nThat lands in the knowledge base's `.kb\u002Fpending\u002F`, and kb's archiver promotes it to the\nproject page overnight — you do not write the wiki page yourself.\n\n**Without this step the never-the-only-copy rule is aspirational**, and `kb prune` starts\nlosing things: the action page said the call happened, the action page is gone, and what was\nactually agreed went with it. Everything else here is bookkeeping; this is the part that\nprotects the user's memory.\n\nA report that carries no knowledge needs nothing — most *\"I did that\"*s are exactly that.\nJudge whether a fact came with it, and prefer capturing over not: a redundant capture costs\none queue entry, a lost one costs the thing itself.\n",{"name":5,"metadata":24,"description":7},{"aos":25},{"origin":26},"work-tracker@0.1.5","main","31f4199ef67a0cedbdab2404eb9012d0c6e60c79","tests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Ffront\u002Fskills\u002Fwt-update",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 wt-update",{"tool":42,"command":43},"bunx","bunx skills add AlmogBaku\u002Faos --skill wt-update",{"tool":45,"command":46},"pnpm","pnpm dlx skills add AlmogBaku\u002Faos --skill wt-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Ffront\u002Fskills\u002Fwt-update\u002FSKILL.md",true,[],[51,56,63,70,77,84],{"skillNo":52,"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":53,"categories":54,"keywords":55,"publishedAt":19},"01M7DZT1MJJHC87HQVK2D6RRFW","https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Fhome\u002Frendered\u002Fwork-tracker\u002Fskills\u002Fwt-update\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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",[],[]]