[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HTXQ86NWSD16625HB57C5X":3,"skill-same:01M6HTXQ86NWSD16625HB57C5X":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6HTXQ86NWSD16625HB57C5X","docs-drift",null,"Documentation-drift audit for this plugin monorepo. Audit either each scoped plugin's unreleased changelog claims or its latest shipped release from the previous reachable plugin-name--v* tag, then verify that plugin READMEs, docs, CLAUDE.md or AGENTS.md files, and root documentation tell the truth for the matching snapshot. Report meaningful contradictions with concrete proposed edits and wait for approval before changing files. Use when preparing or verifying a release, when asked to check the latest version, or when the user says \"docs drift\", \"check the docs\", \"are the docs up to date\", \"docs audit\", \"did the docs keep up\", or whether documentation matches released or unreleased changes. Complements pre-release-review, which checks changelog claims against code; this skill checks changelog claims against docs.","gtapps\u002Fhermitd","gtapps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16778396?v=4","01M6HTX8TNTPQN3NXRVA63VHTH","01M6HTX8Z23S531ZPPA5DKJVD0",84,"MIT","https:\u002F\u002Fgithub.com\u002Fgtapps\u002Fhermitd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdocs-drift\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"docs","docs drift","drift","when","review","for","claims","which","with","keep","wait","either","files","up","version","use","snapshot","check","monorepo","wait for","docs audit","audit","changelog","release","code","plugin","documentation","2026-11-10 10:12:30",false,"---\nname: docs-drift\ndescription: Documentation-drift audit for this plugin monorepo. Audit either each scoped plugin's unreleased changelog claims or its latest shipped release from the previous reachable plugin-name--v* tag, then verify that plugin READMEs, docs, CLAUDE.md or AGENTS.md files, and root documentation tell the truth for the matching snapshot. Report meaningful contradictions with concrete proposed edits and wait for approval before changing files. Use when preparing or verifying a release, when asked to check the latest version, or when the user says \"docs drift\", \"check the docs\", \"are the docs up to date\", \"docs audit\", \"did the docs keep up\", or whether documentation matches released or unreleased changes. Complements pre-release-review, which checks changelog claims against code; this skill checks changelog claims against docs.\n---\n\n# Docs Drift\n\nVerify that documentation tells the truth about either the changes about to\nship or the latest version already shipped.\n\nKeep the audit read-only. Do not edit, commit, tag, push, publish, or release\nuntil the user explicitly approves specific findings. Even after approval,\nnever commit or publish from this skill.\n\n## Invocation\n\n- `$docs-drift` or `$docs-drift unreleased` — audit every plugin with a\n  non-empty `[Unreleased]` section.\n- `$docs-drift \u003Cplugin-slug>` — audit that plugin's unreleased changes.\n- `$docs-drift latest` — audit the latest reachable release of every tagged\n  plugin.\n- `$docs-drift latest \u003Cplugin-slug>` — audit only that plugin's latest release.\n\nUse unreleased mode by default. Treat \"latest version\", \"latest release\", or\nequivalent wording as latest-release mode.\n\nTypical release order, when the sibling skills are installed:\n\n`$release-status` → `$pre-release-review` → `$docs-drift` → `$release`\n\n## Step 1 — Scope plugins and snapshots\n\nNever mix released and unreleased windows in one claim set.\n\n### Unreleased mode\n\nIdentify plugins whose `[Unreleased]` section contains non-blank content:\n\n```bash\nfor p in plugins\u002F*\u002FCHANGELOG.md; do\n  slug=$(basename \"$(dirname \"$p\")\")\n  awk '\u002F^## \\[Unreleased\\]\u002F{f=1; next} \u002F^## \\[\u002F{f=0} f && NF' \"$p\" | rg -q '.' \\\n    && echo \"$slug\"\ndone\n```\n\nIf the user named a plugin, limit scope to that slug after verifying it exists\nand has unreleased content. If nothing is in scope, stop with:\n\n`No unreleased changes in any plugin — nothing to drift-check.`\n\nUse the working tree as the documentation snapshot. Keep incidentally noticed\nolder drift separate as pre-existing debt.\n\n### Latest-release mode\n\nStart from all `plugins\u002F*\u002FCHANGELOG.md` slugs, or only the user-named slug.\nResolve each plugin's refs independently:\n\n```bash\nEMPTY_TREE=$(git hash-object -t tree \u002Fdev\u002Fnull)\n\nfor p in plugins\u002F*\u002FCHANGELOG.md; do\n  slug=$(basename \"$(dirname \"$p\")\")\n  latest=$(git describe --tags --abbrev=0 --match \"${slug}--v*\" HEAD 2>\u002Fdev\u002Fnull || true)\n\n  if [ -z \"$latest\" ]; then\n    printf '%s\\n' \"$slug: skipped (no reachable release tag)\"\n    continue\n  fi\n\n  previous=$(git describe --tags --abbrev=0 --match \"${slug}--v*\" \"${latest}^\" 2>\u002Fdev\u002Fnull || true)\n  printf '%s\\n' \"$slug latest=$latest previous=${previous:-\u003Cempty-tree>}\"\ndone\n```\n\nUse only reachable `\u003Cslug>--v*` tags. Do not select an unreachable tag merely\nbecause its version sorts later. If a plugin has only one reachable tag, use\nthe empty tree as its previous snapshot. If every scoped plugin lacks a tag,\nstop with:\n\n`No reachable plugin release tags — nothing to latest-release drift-check.`\n\nFor each plugin, use:\n\n- claim window: `\u003Cprevious-tag>..\u003Clatest-tag>`, or empty tree to latest tag;\n- changelog claims: the exact `## [\u003Clatest-version>]` section at the latest tag;\n- documentation snapshot: the repository exactly at that plugin's latest tag.\n\nLater commits and working-tree changes are not release claims in this mode.\nDifferent plugins may have different latest-tag snapshots; preserve that\nmapping throughout the audit.\n\n## Step 2 — Extract doc-checkable claims\n\nIn unreleased mode, read only each scoped plugin's working-tree `[Unreleased]`\nsection.\n\nIn latest-release mode, derive the version from `\u003Cslug>--v\u003Cversion>` and read\nthe matching changelog section from the tagged snapshot:\n\n```bash\nversion=${latest##*--v}\ngit show \"$latest:plugins\u002F$slug\u002FCHANGELOG.md\" | awk -v ver=\"$version\" '\n  index($0, \"## [\" ver \"]\") == 1 {f=1; next}\n  \u002F^## \\[\u002F && f {exit}\n  f\n'\n```\n\nAlso inspect the plugin-scoped release diff to catch doc-checkable\nconsumer-visible changes that a changelog bullet may group:\n\n```bash\nrelease_diff_base=${previous:-$EMPTY_TREE}\ngit diff \"$release_diff_base\" \"$latest\" -- \"plugins\u002F$slug\u002F\"\n```\n\nUse that diff only in latest-release mode and only for claim discovery; this\nskill does not replace changelog-versus-code review.\n\nTurn each claim into zero or more checks:\n\n- **Removal or rename** — a skill, command, script, hook, config key, doc file,\n  or CLI changed identity.\n- **New operator-visible surface** — a new skill, command, config block, hook,\n  CLI, or channel behavior should appear where siblings are enumerated.\n- **Changed default or behavior** — documentation may still state the previous\n  default or behavior. Treat this as the highest-severity class.\n- **Count or version claim** — a hand-written number or version marker may\n  still contain the old value.\n- **Promised documentation** — a cited file or anchor must exist and cover what\n  the changelog promises.\n\nMark pure internal fixes, refactors, and test-only changes as `no doc surface`.\nDo not manufacture a finding for every bullet.\n\n## Step 3 — Sweep the matching documentation\n\nFor each scoped plugin, consider the files that exist in its selected snapshot:\n\n- `plugins\u002F\u003Cslug>\u002FREADME.md`\n- `plugins\u002F\u003Cslug>\u002Fdocs\u002F*.md`\n- `plugins\u002F\u003Cslug>\u002FCLAUDE.md`\n- `plugins\u002F\u003Cslug>\u002FAGENTS.md`\n- top-level plugin extras such as `SAFETY.md`, `DOCKER.md`, or\n  `CONTRIBUTING.md`\n\nAlso check relevant root documentation:\n\n- root `README.md`\n- root `CLAUDE.md`\n- root `AGENTS.md`\n- root documentation extras relevant to a claim\n\nWork claim-first, not file-first:\n\n- **Unreleased:** use `rg -n` against the working tree. Sweep root files once\n  against the union of all claims.\n- **Latest release:** use `git grep -n \u003Cpattern> \"$latest\" -- \u003Cpaths>` and\n  `git show \"$latest:\u003Cpath>\"`. Sweep root files at each plugin's own latest-tag\n  snapshot. Deduplicate identical root findings in the report without losing\n  the plugin\u002Ftag evidence.\n\nNever silently substitute current documentation for a released snapshot.\n\nWhen more than two plugins are in scope and agent delegation is available,\ndelegate one plugin audit per worker. Give each worker that plugin's claims,\nmode, and snapshot ref, and require:\n\n`snapshot:file:line — contradicted claim — current text — suggested fix`\n\nKeep the root-file sweep in the main session because it needs cross-plugin\ndeduplication. Respect the available agent-slot limit and use additional waves\nif needed. If delegation is unavailable, perform the checks sequentially.\n\nIn latest-release mode, re-check each snapshot finding against the current\nworking tree:\n\n- If it is still stale, propose an edit to the current file.\n- If it is already corrected, report it under `Fixed after release` with no\n  proposed edit.\n- If the file no longer exists, explain its replacement or removal and do not\n  propose recreating it without evidence.\n\n## Step 4 — Judge meaningfulness\n\nPropose an edit only when a reader would be factually misled:\n\n- **Meaningful:** references a removed or renamed surface; states an old\n  default or behavior; gives a wrong count or version; omits a new surface from\n  a sibling enumeration; or promises documentation that does not exist or does\n  not cover the claim.\n- **Not meaningful:** tone, formatting, absent marketing coverage, missing\n  documentation for internal fixes, or changelog accuracy that\n  `$pre-release-review` owns.\n- **Borderline:** reader impact is unclear. Report it separately with a\n  one-line rationale and no proposed edit.\n\nThis marketplace ships as a research preview. Removed operator surfaces are\ndeleted from documentation. Do not propose a Legacy section, leftover config\nkeys in examples, \"legacy configuration\" labels, or dual current\u002Fold\ndescriptions. State the present surface only.\n\nDo not pad findings.\n\n## Step 5 — Report and wait for approval\n\nUse this shape:\n\n```text\n# Docs Drift — \u003Cdate>\n\n## Scope\nMode: \u003Cunreleased | latest release>\nIn scope: \u003Cslugs with snapshot refs>\nSkipped: \u003Cslugs and reasons>\nClaim windows: \u003C[Unreleased] | previous-tag..latest-tag per plugin>\nDocumentation snapshots: \u003Cworking tree | latest tag per plugin>\n\n## Findings\n### \u003Cn>. \u003Cslug> — \u003Cmisleading | stale-reference | missing-doc>\n- Claim: \u003Cabbreviated claim and changelog\u002Fdiff evidence>\n- Drift: \u003Csnapshot>:\u003Cdoc file:line> — currently says: \"\u003Cexcerpt>\"\n- Current tree: \u003Cstill stale | changed | file removed>\n- Proposed edit: \u003Cexact replacement text, or \"add section X covering Y\">\n\n## Fixed after release (no edit proposed)\n- \u003Csnapshot>:\u003Cfile:line> — \u003Cwhat was stale and where it is now corrected>\n\n## Borderline (no edit proposed)\n- \u003Csnapshot>:\u003Cfile:line> — \u003Cone-line rationale>\n\n## No doc surface\n- \u003Cbriefly grouped internal or test-only claims>\n\n## Pre-existing drift (not this window)\n- \u003Canything noticed outside the selected claim window>\n\n## Verdict\n\u003CN> actionable findings across \u003CM> current files | Docs are clean for this window.\n```\n\nAsk which actionable findings to apply: all, selected finding numbers, or none.\nThe audit request itself is not approval to edit.\n\nAfter the user approves:\n\n1. Apply only the approved edits to the current working tree with `apply_patch`.\n   Never edit a tag.\n2. Match each document's existing style. Keep edits succinct: prefer one\n   sentence or one table-cell correction, and do not restate a full policy when\n   its established term or canonical link is enough. Delete a removed surface;\n   do not relabel it as leftover, compatibility, or legacy support.\n3. Re-read the changed passages and run `git diff --check`.\n4. Do not add a changelog entry for documentation-only edits; repository\n   guidance explicitly excludes them.\n5. Report the uncommitted files and verification. Never commit, push, tag,\n   publish, or release from this skill.\n","# Docs Drift\n\nVerify that documentation tells the truth about either the changes about to\nship or the latest version already shipped.\n\nKeep the audit read-only. Do not edit, commit, tag, push, publish, or release\nuntil the user explicitly approves specific findings. Even after approval,\nnever commit or publish from this skill.\n\n## Invocation\n\n- `$docs-drift` or `$docs-drift unreleased` — audit every plugin with a\n  non-empty `[Unreleased]` section.\n- `$docs-drift \u003Cplugin-slug>` — audit that plugin's unreleased changes.\n- `$docs-drift latest` — audit the latest reachable release of every tagged\n  plugin.\n- `$docs-drift latest \u003Cplugin-slug>` — audit only that plugin's latest release.\n\nUse unreleased mode by default. Treat \"latest version\", \"latest release\", or\nequivalent wording as latest-release mode.\n\nTypical release order, when the sibling skills are installed:\n\n`$release-status` → `$pre-release-review` → `$docs-drift` → `$release`\n\n## Step 1 — Scope plugins and snapshots\n\nNever mix released and unreleased windows in one claim set.\n\n### Unreleased mode\n\nIdentify plugins whose `[Unreleased]` section contains non-blank content:\n\n```bash\nfor p in plugins\u002F*\u002FCHANGELOG.md; do\n  slug=$(basename \"$(dirname \"$p\")\")\n  awk '\u002F^## \\[Unreleased\\]\u002F{f=1; next} \u002F^## \\[\u002F{f=0} f && NF' \"$p\" | rg -q '.' \\\n    && echo \"$slug\"\ndone\n```\n\nIf the user named a plugin, limit scope to that slug after verifying it exists\nand has unreleased content. If nothing is in scope, stop with:\n\n`No unreleased changes in any plugin — nothing to drift-check.`\n\nUse the working tree as the documentation snapshot. Keep incidentally noticed\nolder drift separate as pre-existing debt.\n\n### Latest-release mode\n\nStart from all `plugins\u002F*\u002FCHANGELOG.md` slugs, or only the user-named slug.\nResolve each plugin's refs independently:\n\n```bash\nEMPTY_TREE=$(git hash-object -t tree \u002Fdev\u002Fnull)\n\nfor p in plugins\u002F*\u002FCHANGELOG.md; do\n  slug=$(basename \"$(dirname \"$p\")\")\n  latest=$(git describe --tags --abbrev=0 --match \"${slug}--v*\" HEAD 2>\u002Fdev\u002Fnull || true)\n\n  if [ -z \"$latest\" ]; then\n    printf '%s\\n' \"$slug: skipped (no reachable release tag)\"\n    continue\n  fi\n\n  previous=$(git describe --tags --abbrev=0 --match \"${slug}--v*\" \"${latest}^\" 2>\u002Fdev\u002Fnull || true)\n  printf '%s\\n' \"$slug latest=$latest previous=${previous:-\u003Cempty-tree>}\"\ndone\n```\n\nUse only reachable `\u003Cslug>--v*` tags. Do not select an unreachable tag merely\nbecause its version sorts later. If a plugin has only one reachable tag, use\nthe empty tree as its previous snapshot. If every scoped plugin lacks a tag,\nstop with:\n\n`No reachable plugin release tags — nothing to latest-release drift-check.`\n\nFor each plugin, use:\n\n- claim window: `\u003Cprevious-tag>..\u003Clatest-tag>`, or empty tree to latest tag;\n- changelog claims: the exact `## [\u003Clatest-version>]` section at the latest tag;\n- documentation snapshot: the repository exactly at that plugin's latest tag.\n\nLater commits and working-tree changes are not release claims in this mode.\nDifferent plugins may have different latest-tag snapshots; preserve that\nmapping throughout the audit.\n\n## Step 2 — Extract doc-checkable claims\n\nIn unreleased mode, read only each scoped plugin's working-tree `[Unreleased]`\nsection.\n\nIn latest-release mode, derive the version from `\u003Cslug>--v\u003Cversion>` and read\nthe matching changelog section from the tagged snapshot:\n\n```bash\nversion=${latest##*--v}\ngit show \"$latest:plugins\u002F$slug\u002FCHANGELOG.md\" | awk -v ver=\"$version\" '\n  index($0, \"## [\" ver \"]\") == 1 {f=1; next}\n  \u002F^## \\[\u002F && f {exit}\n  f\n'\n```\n\nAlso inspect the plugin-scoped release diff to catch doc-checkable\nconsumer-visible changes that a changelog bullet may group:\n\n```bash\nrelease_diff_base=${previous:-$EMPTY_TREE}\ngit diff \"$release_diff_base\" \"$latest\" -- \"plugins\u002F$slug\u002F\"\n```\n\nUse that diff only in latest-release mode and only for claim discovery; this\nskill does not replace changelog-versus-code review.\n\nTurn each claim into zero or more checks:\n\n- **Removal or rename** — a skill, command, script, hook, config key, doc file,\n  or CLI changed identity.\n- **New operator-visible surface** — a new skill, command, config block, hook,\n  CLI, or channel behavior should appear where siblings are enumerated.\n- **Changed default or behavior** — documentation may still state the previous\n  default or behavior. Treat this as the highest-severity class.\n- **Count or version claim** — a hand-written number or version marker may\n  still contain the old value.\n- **Promised documentation** — a cited file or anchor must exist and cover what\n  the changelog promises.\n\nMark pure internal fixes, refactors, and test-only changes as `no doc surface`.\nDo not manufacture a finding for every bullet.\n\n## Step 3 — Sweep the matching documentation\n\nFor each scoped plugin, consider the files that exist in its selected snapshot:\n\n- `plugins\u002F\u003Cslug>\u002FREADME.md`\n- `plugins\u002F\u003Cslug>\u002Fdocs\u002F*.md`\n- `plugins\u002F\u003Cslug>\u002FCLAUDE.md`\n- `plugins\u002F\u003Cslug>\u002FAGENTS.md`\n- top-level plugin extras such as `SAFETY.md`, `DOCKER.md`, or\n  `CONTRIBUTING.md`\n\nAlso check relevant root documentation:\n\n- root `README.md`\n- root `CLAUDE.md`\n- root `AGENTS.md`\n- root documentation extras relevant to a claim\n\nWork claim-first, not file-first:\n\n- **Unreleased:** use `rg -n` against the working tree. Sweep root files once\n  against the union of all claims.\n- **Latest release:** use `git grep -n \u003Cpattern> \"$latest\" -- \u003Cpaths>` and\n  `git show \"$latest:\u003Cpath>\"`. Sweep root files at each plugin's own latest-tag\n  snapshot. Deduplicate identical root findings in the report without losing\n  the plugin\u002Ftag evidence.\n\nNever silently substitute current documentation for a released snapshot.\n\nWhen more than two plugins are in scope and agent delegation is available,\ndelegate one plugin audit per worker. Give each worker that plugin's claims,\nmode, and snapshot ref, and require:\n\n`snapshot:file:line — contradicted claim — current text — suggested fix`\n\nKeep the root-file sweep in the main session because it needs cross-plugin\ndeduplication. Respect the available agent-slot limit and use additional waves\nif needed. If delegation is unavailable, perform the checks sequentially.\n\nIn latest-release mode, re-check each snapshot finding against the current\nworking tree:\n\n- If it is still stale, propose an edit to the current file.\n- If it is already corrected, report it under `Fixed after release` with no\n  proposed edit.\n- If the file no longer exists, explain its replacement or removal and do not\n  propose recreating it without evidence.\n\n## Step 4 — Judge meaningfulness\n\nPropose an edit only when a reader would be factually misled:\n\n- **Meaningful:** references a removed or renamed surface; states an old\n  default or behavior; gives a wrong count or version; omits a new surface from\n  a sibling enumeration; or promises documentation that does not exist or does\n  not cover the claim.\n- **Not meaningful:** tone, formatting, absent marketing coverage, missing\n  documentation for internal fixes, or changelog accuracy that\n  `$pre-release-review` owns.\n- **Borderline:** reader impact is unclear. Report it separately with a\n  one-line rationale and no proposed edit.\n\nThis marketplace ships as a research preview. Removed operator surfaces are\ndeleted from documentation. Do not propose a Legacy section, leftover config\nkeys in examples, \"legacy configuration\" labels, or dual current\u002Fold\ndescriptions. State the present surface only.\n\nDo not pad findings.\n\n## Step 5 — Report and wait for approval\n\nUse this shape:\n\n```text\n# Docs Drift — \u003Cdate>\n\n## Scope\nMode: \u003Cunreleased | latest release>\nIn scope: \u003Cslugs with snapshot refs>\nSkipped: \u003Cslugs and reasons>\nClaim windows: \u003C[Unreleased] | previous-tag..latest-tag per plugin>\nDocumentation snapshots: \u003Cworking tree | latest tag per plugin>\n\n## Findings\n### \u003Cn>. \u003Cslug> — \u003Cmisleading | stale-reference | missing-doc>\n- Claim: \u003Cabbreviated claim and changelog\u002Fdiff evidence>\n- Drift: \u003Csnapshot>:\u003Cdoc file:line> — currently says: \"\u003Cexcerpt>\"\n- Current tree: \u003Cstill stale | changed | file removed>\n- Proposed edit: \u003Cexact replacement text, or \"add section X covering Y\">\n\n## Fixed after release (no edit proposed)\n- \u003Csnapshot>:\u003Cfile:line> — \u003Cwhat was stale and where it is now corrected>\n\n## Borderline (no edit proposed)\n- \u003Csnapshot>:\u003Cfile:line> — \u003Cone-line rationale>\n\n## No doc surface\n- \u003Cbriefly grouped internal or test-only claims>\n\n## Pre-existing drift (not this window)\n- \u003Canything noticed outside the selected claim window>\n\n## Verdict\n\u003CN> actionable findings across \u003CM> current files | Docs are clean for this window.\n```\n\nAsk which actionable findings to apply: all, selected finding numbers, or none.\nThe audit request itself is not approval to edit.\n\nAfter the user approves:\n\n1. Apply only the approved edits to the current working tree with `apply_patch`.\n   Never edit a tag.\n2. Match each document's existing style. Keep edits succinct: prefer one\n   sentence or one table-cell correction, and do not restate a full policy when\n   its established term or canonical link is enough. Delete a removed surface;\n   do not relabel it as leftover, compatibility, or legacy support.\n3. Re-read the changed passages and run `git diff --check`.\n4. Do not add a changelog entry for documentation-only edits; repository\n   guidance explicitly excludes them.\n5. Report the uncommitted files and verification. Never commit, push, tag,\n   publish, or release from this skill.\n",{"name":5,"description":7},"main","79e254360ba999b70a827541bbcfd2d4cc525992",".agents\u002Fskills\u002Fdocs-drift",16,"https:\u002F\u002Fgithub.com\u002Fgtapps\u002Fhermitd","https:\u002F\u002Fhermitd.dev","https:\u002F\u002Fgithub.com\u002Fgtapps","Software engineer from Portugal.\r\nBuilding and deploying agents for real companies.","2026-11-12 00:14:57",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add gtapps\u002Fhermitd --skill docs-drift",{"tool":65,"command":66},"bunx","bunx skills add gtapps\u002Fhermitd --skill docs-drift",{"tool":68,"command":69},"pnpm","pnpm dlx skills add gtapps\u002Fhermitd --skill docs-drift","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgtapps\u002Fhermitd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdocs-drift\u002FSKILL.md",true,[73],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"agents\u002Fopenai.yaml","REFERENCE","参考文档",274,"https:\u002F\u002Fgithub.com\u002Fgtapps\u002Fhermitd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdocs-drift\u002Fagents\u002Fopenai.yaml",[80,94,107,132,148,157],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":45},"01M718AB18DTYHVGXA6VF1VVR2","dream","Nightly memory maintenance from transcript ground truth. Verifies, enriches and tidies auto-memory and topic pages with snapshot validation and undo. Also handles 'undo the dream'.","https:\u002F\u002Fgithub.com\u002Fgtapps\u002Fhermitd\u002Fblob\u002Fmain\u002Fplugins\u002Fhermitd\u002Fskills\u002Fdream\u002FSKILL.md",[],[82,26,87,88,89,34,90,91,92,93],"maintenance","memory","validation","pages","auto","memory maintenance","transcript",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":45},"01M6HVD4WX8RB5EKH49HM66M8X","when-done-switch-to","Arm a deferred model or effort switch. Use for \"when done switch to\", \"after this drop to sonnet\", or \"switch model when idle\".","https:\u002F\u002Fgithub.com\u002Fgtapps\u002Fhermitd\u002Fblob\u002Fmain\u002Fplugins\u002Fhermitd\u002Fskills\u002Fwhen-done-switch-to\u002FSKILL.md",[],[21,101,102,103,23,104,33,105,106],"done","switch","when done switch to","model","drop","sonnet",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":45},"01M6HVD0ZA2Q1RD7CA0X8VWF3T","weekly-review","Generate the weekly review report for the current ISO week. Writes to .hermit\u002Fcompiled\u002Freview-weekly-YYYY-Www.md (dev-facing detail) and sends a plain-language channel summary (Delivered \u002F Decisions \u002F Waiting on you \u002F Spend). Runs every Sunday at 23:00 via routine.","https:\u002F\u002Fgithub.com\u002Fgtapps\u002Fhermitd\u002Fblob\u002Fmain\u002Fplugins\u002Fhermitd\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[114,22,115,116,117,118,119,120,121,122,123,124,125,126,127,23,128,129,130,131],"weekly review","weekly","hermit","plain","routine","channel","summary","report","at","generate","via","decisions","you","detail","iso","review report","dev","plain-language",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":45},"01M6HVCW8PHZXSPYAZQBZXB9DX","watch","Background events via the config watch monitor or ad-hoc Monitor tool. Quiet watches cost zero tokens.","https:\u002F\u002Fgithub.com\u002Fgtapps\u002Fhermitd\u002Fblob\u002Fmain\u002Fplugins\u002Fhermitd\u002Fskills\u002Fwatch\u002FSKILL.md",[],[134,139,140,141,142,143,144,145,146,124,147],"monitor","ZeRO","tokens","tool","cost","ad","config","background","events",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":45},"01M6HVCRMG53K3Y63WAH59YVFJ","watch-activate","Activate the config watch monitor.","https:\u002F\u002Fgithub.com\u002Fgtapps\u002Fhermitd\u002Fblob\u002Fmain\u002Fplugins\u002Fhermitd\u002Fskills\u002Fwatch-activate\u002FSKILL.md",[],[134,155,156,139,145],"activate","watch activate",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":168,"publishedAt":45},"01M6HVCK6782RD4D9ADQY0ENKD","voice-notes","Transcribe and respond to voice notes. Activates when any channel message carries an audio attachment, or when asked to transcribe an inbound voice message.","https:\u002F\u002Fgithub.com\u002Fgtapps\u002Fhermitd\u002Fblob\u002Fmain\u002Fplugins\u002Fhermitd\u002Fskills\u002Fvoice-notes\u002FSKILL.md",[163],{"categoryNo":164,"categoryName":165,"taxonomyType":166,"taxonomyTypeDesc":167},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[169,170,171,172,173,174,175,176,177,178,116,21,179,180,181,182,183,184,126,31],"notes","voice","voice notes","SET","Audio","transcribe","operator","understand","transcription","my","read","message","can","telegram","channel message","discord"]