[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ME0N0XGBA1W44R5W3Q0KJR":3,"skill-same:01M6ME0N0XGBA1W44R5W3Q0KJR":65},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6ME0N0XGBA1W44R5W3Q0KJR","omos-apply",null,"Apply an OpenSpec change via $oh-my-openspec:omos-apply — implement task groups in parallel waves, verify scenarios, review the diff. Never commits. Invoke via $oh-my-openspec:omos-apply.","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-apply\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"omos apply","apply","implement task","groups","invoke","my","via","task","openspec","review","never","diff","parallel","commits","verify","change","implement","2026-11-10 10:12:30",false,"---\nname: omos-apply\ndescription: \"Apply an OpenSpec change via $oh-my-openspec:omos-apply — implement task groups in parallel waves, verify scenarios, review the diff. Never commits. Invoke via $oh-my-openspec:omos-apply.\"\n---\n\n> Codex host adaptation (generated from skills\u002Fomos-apply\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-apply` 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-apply\n\nImplement `openspec\u002Fchanges\u002F\u003Cchange-id>\u002F` through dependency-ordered parallel\nsubagent waves with verification and review. The OpenSpec artifacts are the\ncontract. You never run git write commands — the user reviews and commits.\n\n## Flow\n\n### 1. Select the change\n\n- `Change: \u003Cid>` given → use it.\n- Otherwise run `openspec list --json` (or read `openspec\u002Fchanges\u002F`).\n  Exactly one active change → confirm it. Several → ask, one per run.\n  None → tell the user to run `$oh-my-openspec:omos-plan` and stop.\n\n### 2. Mechanical gate\n\nRun `openspec_validate` with the change id.\n\n- `UNAVAILABLE` → offer to install the CLI now (`npm install -g\n@fission-ai\u002Fopenspec`, or `brew install openspec` on macOS; explicit yes\n  required). **Declined** → stop — unlike plan, apply cannot verify without\n  the gate.\n- Not VALID → stop, report the numbered violations, suggest a\n  `$oh-my-openspec:omos-plan` fix round. Do not proceed.\n\n### 3. Wave plan\n\nDispatch `omos-planner` with `MODE: waves` over `tasks.md` + `design.md`.\nIt returns ordered waves of task groups (groups run in parallel within a\nwave; overlapping files serialize groups into later waves; conservative\nchoices on uncertainty). Each wave-table row lists its groups' exact file\npaths, and the planner's `MODE: waves` rules are the source of truth for\nhow waves are formed. Record the wave table in the session before\ndispatching.\n\n### 4. Execute waves\n\nFor each wave, in order:\n\n- Dispatch one `omos-implementer` per group in the wave, all in a single\n  parallel batch. On Codex the batch is one set of `spawn_agent` calls that return\n  immediately — collect each report with `wait_agent`, relay follow-ups\n  with `send_input`, and release threads with `close_agent`; never poll.\n- Each implementer prompt carries verbatim: the group's tasks, the spec\n  requirement\u002Fscenario sections they implement, design.md decisions touching\n  the group, and the full wave table, including each group's assigned files.\n- Implementers tick their own `- [ ]` → `- [x]` in `tasks.md`.\n- A user request arriving mid-wave is first checked against the wave table —\n  the single source of execution order (Guardrails) — and the remaining\n  `tasks.md` items; a covering task is cited, never duplicated by a new\n  dispatch.\n\n### 5. Blockage and conflict\n\nAn implementer `BLOCKED:` answer stops the run's dispatch loop for the\naffected wave:\n\n- `file conflict` → re-dispatch the blocked group alone in a follow-up\n  mini-wave after its conflicting sibling completes.\n- Guardrail or plan defect → halt and ask the user (irreversible action,\n  security change, external side effect, broken plan are always user\n  decisions). Never lower the bar to get green. Exception: a\n  prompt-truncation `BLOCKED:` is the orchestrator's defect, not the\n  plan's — re-dispatch the group with a numbered edit list of ≤150 lines\n  referencing `file:line`, not inlined spec or transcript text.\n\n### 6. Verify\n\nBefore §7 Review, the orchestrator's ordering gate: every manual\u002Feyeball\nacceptance group in `tasks.md` is executed with the user and its\nconfirmation recorded — no change enters Review with any such group\nunticked. `DEFERRED:` is inadmissible for tasks in those groups — they end\nticked or the run halts. This gate is ordering only; the verifier's\n`tasks.md` consistency check stays a separate mechanical audit.\n\nAfter the final wave: dispatch one `omos-verifier` per capability spec\nfile in parallel. Each runs the mechanical gate, executes every scenario's\nWHEN\u002FTHEN, and checks `tasks.md` consistency.\n\n- Any FAIL → one fix round: dispatch `omos-implementer` per failing\n  capability with the exact scenario lines, then re-run only the failed\n  verifiers.\n- Rejected: verifier reports that repeat the original claim with a weakened\n  bar (skipped test, widened assertion) → treat as FAIL, do not re-dispatch\n  the same implementer unchanged.\n- Relay every implementer `DEFERRED:` line (`DEFERRED: \u003Ctask-id> — \u003Creason>\n— \u003Cuser action>`) verbatim to the user before §7 Review starts; a\n  deferral naming a task in a manual\u002Feyeball group halts at the gate above\n  instead of being relayed.\n- After the final wave, before §7 Review, the orchestrator (or a designated\n  dispatch) performs the post-final-wave full check suite run once and\n  cites its output in the reviewer payload; implementer-scoped runs do\n  not replace it.\n\n### 7. Review\n\nDispatch `omos-reviewer` over the cumulative diff (`git diff --stat` +\nfull diff) with a `REVIEW FOCUS:` block: the riskiest hunks from the wave\ntable, verifier notes, and the verbatim `Choices:` report lines of every\nwave implementer (including `Choices: none`).\n\n- `CHANGES-REQUESTED` → fix round (implementer), then scoped re-review: only\n  the open findings, answered `ADDRESSED` \u002F `NOT-ADDRESSED`.\n- On `CHANGES-REQUESTED`, before dispatching the re-review, run the repo's\n  own markdown\u002Flint check over every `openspec\u002F` artifact the fix round\n  touched, when the repo has one, and paste its output into the re-review\n  dispatch.\n- BLOCKING findings left at the user's explicit choice only, recorded as\n  `ruling:` lines.\n\n### 8. Done\n\nFinal report:\n\n- Groups completed per wave with evidence one-liners.\n- `choice:` entries — every implementer `Choices:` decision worth the user's\n  eye, one line each (`none` if empty).\n- `ruling:` entries — user-approved deviations, verbatim.\n- `DEFERRED:` entries — verbatim, one line each\n  (`DEFERRED: \u003Ctask-id> — \u003Creason> — \u003Cuser action>`).\n- Verification summary: scenarios PASS count \u002F total, gate VALID;\n  `PASS (composited)` lines count as passes.\n- `NO-REGRESSION-TEST:` entries — every verifier line relayed verbatim,\n  one line each.\n- `git diff --stat` of the working tree.\n- Next steps for the user, in their hands: review the diff, commit, then\n  archive with `$oh-my-openspec:omos-archive \u003Cchange-id>`. Offered invocations are the\n  plugin's `$oh-my-openspec:omos-*` skill mentions whenever one exists for the action;\n  the upstream `openspec` CLI is offered only where the plugin has no\n  equivalent.\n- Branching questions are answered by citing the repo's `CONTRIBUTING.md`\n  branch-naming convention, e.g. `feat\u002F\u003Ctopic>` — branch creation, renaming,\n  and commits stay the user's; the flow performs no git writes.\n\n## Guardrails\n\n- Implementation is bounded by the spec delta: any needed change outside it\n  is a plan defect → stop and ask, do not sneak it in.\n- Never commit, push, or stage; never run `openspec archive` — archiving is\n  a deliberate user act after review.\n- The wave table is the single source of execution order for this run.\n","> Codex host adaptation (generated from skills\u002Fomos-apply\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-apply` 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-apply\n\nImplement `openspec\u002Fchanges\u002F\u003Cchange-id>\u002F` through dependency-ordered parallel\nsubagent waves with verification and review. The OpenSpec artifacts are the\ncontract. You never run git write commands — the user reviews and commits.\n\n## Flow\n\n### 1. Select the change\n\n- `Change: \u003Cid>` given → use it.\n- Otherwise run `openspec list --json` (or read `openspec\u002Fchanges\u002F`).\n  Exactly one active change → confirm it. Several → ask, one per run.\n  None → tell the user to run `$oh-my-openspec:omos-plan` and stop.\n\n### 2. Mechanical gate\n\nRun `openspec_validate` with the change id.\n\n- `UNAVAILABLE` → offer to install the CLI now (`npm install -g\n@fission-ai\u002Fopenspec`, or `brew install openspec` on macOS; explicit yes\n  required). **Declined** → stop — unlike plan, apply cannot verify without\n  the gate.\n- Not VALID → stop, report the numbered violations, suggest a\n  `$oh-my-openspec:omos-plan` fix round. Do not proceed.\n\n### 3. Wave plan\n\nDispatch `omos-planner` with `MODE: waves` over `tasks.md` + `design.md`.\nIt returns ordered waves of task groups (groups run in parallel within a\nwave; overlapping files serialize groups into later waves; conservative\nchoices on uncertainty). Each wave-table row lists its groups' exact file\npaths, and the planner's `MODE: waves` rules are the source of truth for\nhow waves are formed. Record the wave table in the session before\ndispatching.\n\n### 4. Execute waves\n\nFor each wave, in order:\n\n- Dispatch one `omos-implementer` per group in the wave, all in a single\n  parallel batch. On Codex the batch is one set of `spawn_agent` calls that return\n  immediately — collect each report with `wait_agent`, relay follow-ups\n  with `send_input`, and release threads with `close_agent`; never poll.\n- Each implementer prompt carries verbatim: the group's tasks, the spec\n  requirement\u002Fscenario sections they implement, design.md decisions touching\n  the group, and the full wave table, including each group's assigned files.\n- Implementers tick their own `- [ ]` → `- [x]` in `tasks.md`.\n- A user request arriving mid-wave is first checked against the wave table —\n  the single source of execution order (Guardrails) — and the remaining\n  `tasks.md` items; a covering task is cited, never duplicated by a new\n  dispatch.\n\n### 5. Blockage and conflict\n\nAn implementer `BLOCKED:` answer stops the run's dispatch loop for the\naffected wave:\n\n- `file conflict` → re-dispatch the blocked group alone in a follow-up\n  mini-wave after its conflicting sibling completes.\n- Guardrail or plan defect → halt and ask the user (irreversible action,\n  security change, external side effect, broken plan are always user\n  decisions). Never lower the bar to get green. Exception: a\n  prompt-truncation `BLOCKED:` is the orchestrator's defect, not the\n  plan's — re-dispatch the group with a numbered edit list of ≤150 lines\n  referencing `file:line`, not inlined spec or transcript text.\n\n### 6. Verify\n\nBefore §7 Review, the orchestrator's ordering gate: every manual\u002Feyeball\nacceptance group in `tasks.md` is executed with the user and its\nconfirmation recorded — no change enters Review with any such group\nunticked. `DEFERRED:` is inadmissible for tasks in those groups — they end\nticked or the run halts. This gate is ordering only; the verifier's\n`tasks.md` consistency check stays a separate mechanical audit.\n\nAfter the final wave: dispatch one `omos-verifier` per capability spec\nfile in parallel. Each runs the mechanical gate, executes every scenario's\nWHEN\u002FTHEN, and checks `tasks.md` consistency.\n\n- Any FAIL → one fix round: dispatch `omos-implementer` per failing\n  capability with the exact scenario lines, then re-run only the failed\n  verifiers.\n- Rejected: verifier reports that repeat the original claim with a weakened\n  bar (skipped test, widened assertion) → treat as FAIL, do not re-dispatch\n  the same implementer unchanged.\n- Relay every implementer `DEFERRED:` line (`DEFERRED: \u003Ctask-id> — \u003Creason>\n— \u003Cuser action>`) verbatim to the user before §7 Review starts; a\n  deferral naming a task in a manual\u002Feyeball group halts at the gate above\n  instead of being relayed.\n- After the final wave, before §7 Review, the orchestrator (or a designated\n  dispatch) performs the post-final-wave full check suite run once and\n  cites its output in the reviewer payload; implementer-scoped runs do\n  not replace it.\n\n### 7. Review\n\nDispatch `omos-reviewer` over the cumulative diff (`git diff --stat` +\nfull diff) with a `REVIEW FOCUS:` block: the riskiest hunks from the wave\ntable, verifier notes, and the verbatim `Choices:` report lines of every\nwave implementer (including `Choices: none`).\n\n- `CHANGES-REQUESTED` → fix round (implementer), then scoped re-review: only\n  the open findings, answered `ADDRESSED` \u002F `NOT-ADDRESSED`.\n- On `CHANGES-REQUESTED`, before dispatching the re-review, run the repo's\n  own markdown\u002Flint check over every `openspec\u002F` artifact the fix round\n  touched, when the repo has one, and paste its output into the re-review\n  dispatch.\n- BLOCKING findings left at the user's explicit choice only, recorded as\n  `ruling:` lines.\n\n### 8. Done\n\nFinal report:\n\n- Groups completed per wave with evidence one-liners.\n- `choice:` entries — every implementer `Choices:` decision worth the user's\n  eye, one line each (`none` if empty).\n- `ruling:` entries — user-approved deviations, verbatim.\n- `DEFERRED:` entries — verbatim, one line each\n  (`DEFERRED: \u003Ctask-id> — \u003Creason> — \u003Cuser action>`).\n- Verification summary: scenarios PASS count \u002F total, gate VALID;\n  `PASS (composited)` lines count as passes.\n- `NO-REGRESSION-TEST:` entries — every verifier line relayed verbatim,\n  one line each.\n- `git diff --stat` of the working tree.\n- Next steps for the user, in their hands: review the diff, commit, then\n  archive with `$oh-my-openspec:omos-archive \u003Cchange-id>`. Offered invocations are the\n  plugin's `$oh-my-openspec:omos-*` skill mentions whenever one exists for the action;\n  the upstream `openspec` CLI is offered only where the plugin has no\n  equivalent.\n- Branching questions are answered by citing the repo's `CONTRIBUTING.md`\n  branch-naming convention, e.g. `feat\u002F\u003Ctopic>` — branch creation, renaming,\n  and commits stay the user's; the flow performs no git writes.\n\n## Guardrails\n\n- Implementation is bounded by the spec delta: any needed change outside it\n  is a plan defect → stop and ask, do not sneak it in.\n- Never commit, push, or stage; never run `openspec archive` — archiving is\n  a deliberate user act after review.\n- The wave table is the single source of execution order for this run.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Falexeyco\u002Foh-my-openspec\u002Fskills\u002Fomos-apply",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill omos-apply",{"tool":57,"command":58},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill omos-apply",{"tool":60,"command":61},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill omos-apply","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falexeyco\u002Foh-my-openspec\u002Fskills\u002Fomos-apply\u002FSKILL.md",true,[],[66,76,84,92,100,108],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":75},"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":75},"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":75},"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":75},"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":75},"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":75},"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",[],[]]