[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79B7C45AKS1FD76567PTV2S":3,"skill-same:01M79B7C45AKS1FD76567PTV2S":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},"01M79B7C45AKS1FD76567PTV2S","wt-capture",null,"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.","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-capture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: wt-capture\ndescription: 'Records something the user has said they must do themselves: classifies\n  the commitment as next, waiting, someday or trivial, writes it as an action page\n  in their commitments base, and hands off to wt-schedule when it needs real hours.\n  Use when the user commits to work of their own — \"I need to find time to…\", \"I have\n  to…\", \"remind me to…\", \"help me remember…\", \"put that on my list\", \"I should … at\n  some point\". Do NOT use when the user asks the assistant to do the work (\"write\n  the CFP\", \"research X\", \"email Sam\") — that is a request to act now, not a commitment\n  to track. Do NOT use for thoughts, facts or notes carrying no commitment; those\n  are knowledge and belong to kb-capture.'\nmetadata:\n  aos:\n    origin: work-tracker@0.1.5\n---\n# capture\n\nWrite the page, confirm, hand off. Under five seconds to the confirmation.\n\n## Clarify — one question, asked of yourself\n\n**Is this mine to do?** Not *\"is it actionable?\"* — everything is actionable to an agent, so\nthat question routes every request into the list.\n\n| The commitment is | status: | plus | then |\n|---|---|---|---|\n| real work of the user's | `next` | — | hand off to wt-schedule |\n| someone else's to answer | `waiting` | `waiting_on:` | nothing more |\n| a deadline, not hours | `next` | `due:` | a reminder, no block |\n| not now, maybe never | `someday` | — | nothing more |\n| trivial | `next` | `estimate:` | say *\"that's a two-minute job — worth doing now?\"* **and file it anyway** |\n\n**`status` is one of exactly those four words.** Nothing validates it, so a fifth value —\n`trivial`, `blocked`, `urgent` — is written happily and then matches none of the steward's\nqueries nor its `--without block` backstop, which makes the commitment permanently invisible.\nTrivial work is `next` with a small `estimate:`, not a status of its own.\n\n`someday` protects the list: without it every musing becomes a scheduled commitment, and a\nschedule the user stops trusting is worse than none.\n\n**Never block on the recommendation.** Ask about the two-minute job in the same breath as\nconfirming, not instead of it — a commitment lost to a clarifying question costs more than a\nwrong estimate. If the exchange resolves it (*\"yeah, done\"*), file it `done` with an\n`expires:` rather than skipping the page.\n\n## Write it\n\nThe page is `actions\u002F\u003Cslug>.md`, and there is no `kb` verb that creates one — write it with\nordinary file tools, then attribute it:\n\n```\nkb --base commitments commit --verb create --path actions\u002Fwrite-the-cfp.md \\\n  --summary \"commitment: write the KubeCon CFP\"\n```\n\nAll three flags are required. Skip this and the page reaches git only through the sync sweep,\nwith no acting subject, and `kb lint` reports it — as a *report*, not a failure: bare `kb lint`\nexits 0 even with criticals in it, so read what it says rather than trusting the exit code.\n\nFrontmatter. The four marked `required` are the ones `kb lint` reports as missing — write all\nseven anyway, since the steward's queries depend on `status` and `since`:\n\n```yaml\ntitle: call the dentist        # required\ntype: action                   # required\ncreated: \u003CDATE>            # required\ntimestamp: \u003CTIMESTAMP>    # required\nstatus: next                   # plus due \u002F estimate \u002F waiting_on per the table above\nsince: \u003CDATE>\nslipped: 0\n```\n\n**The user's own words go in the body, verbatim** — that sentence is the only record of what\nthey actually committed to, and a tidier paraphrase is usually a paraphrase of what you\nassumed they meant.\n\nThen add the page to `index.md`, or it is invisible to the map even though every query still\nfinds it: `kb --base commitments index rebuild` does it mechanically.\n\nShape and the full field list: the `work-tracker` skill's `reference\u002Faction-page.md`.\n\nA correction to something already filed is `kb capture --corrects \u003Cpath>` — a link, not prose\nfor a later pass to guess at.\n\n## Hand off\n\nNeeds real hours → invoke wt-schedule, in a sub-agent where the harness has them and inline\notherwise. Which one happened, and whether a block was taken or there was no calendar, is\nrecorded on the page (`block` present or absent) rather than said: this user's confirmation\nis the 🦜 alone, and an unblocked commitment surfaces in the steward's nightly backstop count.\n\nThe user should experience one act, not two. wt-schedule comes back with the time; you\nconfirm once — and per the user's preference below, that one confirmation is the 🦜.\n\n**How the confirmation reads is the user's call**: confirm every commitment with a single 🦜\nemoji — nothing else, ever. Never echo the commitment back, not even after wt-schedule took a\nblock: the confirmation is still just 🦜 (the time is on their calendar and on the page, and\nthey can ask). A sacred-time conflict wt-schedule surfaces is a question, not a confirmation,\nand still gets asked. Honour it exactly — this is the line they see several times a day, and\nit is the whole surface of an interaction whose other half is silent.\n\n**How the page is phrased** is verb-first — *\"Email Sam the deck\"*, not *\"Sam has the deck\"* —\nin the `title:`. Anything with a deadline gets the deadline in the title too (*\"Submit the\nKubeCon CFP by Fri 21 Nov\"*), because that is the part worth seeing at a glance. The body\nstill holds the user's own words verbatim.\n\n## When something fails\n\nThe commitment matters more than the bookkeeping around it. If the page landed and the\nattribution, the flag or the hand-off did not, mention it and move on — an unscheduled action\nis one without a `block`, which the steward's `--without block` backstop already finds. Losing\nthe thought is the only real failure here.\n","# capture\n\nWrite the page, confirm, hand off. Under five seconds to the confirmation.\n\n## Clarify — one question, asked of yourself\n\n**Is this mine to do?** Not *\"is it actionable?\"* — everything is actionable to an agent, so\nthat question routes every request into the list.\n\n| The commitment is | status: | plus | then |\n|---|---|---|---|\n| real work of the user's | `next` | — | hand off to wt-schedule |\n| someone else's to answer | `waiting` | `waiting_on:` | nothing more |\n| a deadline, not hours | `next` | `due:` | a reminder, no block |\n| not now, maybe never | `someday` | — | nothing more |\n| trivial | `next` | `estimate:` | say *\"that's a two-minute job — worth doing now?\"* **and file it anyway** |\n\n**`status` is one of exactly those four words.** Nothing validates it, so a fifth value —\n`trivial`, `blocked`, `urgent` — is written happily and then matches none of the steward's\nqueries nor its `--without block` backstop, which makes the commitment permanently invisible.\nTrivial work is `next` with a small `estimate:`, not a status of its own.\n\n`someday` protects the list: without it every musing becomes a scheduled commitment, and a\nschedule the user stops trusting is worse than none.\n\n**Never block on the recommendation.** Ask about the two-minute job in the same breath as\nconfirming, not instead of it — a commitment lost to a clarifying question costs more than a\nwrong estimate. If the exchange resolves it (*\"yeah, done\"*), file it `done` with an\n`expires:` rather than skipping the page.\n\n## Write it\n\nThe page is `actions\u002F\u003Cslug>.md`, and there is no `kb` verb that creates one — write it with\nordinary file tools, then attribute it:\n\n```\nkb --base commitments commit --verb create --path actions\u002Fwrite-the-cfp.md \\\n  --summary \"commitment: write the KubeCon CFP\"\n```\n\nAll three flags are required. Skip this and the page reaches git only through the sync sweep,\nwith no acting subject, and `kb lint` reports it — as a *report*, not a failure: bare `kb lint`\nexits 0 even with criticals in it, so read what it says rather than trusting the exit code.\n\nFrontmatter. The four marked `required` are the ones `kb lint` reports as missing — write all\nseven anyway, since the steward's queries depend on `status` and `since`:\n\n```yaml\ntitle: call the dentist        # required\ntype: action                   # required\ncreated: \u003CDATE>            # required\ntimestamp: \u003CTIMESTAMP>    # required\nstatus: next                   # plus due \u002F estimate \u002F waiting_on per the table above\nsince: \u003CDATE>\nslipped: 0\n```\n\n**The user's own words go in the body, verbatim** — that sentence is the only record of what\nthey actually committed to, and a tidier paraphrase is usually a paraphrase of what you\nassumed they meant.\n\nThen add the page to `index.md`, or it is invisible to the map even though every query still\nfinds it: `kb --base commitments index rebuild` does it mechanically.\n\nShape and the full field list: the `work-tracker` skill's `reference\u002Faction-page.md`.\n\nA correction to something already filed is `kb capture --corrects \u003Cpath>` — a link, not prose\nfor a later pass to guess at.\n\n## Hand off\n\nNeeds real hours → invoke wt-schedule, in a sub-agent where the harness has them and inline\notherwise. Which one happened, and whether a block was taken or there was no calendar, is\nrecorded on the page (`block` present or absent) rather than said: this user's confirmation\nis the 🦜 alone, and an unblocked commitment surfaces in the steward's nightly backstop count.\n\nThe user should experience one act, not two. wt-schedule comes back with the time; you\nconfirm once — and per the user's preference below, that one confirmation is the 🦜.\n\n**How the confirmation reads is the user's call**: confirm every commitment with a single 🦜\nemoji — nothing else, ever. Never echo the commitment back, not even after wt-schedule took a\nblock: the confirmation is still just 🦜 (the time is on their calendar and on the page, and\nthey can ask). A sacred-time conflict wt-schedule surfaces is a question, not a confirmation,\nand still gets asked. Honour it exactly — this is the line they see several times a day, and\nit is the whole surface of an interaction whose other half is silent.\n\n**How the page is phrased** is verb-first — *\"Email Sam the deck\"*, not *\"Sam has the deck\"* —\nin the `title:`. Anything with a deadline gets the deadline in the title too (*\"Submit the\nKubeCon CFP by Fri 21 Nov\"*), because that is the part worth seeing at a glance. The body\nstill holds the user's own words verbatim.\n\n## When something fails\n\nThe commitment matters more than the bookkeeping around it. If the page landed and the\nattribution, the flag or the hand-off did not, mention it and move on — an unscheduled action\nis one without a `block`, which the steward's `--without block` backstop already finds. Losing\nthe thought is the only real failure here.\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-capture",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-capture",{"tool":42,"command":43},"bunx","bunx skills add AlmogBaku\u002Faos --skill wt-capture",{"tool":45,"command":46},"pnpm","pnpm dlx skills add AlmogBaku\u002Faos --skill wt-capture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Faos\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Ffull-install\u002Ffront\u002Fskills\u002Fwt-capture\u002FSKILL.md",true,[],[51,58,65,72,77,84],{"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":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":74,"categories":75,"keywords":76,"publishedAt":19},"01M7DZSMTQT1CCMQ3MK984C7FS","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",[],[]]