[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78P0N4179XMPXJFRXB2XGQ7":3,"skill-same:01M78P0N4179XMPXJFRXB2XGQ7":48},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M78P0N4179XMPXJFRXB2XGQ7","bulkhead",null,"How to work on a machine where other coding agent sessions (Claude Code, Copilot CLI, Codex and others) and their subagents run at the same time. Use before starting a dev server, stopping or killing a process, freeing a port, running a build, test suite, browser run or other heavy command, switching branches, stashing, staging or committing, deleting a folder or worktree, measuring disk usage, or waiting on a long job.","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\u002Fdooly6276\u002Fclaude-bulkhead\u002Fskills\u002Fbulkhead\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bulkhead\ndescription: How to work on a machine where other coding agent sessions (Claude Code, Copilot CLI, Codex and others) and their subagents run at the same time. Use before starting a dev server, stopping or killing a process, freeing a port, running a build, test suite, browser run or other heavy command, switching branches, stashing, staging or committing, deleting a folder or worktree, measuring disk usage, or waiting on a long job.\n---\n\n# Working on a shared machine\n\nOther agent sessions (Claude Code, Copilot CLI, Codex and others), their subagents and the user run on this machine too. Their dev servers, test runs and git trees look like yours from a shell. The bulkhead hooks block the most damaging mistakes; this is how to avoid hitting them at all.\n\n## Running the bulkhead commands\n\nThe commands below (`bulkhead`, `bulkhead-slot`) are on `PATH` with the Claude Code plugin or after `npm install -g claude-bulkhead`. A Copilot CLI plugin install does not put them on `PATH`. If `bulkhead` is not found, run the same command with `node` from the plugin folder, which is two levels above this skill's folder (`\u003Cplugin>\u002Fskills\u002Fbulkhead\u002F`):\n\n```\nnode \"\u003Cplugin>\u002Fbin\u002Fbulkhead\" status\nnode \"\u003Cplugin>\u002Fbin\u002Fbulkhead-slot\" run --gb=4 -- npm test\n```\n\nCopilot CLI keeps plugins under `~\u002F.copilot\u002Finstalled-plugins\u002F\u003Cmarketplace>\u002Fbulkhead` (`$COPILOT_HOME` instead of `~\u002F.copilot` when it is set). Do not install anything to get the command; the hooks work without it.\n\n## Look before you act\n\nRun `bulkhead status` before you start a server, stop a process or start heavy work. It lists every agent session with its project, memory, listening ports, the heavy jobs queued in bulkhead-slot, and free RAM.\n\n## Dev servers and ports\n\n- A port listed under another session belongs to that session. Do not stop its server and do not start yours on the same port.\n- Get a free port with `bulkhead port --near 3000` and pass it explicitly, for example `npm run dev -- --port $(bulkhead port --near 3000)`.\n- Next.js and Vite move to the next port on their own when theirs is taken. Read the port the server prints instead of assuming the default.\n- Start long-running servers in the background (`run_in_background: true` in Claude Code, an async or detached shell in Copilot CLI), and stop them when you are done.\n\n## Stopping processes\n\n- Stop only processes you started, by PID. Never by program name: `taskkill \u002FIM node.exe`, `pkill node`, `killall python` and `Stop-Process -Name node` stop every session's processes, and can end your own session.\n- Find the PID by port (`netstat -ano | findstr :\u003Cport>` on Windows, `lsof -ti :\u003Cport>` elsewhere) or by your project path (`pgrep -af '\u003Cproject dir>'`, or `Get-CimInstance Win32_Process` filtered on `CommandLine`). Check that it is yours before stopping it.\n- Then `taskkill \u002FPID \u003Cpid> \u002FT \u002FF` on Windows, `kill \u003Cpid>` elsewhere.\n- Kills by port (`npx kill-port`, `fuser -k`, `lsof -ti :N | xargs kill`) are blocked when another session owns that port.\n\n## When the session ends\n\nIn Claude Code, servers, test runners and their workers, watchers, builds and headless browsers you start from the Bash tool are stopped by orphan-reaper a few seconds after the session exits. `bulkhead reap --dry-run` lists what sessions that already exited left running.\n\nIn Copilot CLI and the other agents nothing is stopped for you when the session ends. Before you finish, stop every server, watcher and browser you started, by PID, unless the user asked to keep it running; tell them which ones are still running and on which port.\n\nIn either case, do not promise the user that a server will keep running after the session; if they want that, they should start it in their own terminal.\n\n## Heavy commands\n\nBuilds, full test suites, type checks of large projects, browser automation, emulators and Docker builds can use several GB each. Queue them so sessions take turns instead of freezing the machine:\n\n```\nbulkhead-slot run --gb=4 -- npx playwright test\n```\n\n`--gb` is the job's honest peak size: about 4 for browser suites, `next build` or an emulator, 3 for a dev server or a 4-worker test run, 2 for one type check. The command waits until there is room, runs, and frees the slot when it exits; its exit code passes through. `bulkhead-slot status` shows who holds slots. Never edit, touch or delete slot files by hand. Limit workers (`--maxWorkers=2`, one browser) when memory is tight.\n\n### On another machine\n\nIf `bulkhead remote list` shows a remote, a heavy job can run there instead and use none of this machine's RAM. It sends this project's code to another machine, so it never runs on your own decision, even when free RAM is low or memory-guard blocked the command. Suggest it, and run it only after the user says yes to that run:\n\n1. Run `git log -1 --oneline` and `git status --short`, then tell the user in a few lines: the remote it goes to, that the current commit (only commits the remote lacks) and every uncommitted change listed, deletions included, are sent over SSH, any ignored file you would add with `--files`, and the command it runs there.\n2. Ask whether to go ahead and end your turn. If they say no, send nothing and run the job here through bulkhead-slot. A yes covers that one run, not later ones, and not files or commands you did not name.\n3. Once they agree:\n\n```\nbulkhead remote run --tail=60 --gb=4 -- npx playwright test\n```\n\n- Run it with `run_in_background: true` and end your turn. Its exit code is the command's, and `--tail=60` keeps the output to the last 60 lines plus the path of the full log.\n- It sends the current commit and the uncommitted changes. An ignored file goes only with `--files=\u003Cpath>`, and only one the user named or agreed to in step 1. Never add an env or secrets file on your own.\n- A server the command starts must listen on `$BULKHEAD_PORT`, not a fixed port: other runs use the same remote. Everything the command started is stopped when it ends.\n- Reports and screenshots stay on the remote. Bring them back with `--fetch=playwright-report` on the run, or `bulkhead remote fetch playwright-report` afterwards.\n- Exit 3 means no free copy or RAM there in time, 4 a transfer or setup problem, 5 an unreachable remote. Then tell the user and run it here through bulkhead-slot instead.\n\n## Waiting\n\nDo not sit in a foreground loop waiting for a long job: the session cannot do anything else meanwhile, and long foreground sleeps are blocked. In Claude Code, run the wait with `run_in_background: true` and end your turn; you are notified when it exits. In other agents, start the job in the background and check its output or exit status later. A command ending in `&` also returns at once.\n\n## Git trees\n\nWhen another session works in the same checkout, `git checkout`, `switch`, `stash`, `reset --hard`, `clean -f`, `rebase` and `merge` change its files under it. Work in your own worktree: `git worktree add ..\u002F\u003Crepo>-\u003Ctask> -b \u003Cbranch>`.\n\n- Commit only the files you changed, by name: `git add src\u002Fa.ts src\u002Fb.ts` or `git commit -m \"...\" -- src\u002Fa.ts`. In a shared checkout `git add -A`, `git add .` and `git commit -a` also take the other session's half-finished edits.\n- Never delete a folder or worktree another session works in. `bulkhead status` lists each session's project folder. When cleaning up worktrees, remove only the ones you created and that no live session uses.\n- Commit as the user's git identity. Do not set `user.name` or `user.email`, and do not pass `--author`; a `Co-Authored-By` line in the message is the place for the agent.\n\n## Disk\n\nThe disk is shared too. Measure one folder at a time in the foreground (`du -sh node_modules`), starting from the folders you suspect. Never size or `find` the whole drive or home folder, and never run several scans at once (`xargs -P`, `parallel`, `&` in a loop): the disk sits at 100% and every session stalls. Use `find \u003Cfolder> -maxdepth 3`, `git ls-files`, `mdfind` or `locate` to find a file.\n\n## When a guard blocks you\n\nRead the message: it names the other session and what to do instead. Do not work around it by splitting, encoding or hiding the command. If the block is wrong for this project, tell the user which setting would allow it (`bulkhead config` lists them, for example `killGuard.allowNames` or `portGuard.ignorePorts`). Settings that loosen a guard are read from the user's global config file only; a project's `.claude\u002Fbulkhead.json` can only make the guards stricter. `bulkhead log` shows what was blocked.\n","# Working on a shared machine\n\nOther agent sessions (Claude Code, Copilot CLI, Codex and others), their subagents and the user run on this machine too. Their dev servers, test runs and git trees look like yours from a shell. The bulkhead hooks block the most damaging mistakes; this is how to avoid hitting them at all.\n\n## Running the bulkhead commands\n\nThe commands below (`bulkhead`, `bulkhead-slot`) are on `PATH` with the Claude Code plugin or after `npm install -g claude-bulkhead`. A Copilot CLI plugin install does not put them on `PATH`. If `bulkhead` is not found, run the same command with `node` from the plugin folder, which is two levels above this skill's folder (`\u003Cplugin>\u002Fskills\u002Fbulkhead\u002F`):\n\n```\nnode \"\u003Cplugin>\u002Fbin\u002Fbulkhead\" status\nnode \"\u003Cplugin>\u002Fbin\u002Fbulkhead-slot\" run --gb=4 -- npm test\n```\n\nCopilot CLI keeps plugins under `~\u002F.copilot\u002Finstalled-plugins\u002F\u003Cmarketplace>\u002Fbulkhead` (`$COPILOT_HOME` instead of `~\u002F.copilot` when it is set). Do not install anything to get the command; the hooks work without it.\n\n## Look before you act\n\nRun `bulkhead status` before you start a server, stop a process or start heavy work. It lists every agent session with its project, memory, listening ports, the heavy jobs queued in bulkhead-slot, and free RAM.\n\n## Dev servers and ports\n\n- A port listed under another session belongs to that session. Do not stop its server and do not start yours on the same port.\n- Get a free port with `bulkhead port --near 3000` and pass it explicitly, for example `npm run dev -- --port $(bulkhead port --near 3000)`.\n- Next.js and Vite move to the next port on their own when theirs is taken. Read the port the server prints instead of assuming the default.\n- Start long-running servers in the background (`run_in_background: true` in Claude Code, an async or detached shell in Copilot CLI), and stop them when you are done.\n\n## Stopping processes\n\n- Stop only processes you started, by PID. Never by program name: `taskkill \u002FIM node.exe`, `pkill node`, `killall python` and `Stop-Process -Name node` stop every session's processes, and can end your own session.\n- Find the PID by port (`netstat -ano | findstr :\u003Cport>` on Windows, `lsof -ti :\u003Cport>` elsewhere) or by your project path (`pgrep -af '\u003Cproject dir>'`, or `Get-CimInstance Win32_Process` filtered on `CommandLine`). Check that it is yours before stopping it.\n- Then `taskkill \u002FPID \u003Cpid> \u002FT \u002FF` on Windows, `kill \u003Cpid>` elsewhere.\n- Kills by port (`npx kill-port`, `fuser -k`, `lsof -ti :N | xargs kill`) are blocked when another session owns that port.\n\n## When the session ends\n\nIn Claude Code, servers, test runners and their workers, watchers, builds and headless browsers you start from the Bash tool are stopped by orphan-reaper a few seconds after the session exits. `bulkhead reap --dry-run` lists what sessions that already exited left running.\n\nIn Copilot CLI and the other agents nothing is stopped for you when the session ends. Before you finish, stop every server, watcher and browser you started, by PID, unless the user asked to keep it running; tell them which ones are still running and on which port.\n\nIn either case, do not promise the user that a server will keep running after the session; if they want that, they should start it in their own terminal.\n\n## Heavy commands\n\nBuilds, full test suites, type checks of large projects, browser automation, emulators and Docker builds can use several GB each. Queue them so sessions take turns instead of freezing the machine:\n\n```\nbulkhead-slot run --gb=4 -- npx playwright test\n```\n\n`--gb` is the job's honest peak size: about 4 for browser suites, `next build` or an emulator, 3 for a dev server or a 4-worker test run, 2 for one type check. The command waits until there is room, runs, and frees the slot when it exits; its exit code passes through. `bulkhead-slot status` shows who holds slots. Never edit, touch or delete slot files by hand. Limit workers (`--maxWorkers=2`, one browser) when memory is tight.\n\n### On another machine\n\nIf `bulkhead remote list` shows a remote, a heavy job can run there instead and use none of this machine's RAM. It sends this project's code to another machine, so it never runs on your own decision, even when free RAM is low or memory-guard blocked the command. Suggest it, and run it only after the user says yes to that run:\n\n1. Run `git log -1 --oneline` and `git status --short`, then tell the user in a few lines: the remote it goes to, that the current commit (only commits the remote lacks) and every uncommitted change listed, deletions included, are sent over SSH, any ignored file you would add with `--files`, and the command it runs there.\n2. Ask whether to go ahead and end your turn. If they say no, send nothing and run the job here through bulkhead-slot. A yes covers that one run, not later ones, and not files or commands you did not name.\n3. Once they agree:\n\n```\nbulkhead remote run --tail=60 --gb=4 -- npx playwright test\n```\n\n- Run it with `run_in_background: true` and end your turn. Its exit code is the command's, and `--tail=60` keeps the output to the last 60 lines plus the path of the full log.\n- It sends the current commit and the uncommitted changes. An ignored file goes only with `--files=\u003Cpath>`, and only one the user named or agreed to in step 1. Never add an env or secrets file on your own.\n- A server the command starts must listen on `$BULKHEAD_PORT`, not a fixed port: other runs use the same remote. Everything the command started is stopped when it ends.\n- Reports and screenshots stay on the remote. Bring them back with `--fetch=playwright-report` on the run, or `bulkhead remote fetch playwright-report` afterwards.\n- Exit 3 means no free copy or RAM there in time, 4 a transfer or setup problem, 5 an unreachable remote. Then tell the user and run it here through bulkhead-slot instead.\n\n## Waiting\n\nDo not sit in a foreground loop waiting for a long job: the session cannot do anything else meanwhile, and long foreground sleeps are blocked. In Claude Code, run the wait with `run_in_background: true` and end your turn; you are notified when it exits. In other agents, start the job in the background and check its output or exit status later. A command ending in `&` also returns at once.\n\n## Git trees\n\nWhen another session works in the same checkout, `git checkout`, `switch`, `stash`, `reset --hard`, `clean -f`, `rebase` and `merge` change its files under it. Work in your own worktree: `git worktree add ..\u002F\u003Crepo>-\u003Ctask> -b \u003Cbranch>`.\n\n- Commit only the files you changed, by name: `git add src\u002Fa.ts src\u002Fb.ts` or `git commit -m \"...\" -- src\u002Fa.ts`. In a shared checkout `git add -A`, `git add .` and `git commit -a` also take the other session's half-finished edits.\n- Never delete a folder or worktree another session works in. `bulkhead status` lists each session's project folder. When cleaning up worktrees, remove only the ones you created and that no live session uses.\n- Commit as the user's git identity. Do not set `user.name` or `user.email`, and do not pass `--author`; a `Co-Authored-By` line in the message is the place for the agent.\n\n## Disk\n\nThe disk is shared too. Measure one folder at a time in the foreground (`du -sh node_modules`), starting from the folders you suspect. Never size or `find` the whole drive or home folder, and never run several scans at once (`xargs -P`, `parallel`, `&` in a loop): the disk sits at 100% and every session stalls. Use `find \u003Cfolder> -maxdepth 3`, `git ls-files`, `mdfind` or `locate` to find a file.\n\n## When a guard blocks you\n\nRead the message: it names the other session and what to do instead. Do not work around it by splitting, encoding or hiding the command. If the block is wrong for this project, tell the user which setting would allow it (`bulkhead config` lists them, for example `killGuard.allowNames` or `portGuard.ignorePorts`). Settings that loosen a guard are read from the user's global config file only; a project's `.claude\u002Fbulkhead.json` can only make the guards stricter. `bulkhead log` shows what was blocked.\n",{"name":5,"description":7},"main","2a6d24be2ed571c5ff2319c506b60741bbcb1cb0","plugins\u002Fdooly6276\u002Fclaude-bulkhead\u002Fskills\u002Fbulkhead",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill bulkhead",{"tool":40,"command":41},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill bulkhead",{"tool":43,"command":44},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill bulkhead","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdooly6276\u002Fclaude-bulkhead\u002Fskills\u002Fbulkhead\u002FSKILL.md",true,[],[49,58,66,74,82,90],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":54,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"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",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"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",[],[]]