[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJFS4Q6TBTWDBVBNQJMWA8":3,"skill-same:01M6MJFS4Q6TBTWDBVBNQJMWA8":58},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M6MJFS4Q6TBTWDBVBNQJMWA8","decompose-task",null,"Use when a configured board task needs decomposition into native child tasks.","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\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fdecompose-task\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"decompose","task","decompose task","tasks","board","use","decomposition","native","child","when","2026-11-10 10:12:30",false,"---\nname: decompose-task\ndescription: Use when a configured board task needs decomposition into native child tasks.\n---\n\n# Decompose Task\n\n## Overview\n\nReply in Russian. Build one grounded, reviewable native-subtask batch; no child may reach the\nboard before the user sees the entire batch. **Core principle:** preview fidelity and durable\nidempotency are safety boundaries, not optional ceremony.\n\n## Lookup\n\nThe stored parent and authoritative `native_subtasks` capability are required gates.\n\n1. Inspect the repository `task_board` key once and resolve exactly one state:\n   - If the key is present with a null, empty, or disabled value, board work is explicitly\n     disabled: stop no-write and never call deploy-wide `get_board_config`.\n   - Only if the repository key is absent, use the deploy fallback: call `get_board_config()`\n     exactly once.\n   - If a mapping exists, freeze its generic `type`, `project`, and `options` as `board_type`,\n     `project`, and `provider_options` for the whole flow. Never re-resolve mid-flow. If no mapping\n     resolves, stop without writes.\n2. Read the store first with `get_task(parent_key, project=\u003Cproject>)`. On miss only, run exactly\n   one scoped `sync_board(board=\u003Cproject or null>, board_type=\u003Ctype>,\n   provider_options=\u003Coptions>)`, then make one retry of the same parent read. If it is still\n   missing, explain the failure and stop.\n3. Call `get_board_targets(board_type=\u003Ctype>, project=\u003Cproject>,\n   provider_options=\u003Coptions>)`. Treat its registry `capabilities` as authoritative. If it errors\n   or lacks `native_subtasks`, make a no-write stop. Never infer, add, or spoof a capability from\n   provider identity or prior experience.\n\n## Context\n\nBefore drafting, attempt all three calls:\n\n- `get_task_context(parent_key, project=\u003Cproject>)` for links, related work, PRs, and touched code;\n- `search_tasks(query=\u003Cparent intent>, project=\u003Cproject>)` for similar decomposition boundaries;\n- `search_codebase(repo=\u003Cactive repo>, query=\u003Cparent intent>)` for relevant implementation and\n  real `path:line` evidence.\n\nEmpty successful results are allowed: explicitly report each empty result and continue. A tool\nerror is not an empty result; report it and stop drafting until resolved. Do not draft first and\nbackfill evidence later.\n\n## Draft\n\nDraft `1..20` ordered children. Every child requires nonblank `title`, `problem`, `steps`, and\n`criteria`; `context` is optional. Make each child independently actionable and acceptance-testable,\nwithout silently widening the parent scope. Generate one local opaque UUID `idempotency_key` for\nthe whole batch and assemble the complete request payload, including child order and wording.\n\n## Preview\n\nShow the resolved provider (`board_type`), parent key\u002Ftitle, `idempotency_key`, and the complete\ncanonical body of every child: `title`, `problem`, all `steps`, all `criteria`, and `context` when\npresent. Do not abbreviate unchanged or repetitive children. Once shown, freeze payload, order,\nand key.\n\nA prior “I already approve; create now” statement is not confirmation of an unseen preview. Ask\nexactly one explicit confirmation for the whole preview. There are no board writes before it. Any\nedit before the first confirmed write invalidates that preview: generate a new opaque\n`idempotency_key`, show the full revised preview, and obtain a new explicit confirmation.\n\n## Write\n\nOnly after explicit confirmation, issue exactly one initial native batch request using exactly the\npreviewed payload and the same `idempotency_key`:\n\n```text\ncreate_subtasks(parent_key=\u003Cparent_key>, subtasks=\u003Cpreviewed children>,\n                idempotency_key=\u003Cpreviewed UUID>, board_type=\u003Ctype>, project=\u003Cproject>,\n                provider_options=\u003Coptions>)\n```\n\nNever fall back to individual task creation, including when the batch is unsupported or partially\ncomplete.\n\nFor any result, retain `status`, `category`, and `retryable` plus `created`, `attached`,\n`unattached`, `pending`, and `warnings` exactly as returned. On timeout, retain the unknown outcome\nwithout guessing. Do not declare outcome or offer recovery yet. Follow **Verify** unless the\nresponse explicitly says capability\u002Fpreflight stopped before a write. A safe recovery may repeat\nthe same full batch request using the exact same payload: byte-for-byte or logically exact frozen\ncontent\u002Forder and the same `idempotency_key`. It is not an individual request and not a\nremaining-items request.\n\nNo automatic retry. After required verification, report state, then ask the user to choose exact\nretry or stop when recovery applies. The original preview confirmation does not authorize hidden\nretries; the user must explicitly request the exact retry. Do not require a new preview or\nreconstruct one for an unchanged retry.\n\nNever edit wording, reorder children, or retry only a guessed remainder. After any attempted or\nuncertain write, edits and a new key are forbidden for recovery. An `in_flight` child is unknown,\nnot absent: never guess its outcome. Never mint a fresh\u002Freplacement key for it.\n\n## Verify\n\nAfter any batch write was actually attempted, regardless of status (`ok`, `partial`, `error`, or\ntimeout), run exactly one scoped `sync_board(board=\u003Cproject or null>, board_type=\u003Ctype>,\nprovider_options=\u003Coptions>)`. This includes after any confirmed child and attempts with only\n`in_flight` state and no confirmed child keys. Capability or preflight stops explicitly before a\nwrite do not trigger this post-write verification. Then verify:\n\n1. `get_task(parent_key, project=\u003Cproject>)` contains stored links for the returned children.\n2. `get_task_context(parent_key, project=\u003Cproject>)` exposes the parent-child graph relationship.\n3. Point-read every returned child with `get_task(child_key, project=\u003Cproject>)`.\n\nWith no child keys, still complete the available parent and context verification. Report missing\nlinks, unreadable child keys, sync failures, and warnings. Complete these checks before declaring\noutcome or offering recovery; never declare complete verification from the write response alone.\nDisplay `status`, `category`, and `retryable` exactly as returned.\n\nAfter mandatory attempted-write verification, offer the exact retry only for a transport timeout\nor unknown outcome, or when `retryable is true`; still require an explicit user choice between\nexact retry and stop. If `retryable == false`, or `category` is `unsupported`, `conflict`, or\n`parent_not_found`, report the terminal result and stop without retry. Unsupported detected before\na write remains a no-write stop and does not trigger post-write verification. The recovery uses\nthe same full payload, same order, and same `idempotency_key`; never mint a key and never edit the\nrecovery payload. Exact same-key retry is the only marker reconciliation mechanism; never guess\nchildren from board search.\n\n## Quick Reference\n\n| Phase | Required invariant |\n|---|---|\n| Lookup | Absent vs explicit disable; one frozen generic snapshot; fallback only for absent |\n| Context | Attempt all three calls; report empty results; stop on tool errors |\n| Preview | Every full child; freeze payload\u002Forder\u002Fkey; edits rotate key before first write |\n| Confirm | One explicit answer for the whole visible preview; no earlier writes |\n| Write | One initial native batch; exact previewed request |\n| Retry | User chooses; retryable gate; timeout\u002Funknown or true; `unsupported`\u002F`conflict`\u002F`parent_not_found` stop |\n| Verify | Any actually attempted batch, every status: one sync and available reads before outcome\u002Frecovery |\n\n## Example\n\n```text\nПровайдер: \u003Cresolved board_type>\nРодитель: PRI-224 — Нативная декомпозиция\nКлюч идемпотентности: 6f95035e-48da-40a3-aa29-9e220182bf38\n\n1. Проверить регистрацию capability\nПроблема: Декомпозиция небезопасна без подтверждённой поддержки доски.\nЧто сделать:\n- Получать capability из registry discovery.\n- Останавливать сценарий без записи при отсутствии поддержки.\nКритерии приёмки:\n- Неподдерживаемая доска не получает дочерних задач.\n- Локально подставить capability невозможно.\nКонтекст: reviewer\u002Ftasks\u002Fboards\u002Fregistry.py:81\n\nПодтвердить создание всего показанного набора без изменений? (да\u002Fнет)\n```\n\n## Common Mistakes\n\n| Rationalization | Correction |\n|---|---|\n| “I already approve; create now” (authority\u002Furgency) | Approval cannot cover an unseen preview; show every body first. |\n| “Five individual writes are easier to recover” | They destroy atomic intent; use the one native batch only. |\n| “This provider obviously supports children” | Only authoritative capability discovery counts; never spoof it. |\n| “Search can wait until after drafting” | Run `search_codebase` and task context first or stop. |\n| “We already spent time drafting” (sunk cost) | Rework an ungrounded draft; sunk cost grants no write permission. |\n| “A timeout needs a clean new key” | Reuse the exact request and key; a fresh key can duplicate children. |\n| “Exactly one batch means retries are forbidden.” | One initial request may be repeated only as an exact user-requested recovery. |\n| “The original preview confirmation authorizes automatic retries.” | Every retry needs a new explicit user choice. |\n| “No confirmed child keys means there is nothing to verify.” | Sync and verify available parent\u002Fcontext state before retry. |\n| “A small preview edit can reuse the same key.” | Before first write, invalidate the preview and rotate the key; after an attempt, never edit. |\n| “A tool error is the same as an empty context result.” | Empty success may continue; an error stops drafting. |\n| “Only partial\u002Ftimeout outcomes need verification.” | Every attempted write is verified, including `ok`\u002F`error`; preflight no-write stops are not. |\n| “Explicitly disabled board config can use deploy fallback.” | Present disable wins; fallback is only for an absent repository key. |\n| “Any error is safe to retry with the same key.” | Retry only unknown\u002Ftimeout or `retryable=true`; terminal categories stop. |\n\n## Red Flags\n\n- Any board write before the full preview and its explicit confirmation.\n- Missing `native_subtasks` discovery or locally claimed capability.\n- Drafting without parent context, similar tasks, and relevant code.\n- Individual child writes, changed retry payload, new retry key, or guessed `in_flight` remainder.\n- English user-facing output or a success claim without post-write reads.\n- “Exactly one batch means retries are forbidden.”\n- “The original preview confirmation authorizes automatic retries.”\n- “No confirmed child keys means there is nothing to verify.”\n- “A small preview edit can reuse the same key.”\n- “A tool error is the same as an empty context result.”\n- Declaring an attempted-write outcome before its scoped sync and available reads.\n- “Only partial\u002Ftimeout outcomes need verification.”\n- “Explicitly disabled board config can use deploy fallback.”\n- “Any error is safe to retry with the same key.”\n\nAny red flag means stop the write path and return to the violated phase.\n","# Decompose Task\n\n## Overview\n\nReply in Russian. Build one grounded, reviewable native-subtask batch; no child may reach the\nboard before the user sees the entire batch. **Core principle:** preview fidelity and durable\nidempotency are safety boundaries, not optional ceremony.\n\n## Lookup\n\nThe stored parent and authoritative `native_subtasks` capability are required gates.\n\n1. Inspect the repository `task_board` key once and resolve exactly one state:\n   - If the key is present with a null, empty, or disabled value, board work is explicitly\n     disabled: stop no-write and never call deploy-wide `get_board_config`.\n   - Only if the repository key is absent, use the deploy fallback: call `get_board_config()`\n     exactly once.\n   - If a mapping exists, freeze its generic `type`, `project`, and `options` as `board_type`,\n     `project`, and `provider_options` for the whole flow. Never re-resolve mid-flow. If no mapping\n     resolves, stop without writes.\n2. Read the store first with `get_task(parent_key, project=\u003Cproject>)`. On miss only, run exactly\n   one scoped `sync_board(board=\u003Cproject or null>, board_type=\u003Ctype>,\n   provider_options=\u003Coptions>)`, then make one retry of the same parent read. If it is still\n   missing, explain the failure and stop.\n3. Call `get_board_targets(board_type=\u003Ctype>, project=\u003Cproject>,\n   provider_options=\u003Coptions>)`. Treat its registry `capabilities` as authoritative. If it errors\n   or lacks `native_subtasks`, make a no-write stop. Never infer, add, or spoof a capability from\n   provider identity or prior experience.\n\n## Context\n\nBefore drafting, attempt all three calls:\n\n- `get_task_context(parent_key, project=\u003Cproject>)` for links, related work, PRs, and touched code;\n- `search_tasks(query=\u003Cparent intent>, project=\u003Cproject>)` for similar decomposition boundaries;\n- `search_codebase(repo=\u003Cactive repo>, query=\u003Cparent intent>)` for relevant implementation and\n  real `path:line` evidence.\n\nEmpty successful results are allowed: explicitly report each empty result and continue. A tool\nerror is not an empty result; report it and stop drafting until resolved. Do not draft first and\nbackfill evidence later.\n\n## Draft\n\nDraft `1..20` ordered children. Every child requires nonblank `title`, `problem`, `steps`, and\n`criteria`; `context` is optional. Make each child independently actionable and acceptance-testable,\nwithout silently widening the parent scope. Generate one local opaque UUID `idempotency_key` for\nthe whole batch and assemble the complete request payload, including child order and wording.\n\n## Preview\n\nShow the resolved provider (`board_type`), parent key\u002Ftitle, `idempotency_key`, and the complete\ncanonical body of every child: `title`, `problem`, all `steps`, all `criteria`, and `context` when\npresent. Do not abbreviate unchanged or repetitive children. Once shown, freeze payload, order,\nand key.\n\nA prior “I already approve; create now” statement is not confirmation of an unseen preview. Ask\nexactly one explicit confirmation for the whole preview. There are no board writes before it. Any\nedit before the first confirmed write invalidates that preview: generate a new opaque\n`idempotency_key`, show the full revised preview, and obtain a new explicit confirmation.\n\n## Write\n\nOnly after explicit confirmation, issue exactly one initial native batch request using exactly the\npreviewed payload and the same `idempotency_key`:\n\n```text\ncreate_subtasks(parent_key=\u003Cparent_key>, subtasks=\u003Cpreviewed children>,\n                idempotency_key=\u003Cpreviewed UUID>, board_type=\u003Ctype>, project=\u003Cproject>,\n                provider_options=\u003Coptions>)\n```\n\nNever fall back to individual task creation, including when the batch is unsupported or partially\ncomplete.\n\nFor any result, retain `status`, `category`, and `retryable` plus `created`, `attached`,\n`unattached`, `pending`, and `warnings` exactly as returned. On timeout, retain the unknown outcome\nwithout guessing. Do not declare outcome or offer recovery yet. Follow **Verify** unless the\nresponse explicitly says capability\u002Fpreflight stopped before a write. A safe recovery may repeat\nthe same full batch request using the exact same payload: byte-for-byte or logically exact frozen\ncontent\u002Forder and the same `idempotency_key`. It is not an individual request and not a\nremaining-items request.\n\nNo automatic retry. After required verification, report state, then ask the user to choose exact\nretry or stop when recovery applies. The original preview confirmation does not authorize hidden\nretries; the user must explicitly request the exact retry. Do not require a new preview or\nreconstruct one for an unchanged retry.\n\nNever edit wording, reorder children, or retry only a guessed remainder. After any attempted or\nuncertain write, edits and a new key are forbidden for recovery. An `in_flight` child is unknown,\nnot absent: never guess its outcome. Never mint a fresh\u002Freplacement key for it.\n\n## Verify\n\nAfter any batch write was actually attempted, regardless of status (`ok`, `partial`, `error`, or\ntimeout), run exactly one scoped `sync_board(board=\u003Cproject or null>, board_type=\u003Ctype>,\nprovider_options=\u003Coptions>)`. This includes after any confirmed child and attempts with only\n`in_flight` state and no confirmed child keys. Capability or preflight stops explicitly before a\nwrite do not trigger this post-write verification. Then verify:\n\n1. `get_task(parent_key, project=\u003Cproject>)` contains stored links for the returned children.\n2. `get_task_context(parent_key, project=\u003Cproject>)` exposes the parent-child graph relationship.\n3. Point-read every returned child with `get_task(child_key, project=\u003Cproject>)`.\n\nWith no child keys, still complete the available parent and context verification. Report missing\nlinks, unreadable child keys, sync failures, and warnings. Complete these checks before declaring\noutcome or offering recovery; never declare complete verification from the write response alone.\nDisplay `status`, `category`, and `retryable` exactly as returned.\n\nAfter mandatory attempted-write verification, offer the exact retry only for a transport timeout\nor unknown outcome, or when `retryable is true`; still require an explicit user choice between\nexact retry and stop. If `retryable == false`, or `category` is `unsupported`, `conflict`, or\n`parent_not_found`, report the terminal result and stop without retry. Unsupported detected before\na write remains a no-write stop and does not trigger post-write verification. The recovery uses\nthe same full payload, same order, and same `idempotency_key`; never mint a key and never edit the\nrecovery payload. Exact same-key retry is the only marker reconciliation mechanism; never guess\nchildren from board search.\n\n## Quick Reference\n\n| Phase | Required invariant |\n|---|---|\n| Lookup | Absent vs explicit disable; one frozen generic snapshot; fallback only for absent |\n| Context | Attempt all three calls; report empty results; stop on tool errors |\n| Preview | Every full child; freeze payload\u002Forder\u002Fkey; edits rotate key before first write |\n| Confirm | One explicit answer for the whole visible preview; no earlier writes |\n| Write | One initial native batch; exact previewed request |\n| Retry | User chooses; retryable gate; timeout\u002Funknown or true; `unsupported`\u002F`conflict`\u002F`parent_not_found` stop |\n| Verify | Any actually attempted batch, every status: one sync and available reads before outcome\u002Frecovery |\n\n## Example\n\n```text\nПровайдер: \u003Cresolved board_type>\nРодитель: PRI-224 — Нативная декомпозиция\nКлюч идемпотентности: 6f95035e-48da-40a3-aa29-9e220182bf38\n\n1. Проверить регистрацию capability\nПроблема: Декомпозиция небезопасна без подтверждённой поддержки доски.\nЧто сделать:\n- Получать capability из registry discovery.\n- Останавливать сценарий без записи при отсутствии поддержки.\nКритерии приёмки:\n- Неподдерживаемая доска не получает дочерних задач.\n- Локально подставить capability невозможно.\nКонтекст: reviewer\u002Ftasks\u002Fboards\u002Fregistry.py:81\n\nПодтвердить создание всего показанного набора без изменений? (да\u002Fнет)\n```\n\n## Common Mistakes\n\n| Rationalization | Correction |\n|---|---|\n| “I already approve; create now” (authority\u002Furgency) | Approval cannot cover an unseen preview; show every body first. |\n| “Five individual writes are easier to recover” | They destroy atomic intent; use the one native batch only. |\n| “This provider obviously supports children” | Only authoritative capability discovery counts; never spoof it. |\n| “Search can wait until after drafting” | Run `search_codebase` and task context first or stop. |\n| “We already spent time drafting” (sunk cost) | Rework an ungrounded draft; sunk cost grants no write permission. |\n| “A timeout needs a clean new key” | Reuse the exact request and key; a fresh key can duplicate children. |\n| “Exactly one batch means retries are forbidden.” | One initial request may be repeated only as an exact user-requested recovery. |\n| “The original preview confirmation authorizes automatic retries.” | Every retry needs a new explicit user choice. |\n| “No confirmed child keys means there is nothing to verify.” | Sync and verify available parent\u002Fcontext state before retry. |\n| “A small preview edit can reuse the same key.” | Before first write, invalidate the preview and rotate the key; after an attempt, never edit. |\n| “A tool error is the same as an empty context result.” | Empty success may continue; an error stops drafting. |\n| “Only partial\u002Ftimeout outcomes need verification.” | Every attempted write is verified, including `ok`\u002F`error`; preflight no-write stops are not. |\n| “Explicitly disabled board config can use deploy fallback.” | Present disable wins; fallback is only for an absent repository key. |\n| “Any error is safe to retry with the same key.” | Retry only unknown\u002Ftimeout or `retryable=true`; terminal categories stop. |\n\n## Red Flags\n\n- Any board write before the full preview and its explicit confirmation.\n- Missing `native_subtasks` discovery or locally claimed capability.\n- Drafting without parent context, similar tasks, and relevant code.\n- Individual child writes, changed retry payload, new retry key, or guessed `in_flight` remainder.\n- English user-facing output or a success claim without post-write reads.\n- “Exactly one batch means retries are forbidden.”\n- “The original preview confirmation authorizes automatic retries.”\n- “No confirmed child keys means there is nothing to verify.”\n- “A small preview edit can reuse the same key.”\n- “A tool error is the same as an empty context result.”\n- Declaring an attempted-write outcome before its scoped sync and available reads.\n- “Only partial\u002Ftimeout outcomes need verification.”\n- “Explicitly disabled board config can use deploy fallback.”\n- “Any error is safe to retry with the same key.”\n\nAny red flag means stop the write path and return to the violated phase.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fdecompose-task",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":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill decompose-task",{"tool":50,"command":51},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill decompose-task",{"tool":53,"command":54},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill decompose-task","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fdecompose-task\u002FSKILL.md",true,[],[59,69,77,85,93,101],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":68},"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":68},"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":68},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":68},"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":68},"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":68},"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",[],[]]