[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78P2ZZJTFZQG8XK55DVXPW6":3,"skill-same:01M78P2ZZJTFZQG8XK55DVXPW6":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},"01M78P2ZZJTFZQG8XK55DVXPW6","cloudgpu",null,"Rent and use a cloud GPU on CloudGPU (cloudgpu.app) through the `cloudgpu` MCP tools. Use when the user wants to rent a GPU, run a training, fine-tuning, inference or ComfyUI job on a cloud GPU, or mentions CloudGPU or cloudgpu.app, and the `cloudgpu` MCP tools are available.","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\u002Fmrhy7176\u002Fcloudgpu-mcp\u002Fskills\u002Fcloudgpu\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cloudgpu\ndescription: Rent and use a cloud GPU on CloudGPU (cloudgpu.app) through the `cloudgpu` MCP tools. Use when the user wants to rent a GPU, run a training, fine-tuning, inference or ComfyUI job on a cloud GPU, or mentions CloudGPU or cloudgpu.app, and the `cloudgpu` MCP tools are available.\n---\n\n# CloudGPU\n\nFollow these steps whenever you rent or use a GPU on CloudGPU (cloudgpu.app) through the `cloudgpu` MCP tools.\n\n## Before renting\n\n1. Call `get_account` and `list_gpus`. Pick a GPU with enough VRAM for the job, and don't rent more GPU than the job needs. As a rough guide, LoRA on a 7–8B model fits in 24 GB, and a full fine-tune of the same model needs 80 GB or more.\n2. Check existing `list_instances` before renting. A compatible running rental can run multiple approved commands inside its original limits. Optionally compare billed task costs with `compare_compute_costs`, then call `estimate_cost` with preparation\u002Fdownload\u002Foutput time included.\n3. Show the user a short quote before you rent anything:\n   - the GPU and how many,\n   - the price per hour,\n   - the billing increment and minimum charge: some sources charge a minimum one hour and every started hour in full, with no voluntary-stop refund of unused charged time,\n   - the estimated hours and cost,\n   - the budget and time limit you will set,\n   - their balance after the job.\n4. Rent only after the user says yes. Pass `user_confirmed=true` only in that case.\n\n## Renting\n\n- Always set `max_spend_usd` and `max_hours`. CloudGPU's servers destroy the instance when either is reached, even if you have disconnected.\n- Keep `idle_minutes` on (default 60). Include setup time when agreeing limits before creation. Never silently extend the approved budget, time or idle limits.\n- Call `get_status` at intervals, not in a tight loop, until the instance is `running`.\n- On failure, inspect actual charges and release status; do not promise zero charges or automatic refunds. Do not retry creation while the result or resource release is uncertain.\n\n## Working on the instance\n\n- Put code and data on the instance with `upload`. Do not upload credentials.\n- Use `run_command` for short steps. For training, long installs or big downloads, use `background=true` and follow progress with `tail_logs`.\n- Instances come with Python and CUDA, but not always PyTorch. Check first: `nvidia-smi -L` and `python -c \"import torch; print(torch.__version__, torch.cuda.is_available())\"`.\n- If PyTorch is missing, plain `pip install torch` installs a current CUDA build. It is a few GB, so run it with `background=true`. Index URLs for older CUDA versions (for example `...\u002Fwhl\u002Fcu124`) may have no wheel for the machine's Python, which can be very new. Only use them if the project needs that CUDA version, and then create an environment with an older Python first (`conda create -y -n work python=3.12`, then `conda activate work && ...` in each command).\n- If `nvidia-smi` shows no GPU once the instance is running, stop and tell the user. CloudGPU detects such machines and shuts them down automatically.\n- **Do not** change the root password, edit the SSH configuration, change the firewall, or stop the platform's monitoring agent (`cgpu-*` processes). The platform must keep its access to the instance; if that access is lost, the platform shuts the instance down. The MCP server refuses such commands.\n- Never use the GPU for cryptocurrency mining or anything the [acceptable use policy](https:\u002F\u002Fcloudgpu.app\u002Faup) forbids. Instances that do so are shut down.\n\n## Finishing (always)\n\n1. Download every result: model weights, adapters, checkpoints, logs, metrics. Destroying an instance erases its disk. Workspace persists only files explicitly uploaded and ready, under its quota\u002Fretention policy. It is not an automatic disk backup. Storage fees are separate from GPU budgets.\n2. Call `stop_instance`.\n3. Tell the user what ran, where the results are on their computer, and the final cost from `stop_instance`.\n\nIf anything goes wrong mid-way, do not leave the instance running. Download whatever exists, stop the instance, then explain what happened.\n\n## Balance and top-ups\n\n- If `get_account` or `estimate_cost` shows the balance would not cover the quoted job, do not call `create_instance`. Tell the user how much is missing and ask them to top up at https:\u002F\u002Fcloudgpu.app\u002Fbilling (card or USDT). When they say it is done, call `estimate_cost` again before renting.\n- `create_instance` also checks the balance. If it is below the estimate or budget plus 10%, the MCP server does not rent anything and returns an error that starts with `Not rented: balance $... is below $...` and points to https:\u002F\u002Fcloudgpu.app\u002Fbilling. If the CloudGPU API itself rejects the request with HTTP status 402, the error reads `CloudGPU API error 402 \u003Ccode>: \u003Cmessage>` followed by the same billing link. Handle both the same way as above: stop, tell the user how much is missing, and do not retry.\n- Never top up, enter card details or move money on the user's behalf. The user does that themselves on the billing page.\n\n## Checking prices without the MCP server\n\nIf the `cloudgpu` tools are not available, read current prices from https:\u002F\u002Fcloudgpu.app\u002Fgpu-prices.json (machine-readable, with an `updated_at` field) or https:\u002F\u002Fcloudgpu.app\u002Fpricing. Check `updated_at` and tell the user how fresh the data is. Do not quote prices from memory.\n\n## Optional persistence\n\nDiscover tools and `GET \u002Fv1\u002Fpublic\u002Fcompute-capabilities` first. Persistence is\nunavailable when that endpoint is missing or `storage` is false. Never promise\nfree storage, a retention period or automatic output collection.\n\nWhen enabled, ask before saving private project files. Use `save_workspace` for\nregular source\u002Fconfig\u002Fdependency-manifest files, `upload_artifact` for persistent\nresults or datasets\u002Fmodels, and `download_artifact` to retrieve them. Pass the\nsaved `workspace_version_id` to `run_job` to restore the files before execution.\nThe service does not restore a boot disk and does not automatically save edits;\nthe Job command must still save its results before shutdown. Do not upload secrets.\n\nFor Jobs, prefer `quote_compute` for a server quote and send its `quote_id` with\nthe chosen candidate. Its `required_starting_balance` is separate from the task\nestimate. The original `estimate_cost` quote belongs to `create_instance`.\n\n## Only need a model, not a GPU?\n\nThe same API key works for CloudGPU's model API at `https:\u002F\u002Fcloudgpu.app\u002Fv1`. Call `list_models` to see the models. If you only need inference on a hosted model, use the API instead of renting a GPU.\n\n## If the MCP server is not installed\n\nIf no `cloudgpu` tools are available, the MCP server needs to be set up first:\n\n- Command: `npx -y cloudgpu-mcp`\n- Environment variable: `CLOUDGPU_API_KEY`, with a key created at https:\u002F\u002Fcloudgpu.app.\n- Never paste the key into the chat or into files in the project. Ask the user to put it in their MCP client's configuration or environment themselves.\n\nSee the [README](https:\u002F\u002Fgithub.com\u002Fcloudgpu-app\u002Fcloudgpu-mcp#install) for per-client setup.\n\n## Jobs and instance reuse\n\nSequential approved `run_command` calls may reuse a running rental within its original budget, deadline and idle limit. Check ownership, readiness and free memory\u002Fdisk first. Independent `run_job` calls and `prepare_job_rerun` provision separately, not into that live rental. Job\u002Ftemplate support is configuration-specific; inspect `supports_jobs` and obtain a Job quote, never substitute the rental quote. Do not keep an idle GPU merely to consume a prepaid hour. Confirm result persistence and release when finished.\n\n## Connect with an approval link\n\nIn a configured MCP client, call `connect_account`, show the owner its link, then `finish_connect` after approval. No password or API key is pasted in chat. The link grants scoped access; it does not automatically install an MCP server in arbitrary AI products.\n\n## Several steps on one allocation\n\nIf installed, `prepare_task_pipeline` prepares up to eight reviewed sequential commands for one Job, or for `run_command` on an approved existing rental. It creates nothing. Commands share the filesystem and GPU but use separate shells; they do not share exported shell variables or a resident model process. Failure stops later steps. Python 3, bash and prepared dependencies are required. Review the returned command, obtain a compatible quote and explicit total budget\u002Fdeadline approval, then submit one Job with a stable idempotency key. Preserve the original request on a lost response. The fingerprint is informational, not approval. Optional collection saves only pipeline-summary.json, never arbitrary results or logs; approve actual result persistence separately. Existing user instance limits and lifecycle remain unchanged.\n","# CloudGPU\n\nFollow these steps whenever you rent or use a GPU on CloudGPU (cloudgpu.app) through the `cloudgpu` MCP tools.\n\n## Before renting\n\n1. Call `get_account` and `list_gpus`. Pick a GPU with enough VRAM for the job, and don't rent more GPU than the job needs. As a rough guide, LoRA on a 7–8B model fits in 24 GB, and a full fine-tune of the same model needs 80 GB or more.\n2. Check existing `list_instances` before renting. A compatible running rental can run multiple approved commands inside its original limits. Optionally compare billed task costs with `compare_compute_costs`, then call `estimate_cost` with preparation\u002Fdownload\u002Foutput time included.\n3. Show the user a short quote before you rent anything:\n   - the GPU and how many,\n   - the price per hour,\n   - the billing increment and minimum charge: some sources charge a minimum one hour and every started hour in full, with no voluntary-stop refund of unused charged time,\n   - the estimated hours and cost,\n   - the budget and time limit you will set,\n   - their balance after the job.\n4. Rent only after the user says yes. Pass `user_confirmed=true` only in that case.\n\n## Renting\n\n- Always set `max_spend_usd` and `max_hours`. CloudGPU's servers destroy the instance when either is reached, even if you have disconnected.\n- Keep `idle_minutes` on (default 60). Include setup time when agreeing limits before creation. Never silently extend the approved budget, time or idle limits.\n- Call `get_status` at intervals, not in a tight loop, until the instance is `running`.\n- On failure, inspect actual charges and release status; do not promise zero charges or automatic refunds. Do not retry creation while the result or resource release is uncertain.\n\n## Working on the instance\n\n- Put code and data on the instance with `upload`. Do not upload credentials.\n- Use `run_command` for short steps. For training, long installs or big downloads, use `background=true` and follow progress with `tail_logs`.\n- Instances come with Python and CUDA, but not always PyTorch. Check first: `nvidia-smi -L` and `python -c \"import torch; print(torch.__version__, torch.cuda.is_available())\"`.\n- If PyTorch is missing, plain `pip install torch` installs a current CUDA build. It is a few GB, so run it with `background=true`. Index URLs for older CUDA versions (for example `...\u002Fwhl\u002Fcu124`) may have no wheel for the machine's Python, which can be very new. Only use them if the project needs that CUDA version, and then create an environment with an older Python first (`conda create -y -n work python=3.12`, then `conda activate work && ...` in each command).\n- If `nvidia-smi` shows no GPU once the instance is running, stop and tell the user. CloudGPU detects such machines and shuts them down automatically.\n- **Do not** change the root password, edit the SSH configuration, change the firewall, or stop the platform's monitoring agent (`cgpu-*` processes). The platform must keep its access to the instance; if that access is lost, the platform shuts the instance down. The MCP server refuses such commands.\n- Never use the GPU for cryptocurrency mining or anything the [acceptable use policy](https:\u002F\u002Fcloudgpu.app\u002Faup) forbids. Instances that do so are shut down.\n\n## Finishing (always)\n\n1. Download every result: model weights, adapters, checkpoints, logs, metrics. Destroying an instance erases its disk. Workspace persists only files explicitly uploaded and ready, under its quota\u002Fretention policy. It is not an automatic disk backup. Storage fees are separate from GPU budgets.\n2. Call `stop_instance`.\n3. Tell the user what ran, where the results are on their computer, and the final cost from `stop_instance`.\n\nIf anything goes wrong mid-way, do not leave the instance running. Download whatever exists, stop the instance, then explain what happened.\n\n## Balance and top-ups\n\n- If `get_account` or `estimate_cost` shows the balance would not cover the quoted job, do not call `create_instance`. Tell the user how much is missing and ask them to top up at https:\u002F\u002Fcloudgpu.app\u002Fbilling (card or USDT). When they say it is done, call `estimate_cost` again before renting.\n- `create_instance` also checks the balance. If it is below the estimate or budget plus 10%, the MCP server does not rent anything and returns an error that starts with `Not rented: balance $... is below $...` and points to https:\u002F\u002Fcloudgpu.app\u002Fbilling. If the CloudGPU API itself rejects the request with HTTP status 402, the error reads `CloudGPU API error 402 \u003Ccode>: \u003Cmessage>` followed by the same billing link. Handle both the same way as above: stop, tell the user how much is missing, and do not retry.\n- Never top up, enter card details or move money on the user's behalf. The user does that themselves on the billing page.\n\n## Checking prices without the MCP server\n\nIf the `cloudgpu` tools are not available, read current prices from https:\u002F\u002Fcloudgpu.app\u002Fgpu-prices.json (machine-readable, with an `updated_at` field) or https:\u002F\u002Fcloudgpu.app\u002Fpricing. Check `updated_at` and tell the user how fresh the data is. Do not quote prices from memory.\n\n## Optional persistence\n\nDiscover tools and `GET \u002Fv1\u002Fpublic\u002Fcompute-capabilities` first. Persistence is\nunavailable when that endpoint is missing or `storage` is false. Never promise\nfree storage, a retention period or automatic output collection.\n\nWhen enabled, ask before saving private project files. Use `save_workspace` for\nregular source\u002Fconfig\u002Fdependency-manifest files, `upload_artifact` for persistent\nresults or datasets\u002Fmodels, and `download_artifact` to retrieve them. Pass the\nsaved `workspace_version_id` to `run_job` to restore the files before execution.\nThe service does not restore a boot disk and does not automatically save edits;\nthe Job command must still save its results before shutdown. Do not upload secrets.\n\nFor Jobs, prefer `quote_compute` for a server quote and send its `quote_id` with\nthe chosen candidate. Its `required_starting_balance` is separate from the task\nestimate. The original `estimate_cost` quote belongs to `create_instance`.\n\n## Only need a model, not a GPU?\n\nThe same API key works for CloudGPU's model API at `https:\u002F\u002Fcloudgpu.app\u002Fv1`. Call `list_models` to see the models. If you only need inference on a hosted model, use the API instead of renting a GPU.\n\n## If the MCP server is not installed\n\nIf no `cloudgpu` tools are available, the MCP server needs to be set up first:\n\n- Command: `npx -y cloudgpu-mcp`\n- Environment variable: `CLOUDGPU_API_KEY`, with a key created at https:\u002F\u002Fcloudgpu.app.\n- Never paste the key into the chat or into files in the project. Ask the user to put it in their MCP client's configuration or environment themselves.\n\nSee the [README](https:\u002F\u002Fgithub.com\u002Fcloudgpu-app\u002Fcloudgpu-mcp#install) for per-client setup.\n\n## Jobs and instance reuse\n\nSequential approved `run_command` calls may reuse a running rental within its original budget, deadline and idle limit. Check ownership, readiness and free memory\u002Fdisk first. Independent `run_job` calls and `prepare_job_rerun` provision separately, not into that live rental. Job\u002Ftemplate support is configuration-specific; inspect `supports_jobs` and obtain a Job quote, never substitute the rental quote. Do not keep an idle GPU merely to consume a prepaid hour. Confirm result persistence and release when finished.\n\n## Connect with an approval link\n\nIn a configured MCP client, call `connect_account`, show the owner its link, then `finish_connect` after approval. No password or API key is pasted in chat. The link grants scoped access; it does not automatically install an MCP server in arbitrary AI products.\n\n## Several steps on one allocation\n\nIf installed, `prepare_task_pipeline` prepares up to eight reviewed sequential commands for one Job, or for `run_command` on an approved existing rental. It creates nothing. Commands share the filesystem and GPU but use separate shells; they do not share exported shell variables or a resident model process. Failure stops later steps. Python 3, bash and prepared dependencies are required. Review the returned command, obtain a compatible quote and explicit total budget\u002Fdeadline approval, then submit one Job with a stable idempotency key. Preserve the original request on a lost response. The fingerprint is informational, not approval. Optional collection saves only pipeline-summary.json, never arbitrary results or logs; approve actual result persistence separately. Existing user instance limits and lifecycle remain unchanged.\n",{"name":5,"description":7},"main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fmrhy7176\u002Fcloudgpu-mcp\u002Fskills\u002Fcloudgpu",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 cloudgpu",{"tool":40,"command":41},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cloudgpu",{"tool":43,"command":44},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cloudgpu","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmrhy7176\u002Fcloudgpu-mcp\u002Fskills\u002Fcloudgpu\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",[],[]]