[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVST55RZF5S9NHYZCY05N6":3,"skill-same:01M6JVST55RZF5S9NHYZCY05N6":67},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6JVST55RZF5S9NHYZCY05N6","using-git-worktrees",null,"Use when a coding task needs a concurrent checkout, unrelated dirty state blocks safe branch switching, or the user or repository explicitly requires a worktree.","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\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"using git worktrees","Using git","worktrees","git worktrees","git","worktree","repository","coding","branch","user","state","use","unrelated","task","switching","checkout","safe","blocks","when","2026-11-10 10:12:30",false,"---\nname: using-git-worktrees\ndescription: \"Use when a coding task needs a concurrent checkout, unrelated dirty state blocks safe branch switching, or the user or repository explicitly requires a worktree.\"\n---\n\n# Using Git Worktrees\n\n## Overview\n\nA worktree is an exception for simultaneously checking out another Git history,\nnot a general safety badge. Prefer the current workspace and reuse an existing\nsuitable worktree. A branch decision and a worktree decision are separate.\n\n**Core principle:** create only with necessity and ownership evidence; pair every\ncreated worktree with a cleanup path.\n\n**Announce at start:** explain which concrete checkout conflict requires a\nworktree.\n\n## Step 0: Environment Detection\n\nBefore mutation, record the repository root, `HEAD`, branch\u002Fdetached state,\nstaged\u002Funstaged\u002Funtracked paths, active Git operations, and:\n\n```bash\ngit worktree list --porcelain\n```\n\nClassify the current host surface's task\u002Fchat-bound managed workspace semantics\nas `managed`, `non-managed`, or `unknown`. Use trusted host\u002Fsession context, an\nexplicit host contract, or a host-native lifecycle result; do not infer the\nclassification from a product name, directory prefix, command-level `workdir`,\nmissing tool, or absent metadata. `non-managed` requires positive evidence that\nthe current surface lacks task-bound managed semantics. When the host exposes\nworkspace fields, record the task workspace and the command's default `cwd`\nwithout a per-command directory override.\n\nStop on unresolved conflicts, an active merge\u002Frebase\u002Fcherry-pick\u002Frevert\u002Fbisect,\nor an unexplained detached HEAD. A detached HEAD is acceptable only when\ntrusted host binding evidence identifies it as the intended state of the\ncurrent managed worktree; Codex-managed worktrees, for example, start detached\nby default. Preserve user state: no automatic stash, reset, clean, broad\nstaging, or commit.\n\nBefore deciding necessity or placement, read the smallest relevant project\n`AGENTS.md`, `CLAUDE.md`, current authority, and existing worktree convention.\nRepository policy may require or forbid isolation and owns any approved\nin-repo location; do not discover that policy after creating the checkout.\n\n## Step 1: Necessity Decision\n\nCreate at most one task-owned worktree only when one of these is true:\n\n- another branch must remain checked out while this task proceeds;\n- unrelated dirty state prevents a safe checkout in the current workspace;\n- explicit user or current repository authority requires it.\n\nTask complexity, planning, TDD, use of subagents, or a `main`\u002F`master` branch\nname is not sufficient. Same-task subagents share one workspace; do not create\nper-subagent or nested worktrees. If independent history is unnecessary, do not\ncreate a branch either.\n\nRecord: reason, branch, exact path, creating coordinator, and expected cleanup\nevent. If the owner or cleanup condition is unknown, stop before creation.\n\n## Step 2: Safe Placement\n\nUse an existing repository convention only when the target directory is already\nignored (`git check-ignore`). Never edit or commit `.gitignore` solely to host a\nworktree. If no safe in-repo convention exists, use a task-specific external\nuser-level temporary directory outside the repository. Resolve and verify the\nexact path before creation; do not target a broad home, workspace, or repo root.\n\n## Step 3: Create the Minimum Checkout\n\nPrefer reusing an existing branch carrying the same goal. Create a branch only\nwhen the approved Git lifecycle requires independent history.\n\n### Managed-host binding gate\n\nWhen the host surface declares task\u002Fchat-bound managed workspaces, use its\nnative Worktree\u002FHandoff lifecycle instead of shell creation. Reuse the current\ntask only when trusted host evidence says it is already bound to the intended\nworkspace. If the native operation creates or moves work into another task,\ncontinue only in that bound task.\n\nAfter the native lifecycle operation, or immediately when entering\u002Freusing an\nalready-bound managed workspace, and before the first task content or Git\nhistory write, read back one joint postcondition:\n\n- trusted task workspace;\n- default command `cwd` without a command-level directory override;\n- intended Git worktree root;\n- intended `HEAD` and branch\u002Fdetached state.\n\nAll four must describe the same execution environment. `git worktree list`, a\nmanaged-looking path, or a per-command `workdir` proves only part of that\npostcondition. If native creation\u002Fhandoff is unavailable, only UI-driven, or\ncannot be verified, stop before shell worktree creation or task content\u002Fhistory\nwrites and give the user the host-native re-entry action. Do not silently fall\nback on `git worktree add`.\nCompare resolved path identity using host-appropriate semantics, not raw path\nstrings. The default `cwd` may equal the worktree root or be inside it; running\nGit from that default `cwd` must resolve to the intended worktree root.\nAn intended host-managed detached HEAD satisfies the Git-state component; do\nnot create a branch merely to make that state look like a generic checkout.\n\nIf an unbound manual worktree already exists, preserve it and report its exact\npath, `HEAD`, branch, status, and ownership evidence. Dirty, untracked, or\nownership-unknown state is not auto-migrated, deleted, stashed, reset, or\noverwritten. A later commit\u002Fpatch transfer follows normal Git authorization and\nmust be verified in the new bound task before cleanup is offered.\n\n### Generic Git fallback\n\nUse the shell path below only when trusted evidence positively classifies the\ncurrent host\u002FCLI surface as `non-managed`. An `unknown` classification fails\nclosed; an absent native tool or missing binding metadata is not\ngeneric-fallback evidence.\n\n```bash\n# Existing branch\ngit worktree add \u003Cexact-path> \u003Cbranch>\n\n# New independently justified branch\ngit worktree add -b \u003Cbranch> \u003Cexact-path> \u003Cstart-point>\n```\n\nRead back `git worktree list --porcelain`, the new worktree's `HEAD`\u002Fbranch, and\nits status. Do not use force flags. A command-level `workdir` may target this\ncheckout on a generic host, but it never proves managed task binding.\n\n## Step 4: Authority-Led Setup and Baseline\n\nRead the project's install docs, lockfiles, and existing setup scripts. Run\nonly setup the project explicitly requires. Do not infer `npm install`,\n`cargo build`, `pip install`, `poetry install`, or dependency downloads merely\nfrom manifest presence.\n\nRun the smallest relevant baseline verification. If setup or tests fail, report\nthe exact failure and preserve the worktree; do not hide it by mutating unrelated\nfiles.\n\n## Step 5: Handoff and Cleanup Ownership\n\nReport the exact path, branch, start `HEAD`, baseline result, owner, and cleanup\ntrigger. The creating coordinator remains responsible until it proves cleanup\nor explicitly hands ownership off.\n\nUse `finishing-a-development-branch` after the task commit or integration\ndecision. A worktree may usually be removed while its unmerged branch remains;\nan open PR does not require a permanent checkout.\n\n## Red Flags\n\nNever:\n\n- create a worktree only because a task modifies code;\n- modify `.gitignore` merely to make worktree creation possible;\n- install dependencies blindly;\n- create one worktree per subagent;\n- treat Git readback, a path prefix, or command-level `workdir` as proof of\n  managed task binding;\n- use shell worktree creation merely because a host-native capability is\n  deferred, UI-only, or absent from the initial tool list;\n- run global prune or force cleanup as routine hygiene;\n- remove dirty, untracked, locked, user-owned, or ownership-unknown resources.\n\n## Integration\n\nCalled conditionally by planning\u002Fexecution workflows only after the necessity\ndecision. Pairs with `finishing-a-development-branch` for evidence-led cleanup.\n","# Using Git Worktrees\n\n## Overview\n\nA worktree is an exception for simultaneously checking out another Git history,\nnot a general safety badge. Prefer the current workspace and reuse an existing\nsuitable worktree. A branch decision and a worktree decision are separate.\n\n**Core principle:** create only with necessity and ownership evidence; pair every\ncreated worktree with a cleanup path.\n\n**Announce at start:** explain which concrete checkout conflict requires a\nworktree.\n\n## Step 0: Environment Detection\n\nBefore mutation, record the repository root, `HEAD`, branch\u002Fdetached state,\nstaged\u002Funstaged\u002Funtracked paths, active Git operations, and:\n\n```bash\ngit worktree list --porcelain\n```\n\nClassify the current host surface's task\u002Fchat-bound managed workspace semantics\nas `managed`, `non-managed`, or `unknown`. Use trusted host\u002Fsession context, an\nexplicit host contract, or a host-native lifecycle result; do not infer the\nclassification from a product name, directory prefix, command-level `workdir`,\nmissing tool, or absent metadata. `non-managed` requires positive evidence that\nthe current surface lacks task-bound managed semantics. When the host exposes\nworkspace fields, record the task workspace and the command's default `cwd`\nwithout a per-command directory override.\n\nStop on unresolved conflicts, an active merge\u002Frebase\u002Fcherry-pick\u002Frevert\u002Fbisect,\nor an unexplained detached HEAD. A detached HEAD is acceptable only when\ntrusted host binding evidence identifies it as the intended state of the\ncurrent managed worktree; Codex-managed worktrees, for example, start detached\nby default. Preserve user state: no automatic stash, reset, clean, broad\nstaging, or commit.\n\nBefore deciding necessity or placement, read the smallest relevant project\n`AGENTS.md`, `CLAUDE.md`, current authority, and existing worktree convention.\nRepository policy may require or forbid isolation and owns any approved\nin-repo location; do not discover that policy after creating the checkout.\n\n## Step 1: Necessity Decision\n\nCreate at most one task-owned worktree only when one of these is true:\n\n- another branch must remain checked out while this task proceeds;\n- unrelated dirty state prevents a safe checkout in the current workspace;\n- explicit user or current repository authority requires it.\n\nTask complexity, planning, TDD, use of subagents, or a `main`\u002F`master` branch\nname is not sufficient. Same-task subagents share one workspace; do not create\nper-subagent or nested worktrees. If independent history is unnecessary, do not\ncreate a branch either.\n\nRecord: reason, branch, exact path, creating coordinator, and expected cleanup\nevent. If the owner or cleanup condition is unknown, stop before creation.\n\n## Step 2: Safe Placement\n\nUse an existing repository convention only when the target directory is already\nignored (`git check-ignore`). Never edit or commit `.gitignore` solely to host a\nworktree. If no safe in-repo convention exists, use a task-specific external\nuser-level temporary directory outside the repository. Resolve and verify the\nexact path before creation; do not target a broad home, workspace, or repo root.\n\n## Step 3: Create the Minimum Checkout\n\nPrefer reusing an existing branch carrying the same goal. Create a branch only\nwhen the approved Git lifecycle requires independent history.\n\n### Managed-host binding gate\n\nWhen the host surface declares task\u002Fchat-bound managed workspaces, use its\nnative Worktree\u002FHandoff lifecycle instead of shell creation. Reuse the current\ntask only when trusted host evidence says it is already bound to the intended\nworkspace. If the native operation creates or moves work into another task,\ncontinue only in that bound task.\n\nAfter the native lifecycle operation, or immediately when entering\u002Freusing an\nalready-bound managed workspace, and before the first task content or Git\nhistory write, read back one joint postcondition:\n\n- trusted task workspace;\n- default command `cwd` without a command-level directory override;\n- intended Git worktree root;\n- intended `HEAD` and branch\u002Fdetached state.\n\nAll four must describe the same execution environment. `git worktree list`, a\nmanaged-looking path, or a per-command `workdir` proves only part of that\npostcondition. If native creation\u002Fhandoff is unavailable, only UI-driven, or\ncannot be verified, stop before shell worktree creation or task content\u002Fhistory\nwrites and give the user the host-native re-entry action. Do not silently fall\nback on `git worktree add`.\nCompare resolved path identity using host-appropriate semantics, not raw path\nstrings. The default `cwd` may equal the worktree root or be inside it; running\nGit from that default `cwd` must resolve to the intended worktree root.\nAn intended host-managed detached HEAD satisfies the Git-state component; do\nnot create a branch merely to make that state look like a generic checkout.\n\nIf an unbound manual worktree already exists, preserve it and report its exact\npath, `HEAD`, branch, status, and ownership evidence. Dirty, untracked, or\nownership-unknown state is not auto-migrated, deleted, stashed, reset, or\noverwritten. A later commit\u002Fpatch transfer follows normal Git authorization and\nmust be verified in the new bound task before cleanup is offered.\n\n### Generic Git fallback\n\nUse the shell path below only when trusted evidence positively classifies the\ncurrent host\u002FCLI surface as `non-managed`. An `unknown` classification fails\nclosed; an absent native tool or missing binding metadata is not\ngeneric-fallback evidence.\n\n```bash\n# Existing branch\ngit worktree add \u003Cexact-path> \u003Cbranch>\n\n# New independently justified branch\ngit worktree add -b \u003Cbranch> \u003Cexact-path> \u003Cstart-point>\n```\n\nRead back `git worktree list --porcelain`, the new worktree's `HEAD`\u002Fbranch, and\nits status. Do not use force flags. A command-level `workdir` may target this\ncheckout on a generic host, but it never proves managed task binding.\n\n## Step 4: Authority-Led Setup and Baseline\n\nRead the project's install docs, lockfiles, and existing setup scripts. Run\nonly setup the project explicitly requires. Do not infer `npm install`,\n`cargo build`, `pip install`, `poetry install`, or dependency downloads merely\nfrom manifest presence.\n\nRun the smallest relevant baseline verification. If setup or tests fail, report\nthe exact failure and preserve the worktree; do not hide it by mutating unrelated\nfiles.\n\n## Step 5: Handoff and Cleanup Ownership\n\nReport the exact path, branch, start `HEAD`, baseline result, owner, and cleanup\ntrigger. The creating coordinator remains responsible until it proves cleanup\nor explicitly hands ownership off.\n\nUse `finishing-a-development-branch` after the task commit or integration\ndecision. A worktree may usually be removed while its unmerged branch remains;\nan open PR does not require a permanent checkout.\n\n## Red Flags\n\nNever:\n\n- create a worktree only because a task modifies code;\n- modify `.gitignore` merely to make worktree creation possible;\n- install dependencies blindly;\n- create one worktree per subagent;\n- treat Git readback, a path prefix, or command-level `workdir` as proof of\n  managed task binding;\n- use shell worktree creation merely because a host-native capability is\n  deferred, UI-only, or absent from the initial tool list;\n- run global prune or force cleanup as routine hygiene;\n- remove dirty, untracked, locked, user-owned, or ownership-unknown resources.\n\n## Integration\n\nCalled conditionally by planning\u002Fexecution workflows only after the necessity\ndecision. Pairs with `finishing-a-development-branch` for evidence-led cleanup.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fusing-git-worktrees",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill using-git-worktrees",{"tool":59,"command":60},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill using-git-worktrees",{"tool":62,"command":63},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill using-git-worktrees","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",true,[],[68,78,86,94,102,110],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":77},"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":77},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":77},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":77},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":77},"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":77},"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",[],[]]