[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C0WAGQESSBP565CDCN9MFE":3,"skill-same:01M7C0WAGQESSBP565CDCN9MFE":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7C0WAGQESSBP565CDCN9MFE","docs-update",null,"Generate or update project documentation verified against the codebase — use when docs are missing, stale, or need an accuracy audit","zak-keown\u002Fmoe","zak-keown","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F320717241?v=4","01M7BZFXME0NW6TQX0H7AZM2KS","01M7BZFXN32VR0JN5AATRD53H4",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002F.claude-plugin\u002Fskills\u002Fdocs-update\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: docs-update\ndescription: >-\n  Generate or update project documentation verified against the codebase —\n  use when docs are missing, stale, or need an accuracy audit\nargument-hint: \"[--only readme,api,...] [--force] [--verify-only]\"\n---\n\n# docs-update\n\n## Overview\n\nGenerates or updates a project's core docs — README, ARCHITECTURE, API,\nCONTRIBUTING, CHANGELOG — and can instead audit existing docs for drift\nagainst the codebase without touching a file. The core principle: one\nsubagent per doc type, dispatched in parallel, and every subagent reads the\nactual code before writing a word. Nothing is filled in from a template with\nplausible-sounding prose; every path, command, and signature it documents was\nlooked up in this run.\n\n## Flags\n\nParse `$ARGUMENTS` as a plain string. A flag is active only when its literal\ntoken appears in it — no abbreviation, no inference from context.\n\n- `--only \u003Ctypes>` — comma-separated, drawn from `readme`, `architecture`,\n  `api`, `contributing`, `changelog`. Read the token immediately following\n  `--only`, split on commas, trim whitespace. Any name outside that set is a\n  hard stop: report the offending name and the full valid set, and do not\n  run. When present, `--only` replaces relevance discovery entirely — the\n  named types are dispatched regardless of what discovery would have found.\n- `--force` — overwrite every processed doc regardless of marker state.\n- `--verify-only` — audit mode. No doc file is written; the run produces\n  `DOCS-VERIFY-REPORT.md` instead.\n- Both present — `--force` wins: the run generates\u002Foverwrites and produces no\n  verify report. `--force` means \"write now\"; pairing it with an audit-only\n  flag is contradictory, and the destructive flag has to be the one that\n  wins, or a user who forgot they combined the two loses data silently.\n\n## Relevance discovery\n\nBefore dispatching anything, the coordinator itself — no subagent — globs and\nreads the project to decide which doc types apply. This runs even when\n`--only` is present, so its result can still be reported, but `--only`\noverrides the outcome.\n\n- **readme, contributing** — always relevant.\n- **architecture** — relevant when a `packages\u002F` directory exists, OR when 10\n  or more top-level directories each contain at least one source file.\n- **api** — relevant when a repo-wide grep finds any of: HTTP route handlers\n  (`app.get`, `app.post`, `router.`, `@Get`, `@Post`, `@Controller`), CLI\n  command definitions (`commander`, `yargs`, `.command(`), or an exported\n  public API surface (`export function`, `export class`, `export const`,\n  `module.exports`).\n- **changelog** — relevant only when `CHANGELOG.md` already exists AND\n  contains at least one date-formatted entry. Never relevant for a project\n  with no changelog; this type has no from-scratch generation mode — see\n  `doc-types\u002Fchangelog.md`.\n\nSkip every type that fails its check. Name the skipped types and the reason\nin the final report — dropping one silently is a red flag, not a\nsimplification.\n\n## The marker\n\nA doc this skill generates or regenerates opens with a stamped HTML comment,\nalways its first line, before any heading or content. Its shape: `\u003C!-- `,\nthen the fixed prefix `moe:` glued directly — no space — to this skill's own\ndirectory name, `docs-update`, then a space, `generated=\"YYYY-MM-DD\"`, a\nspace, `type=\"\u003Ctype>\"`, a space, and the closing `-->`. `\u003Ctype>` is whichever\nof the five type identifiers that agent is writing.\n\nThe marker is the entire preservation protocol — no other metadata, and no\nsection-level partial markers in this version. (The design spec's open\nquestions flag section-level markers as a possible later addition; for now\nthis skill supports only whole-file generation and whole-file skip.)\n\n| Existing doc? | Has marker? | Default behavior | With `--force` |\n|---|---|---|---|\n| No | — | Generate, add marker | Generate, add marker |\n| Yes | Yes | Regenerate, refresh the `generated` date | Regenerate, refresh the `generated` date |\n| Yes | No | **Skip. Report drift.** | Overwrite, add marker |\n\nAn unmarked existing doc, left alone by default, is still read: the\ndispatched agent compares it against the codebase and reports references to\nfunctions, files, or commands that no longer exist; setup steps naming\nmissing dependencies or wrong versions; and code examples that would not\ncompile or run. These land in the final report as drift findings, never as\nfile edits — the user decides whether to hand the file to this skill (add\nthe marker, or re-run with `--force`) or fix it by hand.\n\n## Subagent dispatch\n\nOne `general-purpose` agent per relevant doc type (after `--only` and\nrelevance discovery are applied), dispatched with multiple Agent calls in a\nsingle response so they run in parallel. If parallel dispatch is unavailable\n— session policy, runtime limits, a harness without it — dispatch the same\nagents serially, in the order `readme, architecture, api, contributing,\nchangelog`. The output is identical either way; only wall clock changes.\n\nBefore dispatching, the coordinator resolves the relevant templates relative to\nthis loaded document — [skills\u002Fdocs-update\u002Fdoc-types\u002Freadme.md](doc-types\u002Freadme.md),\n[skills\u002Fdocs-update\u002Fdoc-types\u002Farchitecture.md](doc-types\u002Farchitecture.md),\n[skills\u002Fdocs-update\u002Fdoc-types\u002Fapi.md](doc-types\u002Fapi.md),\n[skills\u002Fdocs-update\u002Fdoc-types\u002Fcontributing.md](doc-types\u002Fcontributing.md), or\n[skills\u002Fdocs-update\u002Fdoc-types\u002Fchangelog.md](doc-types\u002Fchangelog.md) — and reads each one plus\nthe project's existing doc file, if one exists. Each agent's prompt carries:\n\n- The full template text for its doc type.\n- The project root.\n- The existing doc's content, or a note that none exists.\n- The marker state for this run: `generate` (no doc), `regenerate` (doc +\n  marker), `skip-drift` (doc, no marker, no `--force`), or `force-overwrite`\n  (`--force` set, any prior state).\n\nEach agent's prompt also states two things plainly, regardless of what its\ntemplate already covers: verify every fact against the code in this run\n(open the file, grep the symbol) rather than trust memory or the existing\ndoc, and never invent a path, command, or signature that does not check out.\n\n**REQUIRED SUB-SKILL:** Every dispatched agent must invoke `write-clearly` before finalizing prose.\n\nA `skip-drift` agent still reads and reports; it just does not write the file\n— see the marker section above. In verify mode, every dispatched agent\nproduces findings only and writes nothing (below).\n\n## Verify mode\n\n`--verify-only`, with `--force` not set, skips writing entirely and audits\ninstead.\n\n1. Run relevance discovery and `--only` as normal, then drop any type whose\n   target file does not exist on disk — there is nothing to verify — and\n   record it in the final report as \"no doc to verify.\" This filter is\n   verify-mode-only, separate from the generate-mode relevance check above.\n2. Dispatch the same one-agent-per-type pattern. Each agent reads its doc and\n   the codebase, then reports findings as a YAML list matching its\n   template's \"Verify mode\" section: `type` (`stale_reference`,\n   `missing_coverage`, or `factual_error`), `file`, `anchor`, `actual`, and\n   `severity` (`high`, `medium`, or `low` — never `critical`; stale\n   documentation is never \"exploitable now or destroys data\").\n3. For each agent's findings, write a JSON array to\n   `.moe\u002Fdocs-verify\u002F\u003Ctype>.json` — the same four content fields plus\n   `severity`, dropping the template's `id` placeholder (the script assigns\n   real IDs).\n4. Once every dispatched agent has staged its findings, resolve\n   [skills\u002Fdocs-update\u002Fscripts\u002Fdocs-verify-report.mjs](scripts\u002Fdocs-verify-report.mjs) relative to\n   this loaded document and run:\n\n   ```bash\n   node \"\u003Cresolved-docs-verify-report.mjs>\" \\\n     --staging .moe\u002Fdocs-verify --out DOCS-VERIFY-REPORT.md\n   ```\n\n   It assigns `DV-###` IDs in severity order, builds the frontmatter, and\n   writes `DOCS-VERIFY-REPORT.md` at the project root — same frontmatter\n   shape, same severity ladder, same stable-ID principle as\n   `review-codebase`'s `CR-###` report, so `fix-review` can\n   consume it directly.\n\n## Final report\n\nAfter every dispatched agent completes, in either mode, summarize in the\nreply:\n\n- Which doc types were generated, regenerated, or left unmarked-and-skipped\n  — with the drift summary, per type, for the skipped ones.\n- Which doc types relevance discovery or `--only` excluded, and why.\n- In verify mode: which types had no doc to verify, and a pointer to\n  `DOCS-VERIFY-REPORT.md` with its finding counts by severity.\n- Any agent that errored or returned nothing usable, named explicitly —\n  never folded silently into \"docs updated.\"\n\n## Red flags\n\n- Writing a doc without first determining its marker state — that is how a\n  hand-written file gets silently clobbered.\n- Dispatching an agent for a doc type relevance discovery ruled out, with no\n  `--only` naming it.\n- A subagent's doc citing a path, command, or signature it did not look up\n  in this run.\n- Regenerating `CHANGELOG.md` wholesale instead of inserting only the\n  entries since the last dated entry, above the existing content.\n- A verify-mode run that writes to `README.md`, `ARCHITECTURE.md`, or any\n  target doc, instead of only staging findings.\n- A verify finding above `high` severity, or a `--force` run that produces\n  `DOCS-VERIFY-REPORT.md` instead of overwriting docs.\n- A final report that omits a doc type instead of naming it skipped and why.\n","# docs-update\n\n## Overview\n\nGenerates or updates a project's core docs — README, ARCHITECTURE, API,\nCONTRIBUTING, CHANGELOG — and can instead audit existing docs for drift\nagainst the codebase without touching a file. The core principle: one\nsubagent per doc type, dispatched in parallel, and every subagent reads the\nactual code before writing a word. Nothing is filled in from a template with\nplausible-sounding prose; every path, command, and signature it documents was\nlooked up in this run.\n\n## Flags\n\nParse `$ARGUMENTS` as a plain string. A flag is active only when its literal\ntoken appears in it — no abbreviation, no inference from context.\n\n- `--only \u003Ctypes>` — comma-separated, drawn from `readme`, `architecture`,\n  `api`, `contributing`, `changelog`. Read the token immediately following\n  `--only`, split on commas, trim whitespace. Any name outside that set is a\n  hard stop: report the offending name and the full valid set, and do not\n  run. When present, `--only` replaces relevance discovery entirely — the\n  named types are dispatched regardless of what discovery would have found.\n- `--force` — overwrite every processed doc regardless of marker state.\n- `--verify-only` — audit mode. No doc file is written; the run produces\n  `DOCS-VERIFY-REPORT.md` instead.\n- Both present — `--force` wins: the run generates\u002Foverwrites and produces no\n  verify report. `--force` means \"write now\"; pairing it with an audit-only\n  flag is contradictory, and the destructive flag has to be the one that\n  wins, or a user who forgot they combined the two loses data silently.\n\n## Relevance discovery\n\nBefore dispatching anything, the coordinator itself — no subagent — globs and\nreads the project to decide which doc types apply. This runs even when\n`--only` is present, so its result can still be reported, but `--only`\noverrides the outcome.\n\n- **readme, contributing** — always relevant.\n- **architecture** — relevant when a `packages\u002F` directory exists, OR when 10\n  or more top-level directories each contain at least one source file.\n- **api** — relevant when a repo-wide grep finds any of: HTTP route handlers\n  (`app.get`, `app.post`, `router.`, `@Get`, `@Post`, `@Controller`), CLI\n  command definitions (`commander`, `yargs`, `.command(`), or an exported\n  public API surface (`export function`, `export class`, `export const`,\n  `module.exports`).\n- **changelog** — relevant only when `CHANGELOG.md` already exists AND\n  contains at least one date-formatted entry. Never relevant for a project\n  with no changelog; this type has no from-scratch generation mode — see\n  `doc-types\u002Fchangelog.md`.\n\nSkip every type that fails its check. Name the skipped types and the reason\nin the final report — dropping one silently is a red flag, not a\nsimplification.\n\n## The marker\n\nA doc this skill generates or regenerates opens with a stamped HTML comment,\nalways its first line, before any heading or content. Its shape: `\u003C!-- `,\nthen the fixed prefix `moe:` glued directly — no space — to this skill's own\ndirectory name, `docs-update`, then a space, `generated=\"YYYY-MM-DD\"`, a\nspace, `type=\"\u003Ctype>\"`, a space, and the closing `-->`. `\u003Ctype>` is whichever\nof the five type identifiers that agent is writing.\n\nThe marker is the entire preservation protocol — no other metadata, and no\nsection-level partial markers in this version. (The design spec's open\nquestions flag section-level markers as a possible later addition; for now\nthis skill supports only whole-file generation and whole-file skip.)\n\n| Existing doc? | Has marker? | Default behavior | With `--force` |\n|---|---|---|---|\n| No | — | Generate, add marker | Generate, add marker |\n| Yes | Yes | Regenerate, refresh the `generated` date | Regenerate, refresh the `generated` date |\n| Yes | No | **Skip. Report drift.** | Overwrite, add marker |\n\nAn unmarked existing doc, left alone by default, is still read: the\ndispatched agent compares it against the codebase and reports references to\nfunctions, files, or commands that no longer exist; setup steps naming\nmissing dependencies or wrong versions; and code examples that would not\ncompile or run. These land in the final report as drift findings, never as\nfile edits — the user decides whether to hand the file to this skill (add\nthe marker, or re-run with `--force`) or fix it by hand.\n\n## Subagent dispatch\n\nOne `general-purpose` agent per relevant doc type (after `--only` and\nrelevance discovery are applied), dispatched with multiple Agent calls in a\nsingle response so they run in parallel. If parallel dispatch is unavailable\n— session policy, runtime limits, a harness without it — dispatch the same\nagents serially, in the order `readme, architecture, api, contributing,\nchangelog`. The output is identical either way; only wall clock changes.\n\nBefore dispatching, the coordinator resolves the relevant templates relative to\nthis loaded document — [skills\u002Fdocs-update\u002Fdoc-types\u002Freadme.md](doc-types\u002Freadme.md),\n[skills\u002Fdocs-update\u002Fdoc-types\u002Farchitecture.md](doc-types\u002Farchitecture.md),\n[skills\u002Fdocs-update\u002Fdoc-types\u002Fapi.md](doc-types\u002Fapi.md),\n[skills\u002Fdocs-update\u002Fdoc-types\u002Fcontributing.md](doc-types\u002Fcontributing.md), or\n[skills\u002Fdocs-update\u002Fdoc-types\u002Fchangelog.md](doc-types\u002Fchangelog.md) — and reads each one plus\nthe project's existing doc file, if one exists. Each agent's prompt carries:\n\n- The full template text for its doc type.\n- The project root.\n- The existing doc's content, or a note that none exists.\n- The marker state for this run: `generate` (no doc), `regenerate` (doc +\n  marker), `skip-drift` (doc, no marker, no `--force`), or `force-overwrite`\n  (`--force` set, any prior state).\n\nEach agent's prompt also states two things plainly, regardless of what its\ntemplate already covers: verify every fact against the code in this run\n(open the file, grep the symbol) rather than trust memory or the existing\ndoc, and never invent a path, command, or signature that does not check out.\n\n**REQUIRED SUB-SKILL:** Every dispatched agent must invoke `write-clearly` before finalizing prose.\n\nA `skip-drift` agent still reads and reports; it just does not write the file\n— see the marker section above. In verify mode, every dispatched agent\nproduces findings only and writes nothing (below).\n\n## Verify mode\n\n`--verify-only`, with `--force` not set, skips writing entirely and audits\ninstead.\n\n1. Run relevance discovery and `--only` as normal, then drop any type whose\n   target file does not exist on disk — there is nothing to verify — and\n   record it in the final report as \"no doc to verify.\" This filter is\n   verify-mode-only, separate from the generate-mode relevance check above.\n2. Dispatch the same one-agent-per-type pattern. Each agent reads its doc and\n   the codebase, then reports findings as a YAML list matching its\n   template's \"Verify mode\" section: `type` (`stale_reference`,\n   `missing_coverage`, or `factual_error`), `file`, `anchor`, `actual`, and\n   `severity` (`high`, `medium`, or `low` — never `critical`; stale\n   documentation is never \"exploitable now or destroys data\").\n3. For each agent's findings, write a JSON array to\n   `.moe\u002Fdocs-verify\u002F\u003Ctype>.json` — the same four content fields plus\n   `severity`, dropping the template's `id` placeholder (the script assigns\n   real IDs).\n4. Once every dispatched agent has staged its findings, resolve\n   [skills\u002Fdocs-update\u002Fscripts\u002Fdocs-verify-report.mjs](scripts\u002Fdocs-verify-report.mjs) relative to\n   this loaded document and run:\n\n   ```bash\n   node \"\u003Cresolved-docs-verify-report.mjs>\" \\\n     --staging .moe\u002Fdocs-verify --out DOCS-VERIFY-REPORT.md\n   ```\n\n   It assigns `DV-###` IDs in severity order, builds the frontmatter, and\n   writes `DOCS-VERIFY-REPORT.md` at the project root — same frontmatter\n   shape, same severity ladder, same stable-ID principle as\n   `review-codebase`'s `CR-###` report, so `fix-review` can\n   consume it directly.\n\n## Final report\n\nAfter every dispatched agent completes, in either mode, summarize in the\nreply:\n\n- Which doc types were generated, regenerated, or left unmarked-and-skipped\n  — with the drift summary, per type, for the skipped ones.\n- Which doc types relevance discovery or `--only` excluded, and why.\n- In verify mode: which types had no doc to verify, and a pointer to\n  `DOCS-VERIFY-REPORT.md` with its finding counts by severity.\n- Any agent that errored or returned nothing usable, named explicitly —\n  never folded silently into \"docs updated.\"\n\n## Red flags\n\n- Writing a doc without first determining its marker state — that is how a\n  hand-written file gets silently clobbered.\n- Dispatching an agent for a doc type relevance discovery ruled out, with no\n  `--only` naming it.\n- A subagent's doc citing a path, command, or signature it did not look up\n  in this run.\n- Regenerating `CHANGELOG.md` wholesale instead of inserting only the\n  entries since the last dated entry, above the existing content.\n- A verify-mode run that writes to `README.md`, `ARCHITECTURE.md`, or any\n  target doc, instead of only staging findings.\n- A verify finding above `high` severity, or a `--force` run that produces\n  `DOCS-VERIFY-REPORT.md` instead of overwriting docs.\n- A final report that omits a doc type instead of naming it skipped and why.\n",{"name":5,"description":7,"argument-hint":23},"[--only readme,api,...] [--force] [--verify-only]","main","728894f3f85fbd4e788f015ddfd72bb6155d5dd5","plugins\u002Fmoe\u002F.claude-plugin\u002Fskills\u002Fdocs-update",1,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe","https:\u002F\u002Fgithub.com\u002Fzak-keown","2026-09-05 06:29:06",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add zak-keown\u002Fmoe --skill docs-update",{"tool":37,"command":38},"bunx","bunx skills add zak-keown\u002Fmoe --skill docs-update",{"tool":40,"command":41},"pnpm","pnpm dlx skills add zak-keown\u002Fmoe --skill docs-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002F.claude-plugin\u002Fskills\u002Fdocs-update\u002FSKILL.md",true,[45,51,55,59,63,67],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"doc-types\u002Fapi.md","REFERENCE","参考文档",3405,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002F.claude-plugin\u002Fskills\u002Fdocs-update\u002Fdoc-types\u002Fapi.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"doc-types\u002Farchitecture.md",3317,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002F.claude-plugin\u002Fskills\u002Fdocs-update\u002Fdoc-types\u002Farchitecture.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"doc-types\u002Fchangelog.md",2899,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002F.claude-plugin\u002Fskills\u002Fdocs-update\u002Fdoc-types\u002Fchangelog.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"doc-types\u002Fcontributing.md",3108,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002F.claude-plugin\u002Fskills\u002Fdocs-update\u002Fdoc-types\u002Fcontributing.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"doc-types\u002Freadme.md",2369,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002F.claude-plugin\u002Fskills\u002Fdocs-update\u002Fdoc-types\u002Freadme.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fdocs-verify-report.mjs","SCRIPT","脚本",3111,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002F.claude-plugin\u002Fskills\u002Fdocs-update\u002Fscripts\u002Fdocs-verify-report.mjs",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7C1Z5362Y8NVRZ69HWP0ZD0","write-skill","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-skill\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7C1YZ9966WK9R6ZRPCGWF3G","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M7C1YMR4SJD7BPBBPXZCVGVH","write-clearly","Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-clearly\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M7C1YH9805YSM0N20VQAVSXF","windows-vm","Create, manage, or connect to a headless Windows 11 VM running in Docker with SSH access. Use when the user wants to spin up, stop, restart, or SSH into a Windows VM.","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwindows-vm\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M7C1YD87SCNEJ2C9B8HFR2NQ","verify-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating MRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fverify-completion\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":18},"01M7C1YARDEHT0TJ9BRG30ZCF4","using-moe","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fusing-moe\u002FSKILL.md",[],[]]