[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75EJC6ACBCEM09QYVWHZGCG":3,"skill-same:01M75EJC6ACBCEM09QYVWHZGCG":69},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75EJC6ACBCEM09QYVWHZGCG","docs-updater",null,"Bring the repository's documentation in line with the code — find where the docs and the code disagree, and fix the docs (or, in check mode, only report it). Use after a feature, fix, or architectural change; when the user asks to update or audit the docs; and from ship and end-session, which run it scoped to a branch's diff.","jwh3times\u002FLeaseBook","jwh3times","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1965019?v=4","01M720KXPKWJRK0WCC0ZD480M7","Jerry Holland","01M75EEXPV2VJKZC9D9XEJVXSB",1,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdocs-updater\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\n# GENERATED — do not edit. Source: .agents\u002Fskills\u002Fdocs-updater\u002FSKILL.md — regenerate with 'node scripts\u002Fsync-agents.mjs'.\nname: docs-updater\ndescription: Bring the repository's documentation in line with the code — find where the docs and the code disagree, and fix the docs (or, in check mode, only report it). Use after a feature, fix, or architectural change; when the user asks to update or audit the docs; and from ship and end-session, which run it scoped to a branch's diff.\nmetadata:\n  settings: docs workspace issue-tracker human-follow-up\n---\n\n# Docs updater\n\nFind drift between what the docs say and what the code does, then fix the docs. The code is the\ntruth: never invent a feature, a command, or a capability the code does not have.\n\n**Announce at start:** \"I'm using the docs-updater skill to bring the docs in line with the code.\"\n\nRun shell snippets in bash (Git Bash on Windows).\n\n## 0. Settings\n\nThis skill reads `docs\u002Fagents\u002Fdocs.md`, `docs\u002Fagents\u002Fworkspace.md`,\n`docs\u002Fagents\u002Fissue-tracker.md` and `docs\u002Fagents\u002Fhuman-follow-up.md`. Follow\n`.agents\u002Fskills\u002Fdocs-updater\u002Fsettings\u002FREADME.md` to read them and complete any that are missing; the\ndefinitions sit beside it.\n\n## 1. Mode and scope\n\nTake both from the arguments or the caller's instructions:\n\n- **Mode** — `fix` (the default) edits the docs; `check` edits nothing and reports drift.\n- **Scope** — a diff range (`\u003Cbase>..HEAD`), a list of changes, or none for a full audit of every\n  `Doc map` item.\n\nA caller may add constraints; follow them. From `ship`: the branch is not merged, so leave\n`ship-owned` documents alone and make no claim that the work shipped — no roadmap, archive, release\nor merge status, or board change. Describing what the branch implements is still in scope. From\n`end-session`: the session's work, merged or not, as it says.\n\n## 2. Find the documents in scope\n\nFor a diff range:\n\n```bash\ngit diff --stat \"$range\"\ngit diff --name-status \"$range\"\n```\n\nRead the diff itself, not only the file list. Skip generated copies (the mirrors the\n`Generated-config check` regenerates) and read their sources instead. Skip the bodies of the skills\nthe `Doc map` marks `frozen` too (installed, and never edited here): read only what their change\nmeans for claims in other documents, such as a renamed setting or a new command. A repository that\ninstalls its own skills skips the installed copy, never the authored source it was installed from.\nMatch each change against every `Doc map` item's **when**: the paths it names, and the kind of\nchange (a new endpoint, a changed command, a new setting, a removed feature). A **when** is a\nsignal, not a limit: a change that plainly affects a document it does not match is in scope too, and\nis named in the report so the `Doc map` can be extended. A pure refactor often owes no doc edit; say\nso rather than inventing one. For a list of changes, match the same way. For a full audit, every\nitem is in scope.\n\nThen search for the names the diff removed or renamed (settings, commands, files, flags, counts\nsuch as \"all four\"), and for names whose meaning it widened or narrowed: stale references to them\nare drift that no **when** predicts. For a member the\ndiff adds to an enumerated set (a marker, a setting, a skill), search for its siblings instead: a\nlist that names them but not the new one is now incomplete. Search for a name as it is written in\nthe docs, usually in backticks (`` `frozen` ``), so a common word does not bury the hits. Search\nwider than the `Doc map`, skipping generated copies and `frozen` documents:\n\n- every tracked Markdown file (`git ls-files '*.md'`);\n- the companion, from its own root, when its checkout exists;\n- each wiki: the `Follow-up wiki`, and any `Doc map` item that lives in a wiki, when the change is\n  on the default branch, in a read-only clone in a scratch location.\n\nA hit in a document the `Doc map` lacks is fixed like any other and named in the report, so the map\ncan be extended. A wiki waits for the merge, so its pages never point at a file that is not there\nyet: a run on an unmerged branch (every run from `ship`) skips it and reports that the wiki search\nis owed after the merge. The next `end-session`, or any run on the default branch, performs it and\nfixes what it finds.\n\n## 3. Check each document against the code\n\nRead each document in scope, then verify every claim the change could affect against its source of\ntruth: the `Drift probes`, and otherwise the code, manifests, configs and CI workflows themselves.\nExecutable config outranks prose. Count what a probe lists rather than trusting a number in a doc\n(CI jobs by their top-level keys, not by every `name:`).\n\nA scoped run reports drift it finds outside its scope (an older claim a probe contradicts) without\nfixing it: that drift belongs to its own change. A full audit fixes it.\n\n**Companion documents.** When the `Private companion` is set, require its checkout before reading\nor editing them, and inspect it from its own root (`git -C private status`, `git -C private log`):\nthe outer repository's history is never evidence about it. When the checkout is absent, check the\npublic documents and report which companion checks could not run; create nothing in its place.\n\n## 4. Fix (fix mode)\n\nEdit each drifted document, honoring its marker:\n\n- `frozen` — never edit. `append-only` — add, never change. `amend-only` — add a dated amendment\n  note.\n- `owner-only` — report the drift; the user edits it.\n- `ship-owned` — leave it to `ship`. Outside `ship`, add an `Unreleased` changelog entry at most;\n  never a version, date or dated section.\n- `pinned` — another check fingerprints it, and any edit, even to a link, fails that check until\n  the pin it names is updated. Edit it only when the change requires it; first confirm the edit\n  alters nothing the pin protects (requirements, matrix rows), then update the pin in the same\n  change, and name both in the report so the caller's PR says why. A `pinned` document in scope\n  that needs no edit keeps its pin; still check that the pin matches it, and report it current.\n\nWrite so the next reader trusts the docs:\n\n- **One home per fact.** Update a fact where the `Doc map` says it lives, and point to it from\n  elsewhere instead of copying it. A thin entry point (`CLAUDE.md` importing `AGENTS.md`) gets no\n  content of its own.\n- **What is, not what is planned.** Project guides describe implemented behavior. Work state —\n  status, next steps, to-dos — lives in issues, not Markdown: a doc may state the resulting contract\n  (\"the secret is in the vault\"), never the pending action.\n- **The rule that survives.** History belongs in the changelog and ADRs; a doc records the current\n  rule and may cite the issue that set it. In a document that mixes the two (a survey beside the\n  design built from it), update the current-state claims and leave dated findings as written.\n  Remove a known limitation only when the code shows it fixed.\n- **Decisions and vocabulary.** Never edit an accepted ADR to match the code; report the\n  contradiction. When a glossary (`CONTEXT.md`) defines a term, point at it rather than restating\n  the definition, and do not rename code to match new vocabulary.\n- **Keep private things private.** Nothing on the `Doc map` **Never in public docs** list, no\n  secrets, credentials, account identifiers, live resource names, or links into the companion goes\n  into a public document. A security weakness follows the `Security findings` route, never a public\n  page.\n- **Generated files.** Edit the source, never the generated copy, then run the\n  `Generated-config check` regenerate command. Leave agent and skill frontmatter alone unless asked.\n- **Setup steps** change only when a prerequisite, command or port really changed.\n\nLeave every edit uncommitted, in the public checkout and the companion alike: the caller commits,\nor the user does when the skill ran on its own.\n\n## 5. Human actions\n\nList every required human action the change leaves (access setup, a dashboard change, credentials,\na manual check), or say that there are none. Run from `ship` or `end-session`, return the list to\nthe caller, which runs the follow-up procedure once for all of it. Run on its own, run the\n`## Procedure` in `.agents\u002Fskills\u002Fdocs-updater\u002Fsettings\u002Fhuman-follow-up.md` yourself. Either way, a\nfollow-up never lives only in a doc.\n\n## 6. Validate\n\n- `Docs validation`, each command from its folder (the repository root when none is named).\n- `Generated-config check`.\n- `git diff --check` for whitespace errors.\n- Links and anchors in every edited document resolve: relative paths exist, and `#anchors` match a\n  heading in their target.\n\nA failure caused by this run's edits is fixed before reporting. Never suppress or work around a real\nfailure; report it.\n\n## 7. Report\n\nReport private-content leaks first, in either mode. Then, one line per document, labelled in plain\ntext:\n\n- **current** — checked against the code, no change needed;\n- **changed** — what changed (fix mode);\n- **drift** — what disagrees and with which source: left unfixed in check mode, or not resolvable\n  from the code alone (a feature disabled or removed?), or in an `owner-only` or `frozen` document.\n\nThen the terms step 2 searched for and where (tracked Markdown, the companion, each wiki), or that\nit searched for none; the changes no `Doc map` item's **when** matched; the human actions found\n(and, run on its own, their follow-up links or the publication blocker); validation results;\ncompanion checks that could not run; and that the edits are uncommitted.\n","# Docs updater\n\nFind drift between what the docs say and what the code does, then fix the docs. The code is the\ntruth: never invent a feature, a command, or a capability the code does not have.\n\n**Announce at start:** \"I'm using the docs-updater skill to bring the docs in line with the code.\"\n\nRun shell snippets in bash (Git Bash on Windows).\n\n## 0. Settings\n\nThis skill reads `docs\u002Fagents\u002Fdocs.md`, `docs\u002Fagents\u002Fworkspace.md`,\n`docs\u002Fagents\u002Fissue-tracker.md` and `docs\u002Fagents\u002Fhuman-follow-up.md`. Follow\n`.agents\u002Fskills\u002Fdocs-updater\u002Fsettings\u002FREADME.md` to read them and complete any that are missing; the\ndefinitions sit beside it.\n\n## 1. Mode and scope\n\nTake both from the arguments or the caller's instructions:\n\n- **Mode** — `fix` (the default) edits the docs; `check` edits nothing and reports drift.\n- **Scope** — a diff range (`\u003Cbase>..HEAD`), a list of changes, or none for a full audit of every\n  `Doc map` item.\n\nA caller may add constraints; follow them. From `ship`: the branch is not merged, so leave\n`ship-owned` documents alone and make no claim that the work shipped — no roadmap, archive, release\nor merge status, or board change. Describing what the branch implements is still in scope. From\n`end-session`: the session's work, merged or not, as it says.\n\n## 2. Find the documents in scope\n\nFor a diff range:\n\n```bash\ngit diff --stat \"$range\"\ngit diff --name-status \"$range\"\n```\n\nRead the diff itself, not only the file list. Skip generated copies (the mirrors the\n`Generated-config check` regenerates) and read their sources instead. Skip the bodies of the skills\nthe `Doc map` marks `frozen` too (installed, and never edited here): read only what their change\nmeans for claims in other documents, such as a renamed setting or a new command. A repository that\ninstalls its own skills skips the installed copy, never the authored source it was installed from.\nMatch each change against every `Doc map` item's **when**: the paths it names, and the kind of\nchange (a new endpoint, a changed command, a new setting, a removed feature). A **when** is a\nsignal, not a limit: a change that plainly affects a document it does not match is in scope too, and\nis named in the report so the `Doc map` can be extended. A pure refactor often owes no doc edit; say\nso rather than inventing one. For a list of changes, match the same way. For a full audit, every\nitem is in scope.\n\nThen search for the names the diff removed or renamed (settings, commands, files, flags, counts\nsuch as \"all four\"), and for names whose meaning it widened or narrowed: stale references to them\nare drift that no **when** predicts. For a member the\ndiff adds to an enumerated set (a marker, a setting, a skill), search for its siblings instead: a\nlist that names them but not the new one is now incomplete. Search for a name as it is written in\nthe docs, usually in backticks (`` `frozen` ``), so a common word does not bury the hits. Search\nwider than the `Doc map`, skipping generated copies and `frozen` documents:\n\n- every tracked Markdown file (`git ls-files '*.md'`);\n- the companion, from its own root, when its checkout exists;\n- each wiki: the `Follow-up wiki`, and any `Doc map` item that lives in a wiki, when the change is\n  on the default branch, in a read-only clone in a scratch location.\n\nA hit in a document the `Doc map` lacks is fixed like any other and named in the report, so the map\ncan be extended. A wiki waits for the merge, so its pages never point at a file that is not there\nyet: a run on an unmerged branch (every run from `ship`) skips it and reports that the wiki search\nis owed after the merge. The next `end-session`, or any run on the default branch, performs it and\nfixes what it finds.\n\n## 3. Check each document against the code\n\nRead each document in scope, then verify every claim the change could affect against its source of\ntruth: the `Drift probes`, and otherwise the code, manifests, configs and CI workflows themselves.\nExecutable config outranks prose. Count what a probe lists rather than trusting a number in a doc\n(CI jobs by their top-level keys, not by every `name:`).\n\nA scoped run reports drift it finds outside its scope (an older claim a probe contradicts) without\nfixing it: that drift belongs to its own change. A full audit fixes it.\n\n**Companion documents.** When the `Private companion` is set, require its checkout before reading\nor editing them, and inspect it from its own root (`git -C private status`, `git -C private log`):\nthe outer repository's history is never evidence about it. When the checkout is absent, check the\npublic documents and report which companion checks could not run; create nothing in its place.\n\n## 4. Fix (fix mode)\n\nEdit each drifted document, honoring its marker:\n\n- `frozen` — never edit. `append-only` — add, never change. `amend-only` — add a dated amendment\n  note.\n- `owner-only` — report the drift; the user edits it.\n- `ship-owned` — leave it to `ship`. Outside `ship`, add an `Unreleased` changelog entry at most;\n  never a version, date or dated section.\n- `pinned` — another check fingerprints it, and any edit, even to a link, fails that check until\n  the pin it names is updated. Edit it only when the change requires it; first confirm the edit\n  alters nothing the pin protects (requirements, matrix rows), then update the pin in the same\n  change, and name both in the report so the caller's PR says why. A `pinned` document in scope\n  that needs no edit keeps its pin; still check that the pin matches it, and report it current.\n\nWrite so the next reader trusts the docs:\n\n- **One home per fact.** Update a fact where the `Doc map` says it lives, and point to it from\n  elsewhere instead of copying it. A thin entry point (`CLAUDE.md` importing `AGENTS.md`) gets no\n  content of its own.\n- **What is, not what is planned.** Project guides describe implemented behavior. Work state —\n  status, next steps, to-dos — lives in issues, not Markdown: a doc may state the resulting contract\n  (\"the secret is in the vault\"), never the pending action.\n- **The rule that survives.** History belongs in the changelog and ADRs; a doc records the current\n  rule and may cite the issue that set it. In a document that mixes the two (a survey beside the\n  design built from it), update the current-state claims and leave dated findings as written.\n  Remove a known limitation only when the code shows it fixed.\n- **Decisions and vocabulary.** Never edit an accepted ADR to match the code; report the\n  contradiction. When a glossary (`CONTEXT.md`) defines a term, point at it rather than restating\n  the definition, and do not rename code to match new vocabulary.\n- **Keep private things private.** Nothing on the `Doc map` **Never in public docs** list, no\n  secrets, credentials, account identifiers, live resource names, or links into the companion goes\n  into a public document. A security weakness follows the `Security findings` route, never a public\n  page.\n- **Generated files.** Edit the source, never the generated copy, then run the\n  `Generated-config check` regenerate command. Leave agent and skill frontmatter alone unless asked.\n- **Setup steps** change only when a prerequisite, command or port really changed.\n\nLeave every edit uncommitted, in the public checkout and the companion alike: the caller commits,\nor the user does when the skill ran on its own.\n\n## 5. Human actions\n\nList every required human action the change leaves (access setup, a dashboard change, credentials,\na manual check), or say that there are none. Run from `ship` or `end-session`, return the list to\nthe caller, which runs the follow-up procedure once for all of it. Run on its own, run the\n`## Procedure` in `.agents\u002Fskills\u002Fdocs-updater\u002Fsettings\u002Fhuman-follow-up.md` yourself. Either way, a\nfollow-up never lives only in a doc.\n\n## 6. Validate\n\n- `Docs validation`, each command from its folder (the repository root when none is named).\n- `Generated-config check`.\n- `git diff --check` for whitespace errors.\n- Links and anchors in every edited document resolve: relative paths exist, and `#anchors` match a\n  heading in their target.\n\nA failure caused by this run's edits is fixed before reporting. Never suppress or work around a real\nfailure; report it.\n\n## 7. Report\n\nReport private-content leaks first, in either mode. Then, one line per document, labelled in plain\ntext:\n\n- **current** — checked against the code, no change needed;\n- **changed** — what changed (fix mode);\n- **drift** — what disagrees and with which source: left unfixed in check mode, or not resolvable\n  from the code alone (a feature disabled or removed?), or in an `owner-only` or `frozen` document.\n\nThen the terms step 2 searched for and where (tracked Markdown, the companion, each wiki), or that\nit searched for none; the changes no `Doc map` item's **when** matched; the human actions found\n(and, run on its own, their follow-up links or the publication blocker); validation results;\ncompanion checks that could not run; and that the edits are uncommitted.\n",{"name":5,"metadata":24,"description":7},{"settings":25},"docs workspace issue-tracker human-follow-up","main","7741c685d4ed85a36dfb7c6659d5c125b99e48cb",".claude\u002Fskills\u002Fdocs-updater",0,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook","https:\u002F\u002Fgithub.com\u002Fjwh3times","2026-11-15 04:20:54",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jwh3times\u002FLeaseBook --skill docs-updater",{"tool":39,"command":40},"bunx","bunx skills add jwh3times\u002FLeaseBook --skill docs-updater",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jwh3times\u002FLeaseBook --skill docs-updater","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdocs-updater\u002FSKILL.md",true,[47,53,57,61,65],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"settings\u002Fdocs.md","REFERENCE","参考文档",3405,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdocs-updater\u002Fsettings\u002Fdocs.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"settings\u002Fhuman-follow-up.md",6331,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdocs-updater\u002Fsettings\u002Fhuman-follow-up.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"settings\u002Fissue-tracker.md",3175,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdocs-updater\u002Fsettings\u002Fissue-tracker.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"settings\u002FREADME.md",3227,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdocs-updater\u002Fsettings\u002FREADME.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"settings\u002Fworkspace.md",7151,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdocs-updater\u002Fsettings\u002Fworkspace.md",[70,78,83,90,97,104],{"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":77},"01M78SZRZ5JSR461749EDQRFCZ","what-next","Report what to work on next in this repository — an active handoff waiting to be resumed, work already in flight, ready issues ranked the way the board ranks them, what needs the user, what needs shaping first, and blocks that have quietly cleared — and recommend the one command to run. Read-only. Use when the user asks what to work on next, what is ready or what to pick up, or when a phase ends with no next piece of work chosen.","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwhat-next\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":79,"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":80,"categories":81,"keywords":82,"publishedAt":77},"01M78SZMAW7105G43GENZEFVD8","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhat-next\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M75EMB35PBWKWHT4PZ60HSK5","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M75EM79FGJB2ZV1B3SH7CHKT","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M75EM4TC7J46MJTAVZMHE020","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M75EM2AZWWYGGYV6XY8HYQ3N","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002FLeaseBook\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[]]