[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJGWFTHCTTKXW1YGV7TS0P":3,"skill-same:01M6MJGWFTHCTTKXW1YGV7TS0P":93},{"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":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6MJGWFTHCTTKXW1YGV7TS0P","solve-task",null,"Gather disciplined context for solving a task, then hand off to development. Use when the user asks to solve\u002Fimplement a task (\"solve PRI-4\", \"rag-reviewer:solve-task \u003Ckey or description>\", \"реши задачу X\"). Reads a keyed task from the reviewer store, pulls related\u002Fsimilar tasks and relevant code, distills a brief, and enters brainstorming. Requires the reviewer MCP server.","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\u002Fsolve-task\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"solve task","task","solve","user","when","gather","for","hand","relevant","store","use","MCP","reviewer","brief","server","code","development","tasks","rag","brainstorming","implement","mcp server","2026-11-10 10:12:30",false,"---\nname: solve-task\ndescription: Gather disciplined context for solving a task, then hand off to development. Use when the user asks to solve\u002Fimplement a task (\"solve PRI-4\", \"rag-reviewer:solve-task \u003Ckey or description>\", \"реши задачу X\"). Reads a keyed task from the reviewer store, pulls related\u002Fsimilar tasks and relevant code, distills a brief, and enters brainstorming. Requires the reviewer MCP server.\n---\n\n# Solve Task\n\nGather the right context for a task, distill it into a brief, then enter the normal development\nworkflow. This skill does NOT plan or implement — it disciplines context-gathering and hands the\nbrief to `superpowers:brainstorming` (which leads to writing-plans → subagent-driven-development,\nor the execution strategy chosen in the startup survey (inline \u002F subagent \u002F lite)).\n\n## Inputs\n\n`$ARGUMENTS` is either:\n- a task key (e.g. `PRI-4`, matching the board's `key_pattern`), or\n- a free-text description (e.g. \"add a logout endpoint\").\n\n## Pipeline\n\n0. **Startup: survey + Preflight (index freshness + task-corpus warm-up).** Run this BEFORE anything else.\n   First resolve, once, the repo path (`git rev-parse --show-toplevel`) and the working branch\n   (`git branch --show-current`; if it is in `REVIEW_BRANCHES` use it, else the primary branch) —\n   step 3 reuses the same branch for `search_codebase`.\n\n   **Resolve `task_board` exactly once before any board call.** Read the repo `.review.yml` block:\n   its `task_board` mapping has priority; an absent block falls back to `get_board_config()`;\n   an explicit empty `task_board:` disables board work for this run. Keep the resolved\n   `{type, project, key_pattern, create_target, done_target, options}` value and **reuse this resolved value** in Step 1 and every board operation. Never call the deploy fallback when the\n   repo explicitly disables the board.\n\n   **Call `prepare_task_context(repo, key, branch, warm_board=True)` once here** — pass the\n   resolved `key` when `$ARGUMENTS` matches `key_pattern`, else board-less: pass the user's\n   formulation verbatim as `key` (the tool's `key` parameter is required and accepts free text\n   when no board key matches). It folds\n   the manual round trips below into one deterministic call and returns a single payload:\n   `preflight` (branch, indexed_sha, drift, summaries, chunks, graph_nodes — feeds Step 0.1\u002F0.4\n   below), `task_board`\u002F`task` (feeds Step 2), `related`\u002F`subsystems`\u002F`code`\u002F`test_exemplars`\n   (feeds Step 3), `gaps` (a list of `{section, reason, cause, cause_detail, remedy}` — branch on whether\n   `cause` is `unknown`, not on one non-`unknown` value; the classes are `storage_unavailable` |\n   `embedder_unavailable`, and `cause_detail` refines `storage_unavailable` only (`auth_failed` |\n   `missing_database` | `pool_exhausted` | `null`); copy every entry into **Constraints \u002F open questions**\n   in the Step 4 brief verbatim) and `warnings` (surface to the user). No source failure raises — a failed\n   section just adds a `gaps` entry, so the steps below stay fail-open.\n\n\u003C!-- include: solve-task\u002Freferences\u002Fpreflight.md -->\n\n1. **Config.** Reuse the resolved value from preflight; do not read `.review.yml` or call\n   `get_board_config()` again. If no board resolved, continue board-less. For incomplete metadata\n   call `get_board_targets(board_type=\u003Ctask_board.type>,\n   project=\u003Ctask_board.project>, provider_options=\u003Ctask_board.options or {}>)`: select from\n   `targets` by `label`, and use option `required_for` \u002F `choices` to ask for missing `options`.\n   Never guess a target or an option and never branch on a board type.\n\n**Brief-building unit (Steps 2–4) runs on the chosen model.** Steps 2–4 (identify → gather → distill\n→ persist) are non-interactive; run them on the model chosen in the Step 0 startup survey. Dispatch\na subagent on the chosen model when a per-subagent model override is available (session-less tools +\n`Read`\u002F`Bash`\u002F`Glob`\u002F`Write` to persist the brief), passing the Step 0 `prepare_task_context` payload\ninto its dispatch prompt so it does not re-call `prepare_task_context` or the tools it already\nreplaced; otherwise build the brief inline. Details, the existing-artifacts pre-dispatch warn, the\n`Собран на:` marker line and the fail-open fallback are in `references\u002Fbrief-format.md` below.\n\n2. **Identify the task.**\n   - If `$ARGUMENTS` matches the board's `key_pattern`:\n     1. **Store-first.** Use `payload.task` from the Step 0 `prepare_task_context` call — it already\n        carries the task's own normalized content (`{key, aliases[], title, description, criteria[],\n        status, url}`) from the reviewer store, refreshed by that call's board warm-up. Call reviewer\n        `get_task(key, project=\u003Ctask_board.project>)` directly only as a fallback: when\n        `payload.task` is empty without a matching `gaps` entry explaining why, or when\n        `prepare_task_context` itself is unavailable — it returns the same normalized shape.\n        - **Hit** (a task object with a `key`, from `payload.task` or the fallback `get_task` call):\n          use it directly as the `TaskBrief`. The task is\n          already indexed (the preflight sync persisted it) — do NOT call `index_task`. Note in the\n          brief that the task data came from the reviewer store (after sync).\n          - **Thin criteria (optional, fail-open).** The store can return `criteria=[]`; requirements\n            normally live in `description`. If it has NO heading matching\n            `(?i)(критери|приёмк|acceptance)`, leave `criteria` empty and record the gap. Do NOT call `index_task`.\n        - **Miss** (`null` \u002F no `key`) AND a board is resolved: call generic incremental\n          `sync_board(board=\u003Ctask_board.project or null>, board_type=\u003Ctask_board.type>,\n          provider_options=\u003Ctask_board.options or {}>, limit=null, purge_orphaned=false)`, then\n          retry `get_task(key, project=\u003Ctask_board.project>)` once. Error or second miss →\n          board-less: treat `$ARGUMENTS` as the task description and record the gap.\n        - **Miss** AND no board: board-less — treat `$ARGUMENTS` as the task description.\n   - Otherwise: treat `$ARGUMENTS` as the task description; do not perform external task reads.\n\n   Store-first cuts the double-fetch: `prepare_task_context`'s board warm-up already pulled the whole\n   board into the reviewer store, and a miss gets one generic incremental sync\u002Fretry (fewer LLM\n   tokens and no provider-specific client dependency).\n\n3. **Gather context (best-effort, fail-open).** Any tool returning a \"(… unavailable)\" \u002F \"(ничего не\n   найдено)\" note or an error is non-fatal — continue. Details (subsystem prior, project scope,\n   related-task lookups, `search_codebase`, graph deepening, test exemplars, lazy expansion\u002FPR diff)\n   are in `references\u002Fcontext-gathering.md` below.\n\n\u003C!-- include: solve-task\u002Freferences\u002Fcontext-gathering.md -->\n\n\u003C!-- include: _common\u002Ftool-usage.md -->\nUse the session-less tools above.\n\n   **Branch selection for `search_codebase`.**\n\n\u003C!-- include: _common\u002Fbranch-selection.md -->\n\n4. **Distill the solution brief.** Write a structured markdown brief whose only job is to seed\n   `brainstorming` — compact, scannable, nothing the implementer won't act on.\n\n\u003C!-- include: solve-task\u002Freferences\u002Fbrief-format.md -->\n\n\u003C!-- include: solve-task\u002Freferences\u002Fmodes.md -->\n\n## Failure handling (fail-open)\n\n- No configured `task_board` \u002F failed generic sync \u002F task not found → board-less: build the brief\n  from `search_tasks` (if the corpus is warm) + `search_codebase` + the user's formulation; note\n  the missing task context.\n- Neo4j down → `get_task_context` \u002F `index_task` graph parts degrade (empty + warning); build the\n  brief from `search_tasks` + `search_codebase`.\n- Empty task corpus (no prior `rag-reviewer:sync-tasks` or reviews) → `search_tasks` is empty; use\n  `search_codebase` + the user's formulation and note the missing task context.\n- Postgres down → `search_codebase` \u002F `search_tasks` return empty; build the brief from the user's\n  formulation alone and note the missing task context; still hand off to brainstorming.\n- Never abort: with any gap, distill what you have, note the deficit in the brief, and still hand off\n  to brainstorming.\n- This skill reads task data only through the reviewer store and generic `sync_board`\u002Fretry. It\n  writes exactly two files: the brief under `docs\u002Fsuperpowers\u002Fbriefs\u002F` and the git-ignored\n  run-state file under `.superpowers\u002Fsolve-task\u002F`; nothing else in the repository.\n\n## Reporting a reviewer defect\n\n\u003C!-- include: _common\u002Fbug-reporting.md -->\n","# Solve Task\n\nGather the right context for a task, distill it into a brief, then enter the normal development\nworkflow. This skill does NOT plan or implement — it disciplines context-gathering and hands the\nbrief to `superpowers:brainstorming` (which leads to writing-plans → subagent-driven-development,\nor the execution strategy chosen in the startup survey (inline \u002F subagent \u002F lite)).\n\n## Inputs\n\n`$ARGUMENTS` is either:\n- a task key (e.g. `PRI-4`, matching the board's `key_pattern`), or\n- a free-text description (e.g. \"add a logout endpoint\").\n\n## Pipeline\n\n0. **Startup: survey + Preflight (index freshness + task-corpus warm-up).** Run this BEFORE anything else.\n   First resolve, once, the repo path (`git rev-parse --show-toplevel`) and the working branch\n   (`git branch --show-current`; if it is in `REVIEW_BRANCHES` use it, else the primary branch) —\n   step 3 reuses the same branch for `search_codebase`.\n\n   **Resolve `task_board` exactly once before any board call.** Read the repo `.review.yml` block:\n   its `task_board` mapping has priority; an absent block falls back to `get_board_config()`;\n   an explicit empty `task_board:` disables board work for this run. Keep the resolved\n   `{type, project, key_pattern, create_target, done_target, options}` value and **reuse this resolved value** in Step 1 and every board operation. Never call the deploy fallback when the\n   repo explicitly disables the board.\n\n   **Call `prepare_task_context(repo, key, branch, warm_board=True)` once here** — pass the\n   resolved `key` when `$ARGUMENTS` matches `key_pattern`, else board-less: pass the user's\n   formulation verbatim as `key` (the tool's `key` parameter is required and accepts free text\n   when no board key matches). It folds\n   the manual round trips below into one deterministic call and returns a single payload:\n   `preflight` (branch, indexed_sha, drift, summaries, chunks, graph_nodes — feeds Step 0.1\u002F0.4\n   below), `task_board`\u002F`task` (feeds Step 2), `related`\u002F`subsystems`\u002F`code`\u002F`test_exemplars`\n   (feeds Step 3), `gaps` (a list of `{section, reason, cause, cause_detail, remedy}` — branch on whether\n   `cause` is `unknown`, not on one non-`unknown` value; the classes are `storage_unavailable` |\n   `embedder_unavailable`, and `cause_detail` refines `storage_unavailable` only (`auth_failed` |\n   `missing_database` | `pool_exhausted` | `null`); copy every entry into **Constraints \u002F open questions**\n   in the Step 4 brief verbatim) and `warnings` (surface to the user). No source failure raises — a failed\n   section just adds a `gaps` entry, so the steps below stay fail-open.\n\n\u003C!-- include: solve-task\u002Freferences\u002Fpreflight.md -->\n\n1. **Config.** Reuse the resolved value from preflight; do not read `.review.yml` or call\n   `get_board_config()` again. If no board resolved, continue board-less. For incomplete metadata\n   call `get_board_targets(board_type=\u003Ctask_board.type>,\n   project=\u003Ctask_board.project>, provider_options=\u003Ctask_board.options or {}>)`: select from\n   `targets` by `label`, and use option `required_for` \u002F `choices` to ask for missing `options`.\n   Never guess a target or an option and never branch on a board type.\n\n**Brief-building unit (Steps 2–4) runs on the chosen model.** Steps 2–4 (identify → gather → distill\n→ persist) are non-interactive; run them on the model chosen in the Step 0 startup survey. Dispatch\na subagent on the chosen model when a per-subagent model override is available (session-less tools +\n`Read`\u002F`Bash`\u002F`Glob`\u002F`Write` to persist the brief), passing the Step 0 `prepare_task_context` payload\ninto its dispatch prompt so it does not re-call `prepare_task_context` or the tools it already\nreplaced; otherwise build the brief inline. Details, the existing-artifacts pre-dispatch warn, the\n`Собран на:` marker line and the fail-open fallback are in `references\u002Fbrief-format.md` below.\n\n2. **Identify the task.**\n   - If `$ARGUMENTS` matches the board's `key_pattern`:\n     1. **Store-first.** Use `payload.task` from the Step 0 `prepare_task_context` call — it already\n        carries the task's own normalized content (`{key, aliases[], title, description, criteria[],\n        status, url}`) from the reviewer store, refreshed by that call's board warm-up. Call reviewer\n        `get_task(key, project=\u003Ctask_board.project>)` directly only as a fallback: when\n        `payload.task` is empty without a matching `gaps` entry explaining why, or when\n        `prepare_task_context` itself is unavailable — it returns the same normalized shape.\n        - **Hit** (a task object with a `key`, from `payload.task` or the fallback `get_task` call):\n          use it directly as the `TaskBrief`. The task is\n          already indexed (the preflight sync persisted it) — do NOT call `index_task`. Note in the\n          brief that the task data came from the reviewer store (after sync).\n          - **Thin criteria (optional, fail-open).** The store can return `criteria=[]`; requirements\n            normally live in `description`. If it has NO heading matching\n            `(?i)(критери|приёмк|acceptance)`, leave `criteria` empty and record the gap. Do NOT call `index_task`.\n        - **Miss** (`null` \u002F no `key`) AND a board is resolved: call generic incremental\n          `sync_board(board=\u003Ctask_board.project or null>, board_type=\u003Ctask_board.type>,\n          provider_options=\u003Ctask_board.options or {}>, limit=null, purge_orphaned=false)`, then\n          retry `get_task(key, project=\u003Ctask_board.project>)` once. Error or second miss →\n          board-less: treat `$ARGUMENTS` as the task description and record the gap.\n        - **Miss** AND no board: board-less — treat `$ARGUMENTS` as the task description.\n   - Otherwise: treat `$ARGUMENTS` as the task description; do not perform external task reads.\n\n   Store-first cuts the double-fetch: `prepare_task_context`'s board warm-up already pulled the whole\n   board into the reviewer store, and a miss gets one generic incremental sync\u002Fretry (fewer LLM\n   tokens and no provider-specific client dependency).\n\n3. **Gather context (best-effort, fail-open).** Any tool returning a \"(… unavailable)\" \u002F \"(ничего не\n   найдено)\" note or an error is non-fatal — continue. Details (subsystem prior, project scope,\n   related-task lookups, `search_codebase`, graph deepening, test exemplars, lazy expansion\u002FPR diff)\n   are in `references\u002Fcontext-gathering.md` below.\n\n\u003C!-- include: solve-task\u002Freferences\u002Fcontext-gathering.md -->\n\n\u003C!-- include: _common\u002Ftool-usage.md -->\nUse the session-less tools above.\n\n   **Branch selection for `search_codebase`.**\n\n\u003C!-- include: _common\u002Fbranch-selection.md -->\n\n4. **Distill the solution brief.** Write a structured markdown brief whose only job is to seed\n   `brainstorming` — compact, scannable, nothing the implementer won't act on.\n\n\u003C!-- include: solve-task\u002Freferences\u002Fbrief-format.md -->\n\n\u003C!-- include: solve-task\u002Freferences\u002Fmodes.md -->\n\n## Failure handling (fail-open)\n\n- No configured `task_board` \u002F failed generic sync \u002F task not found → board-less: build the brief\n  from `search_tasks` (if the corpus is warm) + `search_codebase` + the user's formulation; note\n  the missing task context.\n- Neo4j down → `get_task_context` \u002F `index_task` graph parts degrade (empty + warning); build the\n  brief from `search_tasks` + `search_codebase`.\n- Empty task corpus (no prior `rag-reviewer:sync-tasks` or reviews) → `search_tasks` is empty; use\n  `search_codebase` + the user's formulation and note the missing task context.\n- Postgres down → `search_codebase` \u002F `search_tasks` return empty; build the brief from the user's\n  formulation alone and note the missing task context; still hand off to brainstorming.\n- Never abort: with any gap, distill what you have, note the deficit in the brief, and still hand off\n  to brainstorming.\n- This skill reads task data only through the reviewer store and generic `sync_board`\u002Fretry. It\n  writes exactly two files: the brief under `docs\u002Fsuperpowers\u002Fbriefs\u002F` and the git-ignored\n  run-state file under `.superpowers\u002Fsolve-task\u002F`; nothing else in the repository.\n\n## Reporting a reviewer defect\n\n\u003C!-- include: _common\u002Fbug-reporting.md -->\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill solve-task",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill solve-task",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill solve-task","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-task\u002FSKILL.md",true,[75,81,85,89],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fbrief-format.md","REFERENCE","参考文档",8541,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-task\u002Freferences\u002Fbrief-format.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fcontext-gathering.md",7681,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-task\u002Freferences\u002Fcontext-gathering.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fmodes.md",6747,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-task\u002Freferences\u002Fmodes.md",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fpreflight.md",14272,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-task\u002Freferences\u002Fpreflight.md",[94,104,112,120,128,136],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":103},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":103},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":103},"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":103},"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":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":103},"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":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":140,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":103},"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",[],[]]