[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKHZJ753QQTYGS0RTBBJ35":3,"skill-same:01M6MKHZJ753QQTYGS0RTBBJ35":62},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":61},"01M6MKHZJ753QQTYGS0RTBBJ35","doctor",null,"Read-only diagnosis of the workspace, rules, markers, lease, watchman and deadline, with classified next actions; never repairs anything.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Forwa-mahmoud\u002Fnightshift\u002Fskills\u002Fdoctor\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31],"actions","workspace","Rules","read","never","only","next","diagnosis","markers","with","read-only","true","watchman","2026-11-10 10:12:30",false,"---\nname: doctor\ndescription: Read-only diagnosis of the workspace, rules, markers, lease, watchman and deadline, with classified next actions; never repairs anything.\nlicense: MIT\nmetadata:\n  internal: true\n---\n\nDiagnose the host-opened project **without changing anything**. Doctor is deeper than status: it\nexplains what Nightshift resolved and which failures that implies. It does not arm, stop, revive,\nrewrite, or delete.\n\nThe four state files and what each holds are in\n`$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Fshift\u002Fstate-map.md`. Report these as different categories; do not merge or move them.\n\nResolve the installed plugin root to an absolute `$NIGHTSHIFT_PLUGIN_ROOT` — `${CLAUDE_PLUGIN_ROOT}`\non Claude Code, `$PLUGIN_ROOT` on Codex when set, otherwise the absolute path this skill was\nattached from (`skills\u002Fdoctor\u002FSKILL.md`). Run every command below through\n`\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\"` — native Windows: `& \"$NIGHTSHIFT_PLUGIN_ROOT\\runtime\\windows\\ns.ps1\"`\nin the PowerShell tool, same verbs — which resolves the host and the workspace; `ns help` lists the\nverbs, and `ns bind` prints the six resolved facts (`TASK_ROOT`, `NIGHTSHIFT_WORKSPACE`, `NS`,\n`NIGHTSHIFT_PLUGIN_ROOT`, `HOST`, `SOURCE`); `$NS` below is that `NS`. Never a bare relative path: the working\ndirectory persists between calls. Each `$NS\u002F...` path below is where the current layout keeps that file;\n`ns path \u003Ckey>` prints where this workspace keeps it, and `ns path --list` names every key.\n\n## 1. Run the inspector\n\n```bash\n\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" doctor\n```\n\nPrint its report verbatim. Do not summarise away Facts, Warnings, or Actions, and do not re-derive\nanything it already resolved: the script uses the same workspace, work-mode, work-target, policy\nand ownership libraries as the hooks, and both implementations print the same lines.\n\nThe report answers, in its own words: where the workspace is and whether `.nightshift-link` is\nvalid; the schema version and whether it is current, legacy, malformed, or newer than this plugin;\nwork mode and work target; the punch-list and staged-work counts; each parking-lot or snag-log\nparagraph Archive can never file, by file and line; markers, session, process lease\nand watchman liveness; the deadline and whether it disagrees with the shift policy; an interrupted provisioning transaction; every\n`rules.json` knob it needs and the three native question-tool entries; a `resolved policy` block\nnaming every effective setting with its source (`built-in`, `rules`, `defaults`, `one-shift` or\n`exact-plan`) and expiry (`shift`, `permanent` or `-`); and a `preflight` fact naming which items\nneed an elevation category the resolved policy does not grant.\n\nStaged work is reported, never offered, while the punch list has open items. Doctor suggests\npromoting a draft or a parked Hunt order only when no `- [ ]` remains under `## Items` and no shift\nis armed — the same precedence Start applies. With open work, say what is staged and say plainly\nthat Start works the current list; do not read a count as an invitation to widen the approved\nscope, and never promote anything from this read-only skill.\n\nThe `work mode` fact is `repository` or `artifact`. When `$NS\u002Frun\u002Fwork-mode` is missing and Setup\nwould propose artifact, Doctor warns `work mode is unset; Setup would propose artifact` and offers\n`persist the proposed artifact mode with Setup; Doctor does not write work-mode`. When work-mode is\nunreadable it warns `work mode is malformed; treating the site as unusable until Setup rewrites it`,\nand when the target cannot be resolved it warns\n`work target could not be resolved; treating workspace as the code root`. When the record is\nmissing the resolver takes the workspace or its single immediate child repository.\nSkip a symlink or reparse child; it is not a nested checkout.\n\nIn artifact mode the report also carries `artifact receipts N` for files under `$NS\u002Freceipts\u002F`,\nand `latest artifact receipt` with the filename only of the most recently written receipt (no\ndirectory path). When receipts are enabled it reports `completion record per-item receipt` and,\nif ticked items have no model text, warns\n`N ticked items have no receipt text; each item completes through its receipt file`. Disabled\nreceipts are a fact only: `completion record none; the owner disabled receipts`. When the path exists but is not a real\ndirectory, it warns `artifact receipts path is not a usable directory` and offers to replace it\nso receipts can land; it does not also warn empty ticks for that path.\nCopies from Archive live in each shift's folder under the archive root,\n`$NS\u002Farchive\u002F\u003CYYYY-MM-DD>\u002Freceipts\u002F` by default, and do not replace the live files Doctor counts.\nMissing or empty receipts create no dated receipts folder.\n\n**Every Warning is a real finding — relay it, do not soften it.** A path that is not a usable file\nis a planted symlink where a marker should be, not an empty night; a malformed work mode is not a\nworking site; a failed clock-out is not a finished shift. Say what each one means for the owner\nand, when the report offers a `[confirm]` action for it, name that action.\n\nDoctor never writes the policy file, never runs the project's own tooling, and never prints\ncredentials, raw evidence, rule values, or the output of a command it did not run.\n\n## 2. Classify actions — do not execute them\n\nThe report tags every suggestion:\n\n- `[safe]` — mechanical leftover with no live session (for example a stale watchman pid file whose\n  process is already gone). Still do **not** apply it because Doctor was invoked; offer it.\n- `[confirm]` — owner decision (broken link, missing setup, leftover STOP while they still want\n  the night). During an **unattended active shift** (`$NS\u002Frun\u002F.shift-armed` and open boxes), report that\n  the recommendation should be parked with the default \"leave in place until morning\", but do not\n  write the parking lot or ask — the Doctor invocation remains byte-identical.\n- `[blocked]` — Nightshift cannot fix this here (non-resumable Codex id, malformed process lease,\n  missing host binary, unverified wedge). Say so. Never guess a session id or print\u002Fedit a lease\n  capability. For a stuck conversation or a fenced recorded session, name\n  `\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" stop-shift` — that pauses immediately without waiting for a Stop\n  event. Do not run it from Doctor.\n\nWhen the report says a terminal clock-out failed without releasing the shift, say whether the\nrecorded conversation can operate or whether a recovery worker still holds the lease; never tell\nthe owner to reopen a conversation that would stay blocked.\n\nInvoking Doctor alone must leave the tree byte-identical. Never perform a repair merely because\nDoctor was invoked.\n\nWhen cross-host continuity is relevant, summarize stand-down and revival from `$NS\u002Frun\u002Fshift-log.md`\n(no secrets), and run `continuity-handoff.sh fence-check` only when a duplicate worker or unfenced\nprior owner is suspected.\n\n## 3. After the report\n\nOffer the classified repairs after the report. If the owner explicitly asks to apply a `[safe]`\nleftover while no shift is armed, they are no longer in Doctor — follow stop\u002Fstart\u002Fsetup as those\nskills specify. Until that explicit ask, change nothing. During an unattended shift, the offer is\ninformational only: continue the active work without asking or writing state.\n\nTwo repairs the report names are separate owner actions, never Doctor's own:\n\n- The move into the current layout. On a workspace at an older state-version, or one holding a\n  state file at an earlier path, the `[confirm]` action names each file with its old and new path\n  and says that nothing is deleted; it is `[blocked]` while a shift is armed, a watchman is alive\n  or a lock is held. Relay it as printed. The owner previews it with\n  `\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" migrate-state` and makes it by running that again with\n  `--apply`. A future version is `[blocked]`: never downgrade a marker.\n- A local rule profile. Doctor may list the shipped examples with\n  `\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" apply-profile --list`\n  and preview one with `--profile \u003Cname> --mode fill` (or `--mode replace`). Preview is the\n  default; only `--apply` writes, and Invoking\n  Doctor never writes `rules.json`.\n\nA senior may run the read-only project inventory after the report:\n`\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" inventory`. It prints one table per\nworkspace package — package manager and lockfile, the scripts declared for test, lint, typecheck,\nbuild and format, the config files present, and each named tool as `declared`, `runnable` or\n`absent`. Those three words are the whole verdict; the report never calls a project misconfigured.\nIt writes and caches nothing, and Doctor never runs it — offer it, the way every other action here\nis offered.\n\nIf the owner then explicitly asks to **Export support bundle**, they are no longer in Doctor.\nRun\n`\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" export-support`.\nPrint its path, included sections, and omitted categories. Do not upload, attach, transmit, or open\nthe file. Invoking Doctor alone must not create `$NS\u002Fsupport\u002F`.\n","Diagnose the host-opened project **without changing anything**. Doctor is deeper than status: it\nexplains what Nightshift resolved and which failures that implies. It does not arm, stop, revive,\nrewrite, or delete.\n\nThe four state files and what each holds are in\n`$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Fshift\u002Fstate-map.md`. Report these as different categories; do not merge or move them.\n\nResolve the installed plugin root to an absolute `$NIGHTSHIFT_PLUGIN_ROOT` — `${CLAUDE_PLUGIN_ROOT}`\non Claude Code, `$PLUGIN_ROOT` on Codex when set, otherwise the absolute path this skill was\nattached from (`skills\u002Fdoctor\u002FSKILL.md`). Run every command below through\n`\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\"` — native Windows: `& \"$NIGHTSHIFT_PLUGIN_ROOT\\runtime\\windows\\ns.ps1\"`\nin the PowerShell tool, same verbs — which resolves the host and the workspace; `ns help` lists the\nverbs, and `ns bind` prints the six resolved facts (`TASK_ROOT`, `NIGHTSHIFT_WORKSPACE`, `NS`,\n`NIGHTSHIFT_PLUGIN_ROOT`, `HOST`, `SOURCE`); `$NS` below is that `NS`. Never a bare relative path: the working\ndirectory persists between calls. Each `$NS\u002F...` path below is where the current layout keeps that file;\n`ns path \u003Ckey>` prints where this workspace keeps it, and `ns path --list` names every key.\n\n## 1. Run the inspector\n\n```bash\n\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" doctor\n```\n\nPrint its report verbatim. Do not summarise away Facts, Warnings, or Actions, and do not re-derive\nanything it already resolved: the script uses the same workspace, work-mode, work-target, policy\nand ownership libraries as the hooks, and both implementations print the same lines.\n\nThe report answers, in its own words: where the workspace is and whether `.nightshift-link` is\nvalid; the schema version and whether it is current, legacy, malformed, or newer than this plugin;\nwork mode and work target; the punch-list and staged-work counts; each parking-lot or snag-log\nparagraph Archive can never file, by file and line; markers, session, process lease\nand watchman liveness; the deadline and whether it disagrees with the shift policy; an interrupted provisioning transaction; every\n`rules.json` knob it needs and the three native question-tool entries; a `resolved policy` block\nnaming every effective setting with its source (`built-in`, `rules`, `defaults`, `one-shift` or\n`exact-plan`) and expiry (`shift`, `permanent` or `-`); and a `preflight` fact naming which items\nneed an elevation category the resolved policy does not grant.\n\nStaged work is reported, never offered, while the punch list has open items. Doctor suggests\npromoting a draft or a parked Hunt order only when no `- [ ]` remains under `## Items` and no shift\nis armed — the same precedence Start applies. With open work, say what is staged and say plainly\nthat Start works the current list; do not read a count as an invitation to widen the approved\nscope, and never promote anything from this read-only skill.\n\nThe `work mode` fact is `repository` or `artifact`. When `$NS\u002Frun\u002Fwork-mode` is missing and Setup\nwould propose artifact, Doctor warns `work mode is unset; Setup would propose artifact` and offers\n`persist the proposed artifact mode with Setup; Doctor does not write work-mode`. When work-mode is\nunreadable it warns `work mode is malformed; treating the site as unusable until Setup rewrites it`,\nand when the target cannot be resolved it warns\n`work target could not be resolved; treating workspace as the code root`. When the record is\nmissing the resolver takes the workspace or its single immediate child repository.\nSkip a symlink or reparse child; it is not a nested checkout.\n\nIn artifact mode the report also carries `artifact receipts N` for files under `$NS\u002Freceipts\u002F`,\nand `latest artifact receipt` with the filename only of the most recently written receipt (no\ndirectory path). When receipts are enabled it reports `completion record per-item receipt` and,\nif ticked items have no model text, warns\n`N ticked items have no receipt text; each item completes through its receipt file`. Disabled\nreceipts are a fact only: `completion record none; the owner disabled receipts`. When the path exists but is not a real\ndirectory, it warns `artifact receipts path is not a usable directory` and offers to replace it\nso receipts can land; it does not also warn empty ticks for that path.\nCopies from Archive live in each shift's folder under the archive root,\n`$NS\u002Farchive\u002F\u003CYYYY-MM-DD>\u002Freceipts\u002F` by default, and do not replace the live files Doctor counts.\nMissing or empty receipts create no dated receipts folder.\n\n**Every Warning is a real finding — relay it, do not soften it.** A path that is not a usable file\nis a planted symlink where a marker should be, not an empty night; a malformed work mode is not a\nworking site; a failed clock-out is not a finished shift. Say what each one means for the owner\nand, when the report offers a `[confirm]` action for it, name that action.\n\nDoctor never writes the policy file, never runs the project's own tooling, and never prints\ncredentials, raw evidence, rule values, or the output of a command it did not run.\n\n## 2. Classify actions — do not execute them\n\nThe report tags every suggestion:\n\n- `[safe]` — mechanical leftover with no live session (for example a stale watchman pid file whose\n  process is already gone). Still do **not** apply it because Doctor was invoked; offer it.\n- `[confirm]` — owner decision (broken link, missing setup, leftover STOP while they still want\n  the night). During an **unattended active shift** (`$NS\u002Frun\u002F.shift-armed` and open boxes), report that\n  the recommendation should be parked with the default \"leave in place until morning\", but do not\n  write the parking lot or ask — the Doctor invocation remains byte-identical.\n- `[blocked]` — Nightshift cannot fix this here (non-resumable Codex id, malformed process lease,\n  missing host binary, unverified wedge). Say so. Never guess a session id or print\u002Fedit a lease\n  capability. For a stuck conversation or a fenced recorded session, name\n  `\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" stop-shift` — that pauses immediately without waiting for a Stop\n  event. Do not run it from Doctor.\n\nWhen the report says a terminal clock-out failed without releasing the shift, say whether the\nrecorded conversation can operate or whether a recovery worker still holds the lease; never tell\nthe owner to reopen a conversation that would stay blocked.\n\nInvoking Doctor alone must leave the tree byte-identical. Never perform a repair merely because\nDoctor was invoked.\n\nWhen cross-host continuity is relevant, summarize stand-down and revival from `$NS\u002Frun\u002Fshift-log.md`\n(no secrets), and run `continuity-handoff.sh fence-check` only when a duplicate worker or unfenced\nprior owner is suspected.\n\n## 3. After the report\n\nOffer the classified repairs after the report. If the owner explicitly asks to apply a `[safe]`\nleftover while no shift is armed, they are no longer in Doctor — follow stop\u002Fstart\u002Fsetup as those\nskills specify. Until that explicit ask, change nothing. During an unattended shift, the offer is\ninformational only: continue the active work without asking or writing state.\n\nTwo repairs the report names are separate owner actions, never Doctor's own:\n\n- The move into the current layout. On a workspace at an older state-version, or one holding a\n  state file at an earlier path, the `[confirm]` action names each file with its old and new path\n  and says that nothing is deleted; it is `[blocked]` while a shift is armed, a watchman is alive\n  or a lock is held. Relay it as printed. The owner previews it with\n  `\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" migrate-state` and makes it by running that again with\n  `--apply`. A future version is `[blocked]`: never downgrade a marker.\n- A local rule profile. Doctor may list the shipped examples with\n  `\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" apply-profile --list`\n  and preview one with `--profile \u003Cname> --mode fill` (or `--mode replace`). Preview is the\n  default; only `--apply` writes, and Invoking\n  Doctor never writes `rules.json`.\n\nA senior may run the read-only project inventory after the report:\n`\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" inventory`. It prints one table per\nworkspace package — package manager and lockfile, the scripts declared for test, lint, typecheck,\nbuild and format, the config files present, and each named tool as `declared`, `runnable` or\n`absent`. Those three words are the whole verdict; the report never calls a project misconfigured.\nIt writes and caches nothing, and Doctor never runs it — offer it, the way every other action here\nis offered.\n\nIf the owner then explicitly asks to **Export support bundle**, they are no longer in Doctor.\nRun\n`\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" export-support`.\nPrint its path, included sections, and omitted categories. Do not upload, attach, transmit, or open\nthe file. Invoking Doctor alone must not create `$NS\u002Fsupport\u002F`.\n",{"name":5,"license":15,"metadata":37,"description":7},{"internal":38},true,"main","f620abaff09061f8c8b1f1559dca3fdd031a32e5","plugins\u002Forwa-mahmoud\u002Fnightshift\u002Fskills\u002Fdoctor",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":38},[51,54,57],{"tool":52,"command":53},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill doctor",{"tool":55,"command":56},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill doctor",{"tool":58,"command":59},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill doctor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Forwa-mahmoud\u002Fnightshift\u002Fskills\u002Fdoctor\u002FSKILL.md",[],[63,72,80,88,96,104],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":71},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":71},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":71},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":71},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":71},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\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":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":71},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]