[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ME11765F44EC5KJ4E1Q276":3,"skill-same:01M6ME11765F44EC5KJ4E1Q276":72},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6ME11765F44EC5KJ4E1Q276","omos-plan",null,"Plan an OpenSpec change via $oh-my-openspec:omos-plan — coverage interview, parallel research, adversarial grill, agent-drafted artifacts, critique loop, mechanical CLI validation. Invoke via $oh-my-openspec:omos-plan.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falexeyco\u002Foh-my-openspec\u002Fskills\u002Fomos-plan\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"omos plan","plan","coverage","invoke","adversarial","my","via","mechanical","openspec","grill","interview","cli","parallel","loop","critique","artifacts","validation","change","research","2026-11-10 10:12:30",false,"---\nname: omos-plan\ndescription: \"Plan an OpenSpec change via $oh-my-openspec:omos-plan — coverage interview, parallel research, adversarial grill, agent-drafted artifacts, critique loop, mechanical CLI validation. Invoke via $oh-my-openspec:omos-plan.\"\n---\n\n> Codex host adaptation (generated from skills\u002Fomos-plan\u002FSKILL.md — source of truth stays there):\n> - Dispatch roles with `spawn_agent` \u002F `send_input` \u002F `wait_agent` \u002F `close_agent`. Subagents are asynchronous (default up to 6 concurrent threads), so a wave is one batch of `spawn_agent` calls followed by `wait_agent` collection — never poll.\n> - `openspec_validate` is provided by this plugin's bundled MCP server as `mcp__openspec__openspec_validate` — call it with `cwd` set to your session's project directory (the `change` filter optional); the VALID\u002FINVALID\u002FUNAVAILABLE\u002FERROR one-look report format is identical to OpenCode.\n> - This skill is invoked as a `$oh-my-openspec:omos-plan` mention (or picked from \u002Fskills). There is no argument substitution: arguments arrive as plain text in the user's message after the mention — read them from there; when absent, follow this skill's elicitation steps.\n> - Roles run from `~\u002F.codex\u002Fagents\u002Fomos-*.toml`. If `spawn_agent` reports an unknown agent, stop and tell the user to run `$oh-my-openspec:omos-setup` once.\n\n# omos-plan\n\nTurn the user's request into one complete, validated OpenSpec change under\n`openspec\u002Fchanges\u002F\u003Cchange-id>\u002F`. The orchestrator dispatches, never drafts —\nall artifact writing is done by role subagents. You never run git write\ncommands: the user reviews files and decides what happens to them.\n\n## Flow\n\n### 1. Preconditions\n\n- Check the CLI: call `openspec_validate` once. `UNAVAILABLE` → offer to\n  install it now: run `npm install -g @fission-ai\u002Fopenspec` (or\n  `brew install openspec` on macOS) — a global install is a system change,\n  so proceed only on an explicit yes. Installed → re-check and continue.\n  **Declined** → offer to continue critic-only (non-mechanical validation)\n  — their explicit yes required.\n- Check the project: `openspec\u002F` directory must exist. **Missing** → ask the\n  user for consent, then run `openspec init --tools none` (project artifacts\n  only; the plugin already provides every OpenSpec skill — never re-init\n  tool files). **User declines** → stop.\n\n### 2. Scope check\n\nOne change per run. If the request spans independent capabilities, produce a\ncapability map (`\u003Cname>: \u003Cone line> — depends on: \u003Cnames|none>`) and ask the\nuser which capability to plan first.\n\n### 3. Coverage interview\n\nKeep an internal coverage map over six categories — `Outcome + scenarios \u002F\nConstraints + compat \u002F Data + integrations \u002F Failure + edge \u002F Out of scope \u002F\nSuccess metric` — each `Clear \u002F Partial \u002F Missing` from the request text.\nAsk about at most 5 questions per round, ordered by `Impact × Uncertainty`\n(Missing categories first), each with a recommended answer:\n\n- Outcome: what the user observes when this is done.\n- Why now, and what \"good\" looks like (these become spec scenarios).\n- Constraints: platforms, libraries, performance, compatibility.\n- Out of scope: what this change must not touch.\n- Capability name(s) the behavior belongs to.\n\nSkip questions the request already answers. Every question defines its terms\nwith a concrete example or an either\u002For gloss; when the user signals\nnon-understanding, in any language, restate the question with the gloss before\nrecording an answer as `ASSUMPTION:`. Label anything the user leaves implicit\n`ASSUMPTION:` — the planner seeds these into the artifacts.\n\n### 4. Research\n\nDispatch `omos-researcher` subagents in parallel — one per unknown area\n(codebase region, existing capability, conventions). Wait for every report.\nEvery Unknown a read-only local command can answer (`\u003Cbinary> --help`, a\nno-arg subcommand that performs no action) is re-dispatched to a researcher\nwith a `PROBE:` line; no probe-resolvable Unknown survives into the §6\nplayback. Feed facts into the next steps; surface their `Unknowns:` questions\nin the following interview round.\n\n### 5. Grill (1–3 rounds, up to 5)\n\nAdversarial pass over the user's answers — the point is to break weak\nintent before it becomes paper.\n\n- Every attack must cite evidence: a research fact (`path:line`) or the\n  user's own words. No invented what-ifs; an attack you cannot ground is\n  dropped.\n- Attack checklist per material claim: alternative (\"why not the existing\n  `X`?\"), edge\u002Ffailure case, \"what would make this decision wrong\",\n  scope-reduction pressure, scenario prioritization (\"which two would you\n  still ship without?\").\n- Normally 1–3 rounds; up to 5 only when the change is large-scale —\n  multiple capabilities in the map, compatibility\u002Fmigration risk, or the\n  user calls it big. At most 3 attacks per claim per round.\n- A round that produces no grounded attack ends the grill — intensity is\n  set by what the evidence challenges, not by a quota.\n- The user may end the grill at any time with \"enough\".\n- **Saturation (grill is done when all three hold):** no category of the\n  §3 coverage map is `Missing`; every vague adjective is pinned to a\n  metric (\"fast\" → fast = how much, measured where?); and the last round\n  produced no new grounded attack.\n- Each risk the user dismisses is recorded as\n  `REJECTED-RISK: \u003Crisk> — \u003Ctheir reason or \"no reason given\">`.\n  The grill does not override the user — it makes the dismissal visible.\n\n### 6. Playback gate\n\nRestate intent in seven lines — `Outcome \u002F Why now \u002F Success \u002F Constraints \u002F\nOut of scope \u002F Rejected risks \u002F Established` — and get explicit confirmation\nbefore any file is written. `Established:` recites up to five decision-relevant\nresearch findings the user might re-ask, one per line, absences included (e.g.\n\"X exposes no theme API\").\n\n### 7. Draft\n\nDispatch `omos-planner` with `MODE: plan`: the confirmed playback,\nresearch facts, assumptions, `REJECTED-RISK:` lines, and a proposed change\nid (kebab-case verb-ish noun). It writes proposal, spec deltas, design\n(when non-trivial), tasks.\n\n### 8. Critique loop (≤3 rounds)\n\nDispatch `omos-critic` on the drafted change.\n\n- `NEEDS-FIX` → dispatch `omos-planner` with the exact BLOCKING list to\n  revise; repeat.\n- Wait for the planner revision to report DONE (the role's Status line)\n  before dispatching the next critic; never batch a critic with the revision\n  whose files it reads.\n- `CLEAN` → continue.\n- After 3 rounds still `NEEDS-FIX` → present the open findings to the user\n  and ask: accept them, run one final planner revise plus mechanical\n  `openspec_validate` with no further critic, or stop. A final revise ending\n  with INVALID output is fixed mechanically and re-validated until VALID —\n  never waived, the next bullet holds at loop end; only editorial findings\n  are acceptable by user choice.\n- Mechanical INVALID lines from the critic are always fixed first, never\n  waived by you.\n\n### 9. Mechanical validation and recovery\n\nAfter the critique path is complete and before approval, call\n`openspec_validate` for the drafted change.\n\n- `VALID` → continue to §10.\n- `INVALID` → dispatch `omos-planner` with the exact numbered findings and\n  request a correction. After each planner revision, run `openspec_validate`\n  again for the same change.\n- If findings remain after a revision or the planner reports it cannot safely\n  resolve them, show the exact remaining findings and offer the user another\n  planner revision or the chance to fix them. Do not claim validation passed.\n\nThis mechanical correction step does not consume the critique loop's\nthree-round limit. When the user previously chose critic-only because the CLI\nwas unavailable, report that mechanical validation could not run and continue\nto approval with the critic result clearly identified as non-mechanical.\n\n### 10. Approval\n\nPresent: change id, file list with one-line summaries, every `ASSUMPTION:`\nand `REJECTED-RISK:` line verbatim, validation result. Ask the user to\nconfirm.\n\n- Confirmed → final report: files, gate output, the current branch read from\n  a read-only `git branch --show-current`-style check or \"no branch yet\"\n  (reporting only — not a §1 precondition, no branch creation), next step\n  `$oh-my-openspec:omos-apply \u003Cchange-id>`. Stop — do not implement in the same breath.\n  Offered invocations are the plugin's `$oh-my-openspec:omos-*` skill mentions\n  whenever one exists for the action; the upstream `openspec` CLI is\n  offered only where the plugin has no equivalent.\n- Rejected → collect the fix list as one interview round, go to §7.\n\n## Guardrails\n\n- No file outside `openspec\u002Fchanges\u002F\u003Cchange-id>\u002F` and `openspec\u002Fspecs\u002F` is\n  written by any dispatched role; project code is untouched in this command.\n- Never commit, push, or stage anything.\n- The user's confirmed playback, not chat history, is the drafting contract.\n","> Codex host adaptation (generated from skills\u002Fomos-plan\u002FSKILL.md — source of truth stays there):\n> - Dispatch roles with `spawn_agent` \u002F `send_input` \u002F `wait_agent` \u002F `close_agent`. Subagents are asynchronous (default up to 6 concurrent threads), so a wave is one batch of `spawn_agent` calls followed by `wait_agent` collection — never poll.\n> - `openspec_validate` is provided by this plugin's bundled MCP server as `mcp__openspec__openspec_validate` — call it with `cwd` set to your session's project directory (the `change` filter optional); the VALID\u002FINVALID\u002FUNAVAILABLE\u002FERROR one-look report format is identical to OpenCode.\n> - This skill is invoked as a `$oh-my-openspec:omos-plan` mention (or picked from \u002Fskills). There is no argument substitution: arguments arrive as plain text in the user's message after the mention — read them from there; when absent, follow this skill's elicitation steps.\n> - Roles run from `~\u002F.codex\u002Fagents\u002Fomos-*.toml`. If `spawn_agent` reports an unknown agent, stop and tell the user to run `$oh-my-openspec:omos-setup` once.\n\n# omos-plan\n\nTurn the user's request into one complete, validated OpenSpec change under\n`openspec\u002Fchanges\u002F\u003Cchange-id>\u002F`. The orchestrator dispatches, never drafts —\nall artifact writing is done by role subagents. You never run git write\ncommands: the user reviews files and decides what happens to them.\n\n## Flow\n\n### 1. Preconditions\n\n- Check the CLI: call `openspec_validate` once. `UNAVAILABLE` → offer to\n  install it now: run `npm install -g @fission-ai\u002Fopenspec` (or\n  `brew install openspec` on macOS) — a global install is a system change,\n  so proceed only on an explicit yes. Installed → re-check and continue.\n  **Declined** → offer to continue critic-only (non-mechanical validation)\n  — their explicit yes required.\n- Check the project: `openspec\u002F` directory must exist. **Missing** → ask the\n  user for consent, then run `openspec init --tools none` (project artifacts\n  only; the plugin already provides every OpenSpec skill — never re-init\n  tool files). **User declines** → stop.\n\n### 2. Scope check\n\nOne change per run. If the request spans independent capabilities, produce a\ncapability map (`\u003Cname>: \u003Cone line> — depends on: \u003Cnames|none>`) and ask the\nuser which capability to plan first.\n\n### 3. Coverage interview\n\nKeep an internal coverage map over six categories — `Outcome + scenarios \u002F\nConstraints + compat \u002F Data + integrations \u002F Failure + edge \u002F Out of scope \u002F\nSuccess metric` — each `Clear \u002F Partial \u002F Missing` from the request text.\nAsk about at most 5 questions per round, ordered by `Impact × Uncertainty`\n(Missing categories first), each with a recommended answer:\n\n- Outcome: what the user observes when this is done.\n- Why now, and what \"good\" looks like (these become spec scenarios).\n- Constraints: platforms, libraries, performance, compatibility.\n- Out of scope: what this change must not touch.\n- Capability name(s) the behavior belongs to.\n\nSkip questions the request already answers. Every question defines its terms\nwith a concrete example or an either\u002For gloss; when the user signals\nnon-understanding, in any language, restate the question with the gloss before\nrecording an answer as `ASSUMPTION:`. Label anything the user leaves implicit\n`ASSUMPTION:` — the planner seeds these into the artifacts.\n\n### 4. Research\n\nDispatch `omos-researcher` subagents in parallel — one per unknown area\n(codebase region, existing capability, conventions). Wait for every report.\nEvery Unknown a read-only local command can answer (`\u003Cbinary> --help`, a\nno-arg subcommand that performs no action) is re-dispatched to a researcher\nwith a `PROBE:` line; no probe-resolvable Unknown survives into the §6\nplayback. Feed facts into the next steps; surface their `Unknowns:` questions\nin the following interview round.\n\n### 5. Grill (1–3 rounds, up to 5)\n\nAdversarial pass over the user's answers — the point is to break weak\nintent before it becomes paper.\n\n- Every attack must cite evidence: a research fact (`path:line`) or the\n  user's own words. No invented what-ifs; an attack you cannot ground is\n  dropped.\n- Attack checklist per material claim: alternative (\"why not the existing\n  `X`?\"), edge\u002Ffailure case, \"what would make this decision wrong\",\n  scope-reduction pressure, scenario prioritization (\"which two would you\n  still ship without?\").\n- Normally 1–3 rounds; up to 5 only when the change is large-scale —\n  multiple capabilities in the map, compatibility\u002Fmigration risk, or the\n  user calls it big. At most 3 attacks per claim per round.\n- A round that produces no grounded attack ends the grill — intensity is\n  set by what the evidence challenges, not by a quota.\n- The user may end the grill at any time with \"enough\".\n- **Saturation (grill is done when all three hold):** no category of the\n  §3 coverage map is `Missing`; every vague adjective is pinned to a\n  metric (\"fast\" → fast = how much, measured where?); and the last round\n  produced no new grounded attack.\n- Each risk the user dismisses is recorded as\n  `REJECTED-RISK: \u003Crisk> — \u003Ctheir reason or \"no reason given\">`.\n  The grill does not override the user — it makes the dismissal visible.\n\n### 6. Playback gate\n\nRestate intent in seven lines — `Outcome \u002F Why now \u002F Success \u002F Constraints \u002F\nOut of scope \u002F Rejected risks \u002F Established` — and get explicit confirmation\nbefore any file is written. `Established:` recites up to five decision-relevant\nresearch findings the user might re-ask, one per line, absences included (e.g.\n\"X exposes no theme API\").\n\n### 7. Draft\n\nDispatch `omos-planner` with `MODE: plan`: the confirmed playback,\nresearch facts, assumptions, `REJECTED-RISK:` lines, and a proposed change\nid (kebab-case verb-ish noun). It writes proposal, spec deltas, design\n(when non-trivial), tasks.\n\n### 8. Critique loop (≤3 rounds)\n\nDispatch `omos-critic` on the drafted change.\n\n- `NEEDS-FIX` → dispatch `omos-planner` with the exact BLOCKING list to\n  revise; repeat.\n- Wait for the planner revision to report DONE (the role's Status line)\n  before dispatching the next critic; never batch a critic with the revision\n  whose files it reads.\n- `CLEAN` → continue.\n- After 3 rounds still `NEEDS-FIX` → present the open findings to the user\n  and ask: accept them, run one final planner revise plus mechanical\n  `openspec_validate` with no further critic, or stop. A final revise ending\n  with INVALID output is fixed mechanically and re-validated until VALID —\n  never waived, the next bullet holds at loop end; only editorial findings\n  are acceptable by user choice.\n- Mechanical INVALID lines from the critic are always fixed first, never\n  waived by you.\n\n### 9. Mechanical validation and recovery\n\nAfter the critique path is complete and before approval, call\n`openspec_validate` for the drafted change.\n\n- `VALID` → continue to §10.\n- `INVALID` → dispatch `omos-planner` with the exact numbered findings and\n  request a correction. After each planner revision, run `openspec_validate`\n  again for the same change.\n- If findings remain after a revision or the planner reports it cannot safely\n  resolve them, show the exact remaining findings and offer the user another\n  planner revision or the chance to fix them. Do not claim validation passed.\n\nThis mechanical correction step does not consume the critique loop's\nthree-round limit. When the user previously chose critic-only because the CLI\nwas unavailable, report that mechanical validation could not run and continue\nto approval with the critic result clearly identified as non-mechanical.\n\n### 10. Approval\n\nPresent: change id, file list with one-line summaries, every `ASSUMPTION:`\nand `REJECTED-RISK:` line verbatim, validation result. Ask the user to\nconfirm.\n\n- Confirmed → final report: files, gate output, the current branch read from\n  a read-only `git branch --show-current`-style check or \"no branch yet\"\n  (reporting only — not a §1 precondition, no branch creation), next step\n  `$oh-my-openspec:omos-apply \u003Cchange-id>`. Stop — do not implement in the same breath.\n  Offered invocations are the plugin's `$oh-my-openspec:omos-*` skill mentions\n  whenever one exists for the action; the upstream `openspec` CLI is\n  offered only where the plugin has no equivalent.\n- Rejected → collect the fix list as one interview round, go to §7.\n\n## Guardrails\n\n- No file outside `openspec\u002Fchanges\u002F\u003Cchange-id>\u002F` and `openspec\u002Fspecs\u002F` is\n  written by any dispatched role; project code is untouched in this command.\n- Never commit, push, or stage anything.\n- The user's confirmed playback, not chat history, is the drafting contract.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Falexeyco\u002Foh-my-openspec\u002Fskills\u002Fomos-plan",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill omos-plan",{"tool":64,"command":65},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill omos-plan",{"tool":67,"command":68},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill omos-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falexeyco\u002Foh-my-openspec\u002Fskills\u002Fomos-plan\u002FSKILL.md",true,[],[73,83,91,99,107,115],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":82},"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.","MIT","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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":82},"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":82},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":82},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":82},"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":82},"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",[],[]]