[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78BFV99VF4G7J58RASKF10D":3,"skill-same:01M78BFV99VF4G7J58RASKF10D":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M78BFV99VF4G7J58RASKF10D","remote-compute-ops",null,"Operate GPU and remote compute across RunPod (Pods and Serverless), Massed Compute VMs, and owned or virtual remote servers through existing bridges, SSH sessions, MCP\u002FAPI adapters, bounded polling, cost controls, and resumable lifecycle checks. Use when the user mentions RunPod, Massed Compute, a remote GPU\u002Fserver\u002FVM, SSH bridge\u002Ftunnel\u002Fbastion\u002FTailscale, training or inference on rented compute, GPU inventory, billing, or asks to minimize API\u002FSSH connections and avoid rate limits. Do not use for generic cloud architecture, local-only GPU work, or application code with no remote-resource operation.","hermes-jarvis-bot\u002Fhermes-agent-config-kit","hermes-jarvis-bot","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288284026?v=4","01M78AV3BBD4M67J3YWSQRKP1Q","01M78AV3C2SKH53E0PZMXAKTTS",1,"MIT","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Foperational\u002Fremote-compute-ops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: remote-compute-ops\ndescription: \"Operate GPU and remote compute across RunPod (Pods and Serverless), Massed Compute VMs, and owned or virtual remote servers through existing bridges, SSH sessions, MCP\u002FAPI adapters, bounded polling, cost controls, and resumable lifecycle checks. Use when the user mentions RunPod, Massed Compute, a remote GPU\u002Fserver\u002FVM, SSH bridge\u002Ftunnel\u002Fbastion\u002FTailscale, training or inference on rented compute, GPU inventory, billing, or asks to minimize API\u002FSSH connections and avoid rate limits. Do not use for generic cloud architecture, local-only GPU work, or application code with no remote-resource operation.\"\n---\n\n# Remote compute operations\n\nUse this skill as the provider-neutral workflow for remote GPU and server work. The\nprovider is an adapter, not the name of the skill: RunPod, Massed Compute, and an\nowned\u002Fvirtual server must all follow the same evidence, transport, lifecycle, and\nhandoff rules.\n\nWhen auditing this skill or designing a plan offline, do not call a provider, SSH,\nor bridge at all; state that live mode\u002Fidentity is unproven. The read-only lookup\nbelow applies only when the user explicitly asks to inspect live remote state.\n\n## Non-negotiable transport rule\n\nReuse the already-created bridge or live connection before opening a new one. The\npurpose is reliable, rate-limit-compliant operation and avoiding unnecessary\nauthentication attempts; never disguise traffic, evade a provider limit, rotate\nidentities, or bypass a ban.\n\n- Inspect the local connection registry\u002Fbridge health when one exists. A registry is\n  a coordination hint, not proof that a tunnel is alive. Resolve the existing\n  helper through `%USERPROFILE%\\\\.claude\\\\scripts\\\\conn_registry.py` on Windows or\n  `$HOME\u002F.claude\u002Fscripts\u002Fconn_registry.py` on POSIX when that file exists; if it is\n  not discoverable, report “registry unavailable” instead of guessing a path.\n- In a read-only investigation, do not create or re-register a bridge. If a live\n  route is required, allow at most one explicitly authorized health probe. Record\n  the host alias\u002Froute, registry entry age, session owner, local PID\u002Fservice or\n  control-socket metadata when available, target identity, last probe result, and\n  whether a probe was permitted; never record credentials.\n- Use one persistent provider client\u002Fsession per task phase. Group compatible\n  read-only queries and reuse keep-alive connections; do not create a client or\n  authenticate once per command.\n- The bridge probe has the stricter budget: local registry\u002Fconfig inspection is\n  network-free, but SSH\u002Ftunnel health is at most one attempt total per target and\n  phase, with no SSH retry after a timeout or connection error. The API-read retry\n  budget in [transport-safety.md](references\u002Ftransport-safety.md) does not apply to\n  that probe.\n- Batch related remote shell checks into one SSH invocation. Use\n  `ControlMaster`\u002F`ControlPersist` only after the exact route has passed a health\n  check. If multiplexing fails on the platform or bridge, do not retry it blindly:\n  use one batched command over the known working bridge.\n- Do not fan out API or SSH calls merely to reduce wall-clock time. Parallelism is\n  allowed only when the provider documents it, the connection budget allows it, and\n  the calls cannot duplicate a mutation.\n- For `429`, `503`, connection resets, or transport timeouts, stop increasing the\n  request rate. Honor `Retry-After`, use bounded exponential backoff with jitter,\n  and record the retry budget. See [transport-safety.md](references\u002Ftransport-safety.md).\n\n## Workflow\n\n### 1. Freeze the target and read the architecture\n\nBefore a remote mutation, read the repository `AGENTS.md`, provider runbook, and\nthe relevant reference. Establish:\n\n- provider and mode (RunPod Pod, RunPod Serverless, Massed VM, or owned server);\n- exact target ID\u002Fname, region, image\u002Ftemplate, job ID, and intended outcome;\n- traffic path: existing bridge, bastion, VPN\u002FTailscale, SSH host alias, proxy, or\n  provider API endpoint;\n- current checkout, deployment\u002Fsource revision, process\u002Fjob state, storage and\n  checkpoint path, and cost\u002Fburn boundary.\n\nDo not infer a live state from a stale handoff, old dashboard, or a command that\nonly proves that a process exists locally.\n\n### 2. Classify the provider mode before choosing a channel\n\nUse existing target metadata first. If the mode is unknown, make one read-only\ncontrol-plane lookup and classify it before touching SSH:\n\n- **RunPod Serverless:** endpoint\u002Fjob ID, `\u002Frun`\u002F`\u002Fstatus`\u002F`\u002Fhealth`, webhook, or\n  stream. Do not try to SSH to a Serverless job.\n- **RunPod Pod:** exact Pod ID plus a documented SSH\u002FTCP\u002FHTTP connection route and\n  exact bridge\u002Fhost alias. Use SSH only when the target is an actual Pod and the\n  route is already verified; never infer Pod identity from a generic job name.\n- **Massed VM:** instance UUID and the provider-returned SSH target, plus Massed\n  MCP for account\u002Finstance state.\n- **Owned\u002Fvirtual server:** documented host alias and existing bridge\u002Ftunnel.\n\nIf the provider or mode remains ambiguous after that one lookup, stop and report\nthe missing identity instead of opening a second kind of connection.\n\n### 3. Reconcile read-only state through the cheapest valid path\n\nPrefer this order:\n\n1. existing bridge\u002Fsession health and the shared connection registry;\n2. one batched remote probe for host, GPU, process, disk, and durable logs;\n3. one provider client session for exact inventory, billing, target, or job state;\n4. a second provider call only when the first result is incomplete or ambiguous.\n\nFor long jobs, prefer durable logs, checkpoints, job events, or a webhook over a\ntight status loop. If polling is the only supported observation path, use one\njob-specific timer with a minimum interval, a maximum deadline, a request budget,\nand terminal-state exit. Never poll every target independently from several agents.\n\n### 4. Select the provider adapter\n\nRead [provider-matrix.md](references\u002Fprovider-matrix.md) and then the provider's\nexisting detailed skill\u002Frunbook when available.\n\n- **RunPod:** use the local `runpod-gpu-ops` skill if it is installed; otherwise\n  use [provider-matrix.md](references\u002Fprovider-matrix.md) and the linked official\n  RunPod docs for account-specific images, volumes, and lifecycle. Serverless is\n  the default for scale-to-zero inference; a Pod is a persistent billed resource\n  and needs an explicit reason plus a cleanup owner. Use the returned\n  endpoint\u002Fjob\u002Fpod ID as the identity for all later calls.\n- **Massed Compute:** use the Massed MCP tools and read\n  [massed-compute-recipes.md](references\u002Fmassed-compute-recipes.md) for\n  provider-specific recipes. Prefer read-only tools first; destructive tools may\n  be absent from a read-only key by design. Keep the MCP session and reconcile\n  after any timeout before considering a retry.\n- **Owned or virtual server:** do not invent a cloud API. Reuse the verified SSH or\n  tunnel route, batch probes, inspect the actual service\u002Fprocess\u002FGPU\u002Flog state, and\n  use the host's runbook for restart or shutdown decisions.\n\n### 5. Mutate only the named resource\n\nLaunching or restarting affects cost and capacity. State the chosen target, image,\nquantity, region, expected hourly\u002Fper-job burn, checkpoint\u002Fstorage path, and stop\ncondition before executing within the user's request.\n\nTermination, deletion, key removal, volume destruction, and any action that can\nlose unrecoverable work require exact target disclosure, explicit confirmation,\nthe smallest possible scope, and post-action verification. A vague label such as\n\"the idle pod\" is not an exact target.\n\n### 6. Reconcile instead of duplicating\n\nEvery mutation must have an identity and a durable observation record. If a launch\nor restart times out, assume it may have succeeded: list\u002Fget by exact ID, name,\nclient idempotency key, or a narrow creation-time filter before retrying. Do not\nsend a second launch because the first response was lost.\n\nFor each state transition, record provider, target ID, bridge\u002Fsession used, source\nrevision, last observation timestamp, state, job\u002Fcheckpoint marker, and next\nallowed action. Do not record tokens, passwords, private keys, or full response\nbodies containing credentials.\n\n### 7. Close the loop\n\nAfter launch\u002Frestart\u002Fdeploy, verify the actual user-facing or job outcome, not only\nthat a VM is listed as `running`:\n\n- SSH\u002Fbridge reaches the intended host;\n- GPU and process are the expected ones;\n- service\u002Fjob health is ready and the first safe probe succeeds;\n- output\u002Fcheckpoint\u002Flog marker advances;\n- cost and cleanup owner are known.\n\nIf a remote action is left running, write the handoff\u002Fjournal entry and state the\nexact next observation. Do not leave a paid resource without a shutdown rule.\n\n## Gotchas\n\n- Provider rate limits are not interchangeable. RunPod publishes limits per\n  endpoint and operation; Massed Compute documents a generic 429 recovery path.\n  Always re-check the current provider page and response headers.\n- An SSH control socket can be unsupported or broken on a particular Windows or\n  ProxyCommand route. The safe fallback is one batched connection, not a storm of\n  short SSH calls and not an unverified direct route.\n- A “running” Pod can still be starting a service; a Serverless `\u002Fhealth` result is\n  not the same as a completed job. Check the service\u002Fjob marker and logs.\n- A timeout is an ambiguous mutation result. Reconcile by exact identity before\n  retrying; never rely on a fresh list alone when multiple jobs have similar names.\n- A shared connection registry can contain stale entries. Heartbeat expiry narrows\n  the candidates but cannot replace an external health probe.\n- API keys and VM passwords stay in the approved local secret store or provider\n  UI. Never copy them into this skill, a handoff, Git, or a command transcript.\n- Do not terminate a GPU merely because it is idle for one observation. Compare the\n  active task, owner, checkpoint\u002Foutput progress, and declared stop condition.\n\n## Troubleshooting\n\n- **Several agents keep opening SSH\u002FAPI sessions** -> inspect the shared connection\n  registry and active bridge, nominate one owner for the connection, batch the\n  remaining checks, and make other agents consume the durable log\u002Fheartbeat.\n- **`429` or `503`** -> stop fan-out, honor `Retry-After`, back off with jitter,\n  reduce polling frequency, and retry only idempotent reads. For an ambiguous\n  mutation, reconcile first.\n- **ControlMaster reports a socket or getsockname error** -> mark multiplexing\n  unavailable for that route, use the verified bridge with one batched command, and\n  preserve the local guard\u002Freminder that prevents repeated calls.\n- **RunPod shows a healthy endpoint but the job is stuck** -> inspect queue\u002Fworker\n  state and job status, then worker logs and the actual output marker. Do not create\n  a diagnostic Pod by default.\n- **Massed tools are missing** -> check the MCP entry and token scope; a read-only\n  key intentionally hides launch\u002Frestart\u002Fterminate\u002Fkey-management tools. Do not\n  compensate with ad-hoc REST calls unless the provider runbook explicitly allows it.\n- **A launch command timed out** -> list\u002Fget the exact target and check billing,\n  inventory, and capacity before any retry. Treat the first request as possibly\n  successful.\n- **A bridge is recorded but unreachable** -> do not re-register or reconnect in a\n  read-only investigation. Report the route\u002Falias, registry age, owner\u002Fsession,\n  local PID\u002Fservice or control-socket metadata when available, last health result,\n  target identity, and whether one authorized probe was allowed. Perform only the\n  local checklist: registry heartbeat\u002FTTL, bridge process\u002Fsocket presence, SSH\n  alias and ProxyCommand mapping, and bridge-owner confirmation. Never reclaim a\n  live tunnel based only on a stale timestamp.\n","# Remote compute operations\n\nUse this skill as the provider-neutral workflow for remote GPU and server work. The\nprovider is an adapter, not the name of the skill: RunPod, Massed Compute, and an\nowned\u002Fvirtual server must all follow the same evidence, transport, lifecycle, and\nhandoff rules.\n\nWhen auditing this skill or designing a plan offline, do not call a provider, SSH,\nor bridge at all; state that live mode\u002Fidentity is unproven. The read-only lookup\nbelow applies only when the user explicitly asks to inspect live remote state.\n\n## Non-negotiable transport rule\n\nReuse the already-created bridge or live connection before opening a new one. The\npurpose is reliable, rate-limit-compliant operation and avoiding unnecessary\nauthentication attempts; never disguise traffic, evade a provider limit, rotate\nidentities, or bypass a ban.\n\n- Inspect the local connection registry\u002Fbridge health when one exists. A registry is\n  a coordination hint, not proof that a tunnel is alive. Resolve the existing\n  helper through `%USERPROFILE%\\\\.claude\\\\scripts\\\\conn_registry.py` on Windows or\n  `$HOME\u002F.claude\u002Fscripts\u002Fconn_registry.py` on POSIX when that file exists; if it is\n  not discoverable, report “registry unavailable” instead of guessing a path.\n- In a read-only investigation, do not create or re-register a bridge. If a live\n  route is required, allow at most one explicitly authorized health probe. Record\n  the host alias\u002Froute, registry entry age, session owner, local PID\u002Fservice or\n  control-socket metadata when available, target identity, last probe result, and\n  whether a probe was permitted; never record credentials.\n- Use one persistent provider client\u002Fsession per task phase. Group compatible\n  read-only queries and reuse keep-alive connections; do not create a client or\n  authenticate once per command.\n- The bridge probe has the stricter budget: local registry\u002Fconfig inspection is\n  network-free, but SSH\u002Ftunnel health is at most one attempt total per target and\n  phase, with no SSH retry after a timeout or connection error. The API-read retry\n  budget in [transport-safety.md](references\u002Ftransport-safety.md) does not apply to\n  that probe.\n- Batch related remote shell checks into one SSH invocation. Use\n  `ControlMaster`\u002F`ControlPersist` only after the exact route has passed a health\n  check. If multiplexing fails on the platform or bridge, do not retry it blindly:\n  use one batched command over the known working bridge.\n- Do not fan out API or SSH calls merely to reduce wall-clock time. Parallelism is\n  allowed only when the provider documents it, the connection budget allows it, and\n  the calls cannot duplicate a mutation.\n- For `429`, `503`, connection resets, or transport timeouts, stop increasing the\n  request rate. Honor `Retry-After`, use bounded exponential backoff with jitter,\n  and record the retry budget. See [transport-safety.md](references\u002Ftransport-safety.md).\n\n## Workflow\n\n### 1. Freeze the target and read the architecture\n\nBefore a remote mutation, read the repository `AGENTS.md`, provider runbook, and\nthe relevant reference. Establish:\n\n- provider and mode (RunPod Pod, RunPod Serverless, Massed VM, or owned server);\n- exact target ID\u002Fname, region, image\u002Ftemplate, job ID, and intended outcome;\n- traffic path: existing bridge, bastion, VPN\u002FTailscale, SSH host alias, proxy, or\n  provider API endpoint;\n- current checkout, deployment\u002Fsource revision, process\u002Fjob state, storage and\n  checkpoint path, and cost\u002Fburn boundary.\n\nDo not infer a live state from a stale handoff, old dashboard, or a command that\nonly proves that a process exists locally.\n\n### 2. Classify the provider mode before choosing a channel\n\nUse existing target metadata first. If the mode is unknown, make one read-only\ncontrol-plane lookup and classify it before touching SSH:\n\n- **RunPod Serverless:** endpoint\u002Fjob ID, `\u002Frun`\u002F`\u002Fstatus`\u002F`\u002Fhealth`, webhook, or\n  stream. Do not try to SSH to a Serverless job.\n- **RunPod Pod:** exact Pod ID plus a documented SSH\u002FTCP\u002FHTTP connection route and\n  exact bridge\u002Fhost alias. Use SSH only when the target is an actual Pod and the\n  route is already verified; never infer Pod identity from a generic job name.\n- **Massed VM:** instance UUID and the provider-returned SSH target, plus Massed\n  MCP for account\u002Finstance state.\n- **Owned\u002Fvirtual server:** documented host alias and existing bridge\u002Ftunnel.\n\nIf the provider or mode remains ambiguous after that one lookup, stop and report\nthe missing identity instead of opening a second kind of connection.\n\n### 3. Reconcile read-only state through the cheapest valid path\n\nPrefer this order:\n\n1. existing bridge\u002Fsession health and the shared connection registry;\n2. one batched remote probe for host, GPU, process, disk, and durable logs;\n3. one provider client session for exact inventory, billing, target, or job state;\n4. a second provider call only when the first result is incomplete or ambiguous.\n\nFor long jobs, prefer durable logs, checkpoints, job events, or a webhook over a\ntight status loop. If polling is the only supported observation path, use one\njob-specific timer with a minimum interval, a maximum deadline, a request budget,\nand terminal-state exit. Never poll every target independently from several agents.\n\n### 4. Select the provider adapter\n\nRead [provider-matrix.md](references\u002Fprovider-matrix.md) and then the provider's\nexisting detailed skill\u002Frunbook when available.\n\n- **RunPod:** use the local `runpod-gpu-ops` skill if it is installed; otherwise\n  use [provider-matrix.md](references\u002Fprovider-matrix.md) and the linked official\n  RunPod docs for account-specific images, volumes, and lifecycle. Serverless is\n  the default for scale-to-zero inference; a Pod is a persistent billed resource\n  and needs an explicit reason plus a cleanup owner. Use the returned\n  endpoint\u002Fjob\u002Fpod ID as the identity for all later calls.\n- **Massed Compute:** use the Massed MCP tools and read\n  [massed-compute-recipes.md](references\u002Fmassed-compute-recipes.md) for\n  provider-specific recipes. Prefer read-only tools first; destructive tools may\n  be absent from a read-only key by design. Keep the MCP session and reconcile\n  after any timeout before considering a retry.\n- **Owned or virtual server:** do not invent a cloud API. Reuse the verified SSH or\n  tunnel route, batch probes, inspect the actual service\u002Fprocess\u002FGPU\u002Flog state, and\n  use the host's runbook for restart or shutdown decisions.\n\n### 5. Mutate only the named resource\n\nLaunching or restarting affects cost and capacity. State the chosen target, image,\nquantity, region, expected hourly\u002Fper-job burn, checkpoint\u002Fstorage path, and stop\ncondition before executing within the user's request.\n\nTermination, deletion, key removal, volume destruction, and any action that can\nlose unrecoverable work require exact target disclosure, explicit confirmation,\nthe smallest possible scope, and post-action verification. A vague label such as\n\"the idle pod\" is not an exact target.\n\n### 6. Reconcile instead of duplicating\n\nEvery mutation must have an identity and a durable observation record. If a launch\nor restart times out, assume it may have succeeded: list\u002Fget by exact ID, name,\nclient idempotency key, or a narrow creation-time filter before retrying. Do not\nsend a second launch because the first response was lost.\n\nFor each state transition, record provider, target ID, bridge\u002Fsession used, source\nrevision, last observation timestamp, state, job\u002Fcheckpoint marker, and next\nallowed action. Do not record tokens, passwords, private keys, or full response\nbodies containing credentials.\n\n### 7. Close the loop\n\nAfter launch\u002Frestart\u002Fdeploy, verify the actual user-facing or job outcome, not only\nthat a VM is listed as `running`:\n\n- SSH\u002Fbridge reaches the intended host;\n- GPU and process are the expected ones;\n- service\u002Fjob health is ready and the first safe probe succeeds;\n- output\u002Fcheckpoint\u002Flog marker advances;\n- cost and cleanup owner are known.\n\nIf a remote action is left running, write the handoff\u002Fjournal entry and state the\nexact next observation. Do not leave a paid resource without a shutdown rule.\n\n## Gotchas\n\n- Provider rate limits are not interchangeable. RunPod publishes limits per\n  endpoint and operation; Massed Compute documents a generic 429 recovery path.\n  Always re-check the current provider page and response headers.\n- An SSH control socket can be unsupported or broken on a particular Windows or\n  ProxyCommand route. The safe fallback is one batched connection, not a storm of\n  short SSH calls and not an unverified direct route.\n- A “running” Pod can still be starting a service; a Serverless `\u002Fhealth` result is\n  not the same as a completed job. Check the service\u002Fjob marker and logs.\n- A timeout is an ambiguous mutation result. Reconcile by exact identity before\n  retrying; never rely on a fresh list alone when multiple jobs have similar names.\n- A shared connection registry can contain stale entries. Heartbeat expiry narrows\n  the candidates but cannot replace an external health probe.\n- API keys and VM passwords stay in the approved local secret store or provider\n  UI. Never copy them into this skill, a handoff, Git, or a command transcript.\n- Do not terminate a GPU merely because it is idle for one observation. Compare the\n  active task, owner, checkpoint\u002Foutput progress, and declared stop condition.\n\n## Troubleshooting\n\n- **Several agents keep opening SSH\u002FAPI sessions** -> inspect the shared connection\n  registry and active bridge, nominate one owner for the connection, batch the\n  remaining checks, and make other agents consume the durable log\u002Fheartbeat.\n- **`429` or `503`** -> stop fan-out, honor `Retry-After`, back off with jitter,\n  reduce polling frequency, and retry only idempotent reads. For an ambiguous\n  mutation, reconcile first.\n- **ControlMaster reports a socket or getsockname error** -> mark multiplexing\n  unavailable for that route, use the verified bridge with one batched command, and\n  preserve the local guard\u002Freminder that prevents repeated calls.\n- **RunPod shows a healthy endpoint but the job is stuck** -> inspect queue\u002Fworker\n  state and job status, then worker logs and the actual output marker. Do not create\n  a diagnostic Pod by default.\n- **Massed tools are missing** -> check the MCP entry and token scope; a read-only\n  key intentionally hides launch\u002Frestart\u002Fterminate\u002Fkey-management tools. Do not\n  compensate with ad-hoc REST calls unless the provider runbook explicitly allows it.\n- **A launch command timed out** -> list\u002Fget the exact target and check billing,\n  inventory, and capacity before any retry. Treat the first request as possibly\n  successful.\n- **A bridge is recorded but unreachable** -> do not re-register or reconnect in a\n  read-only investigation. Report the route\u002Falias, registry age, owner\u002Fsession,\n  local PID\u002Fservice or control-socket metadata when available, last health result,\n  target identity, and whether one authorized probe was allowed. Perform only the\n  local checklist: registry heartbeat\u002FTTL, bridge process\u002Fsocket presence, SSH\n  alias and ProxyCommand mapping, and bridge-owner confirmation. Never reclaim a\n  live tunnel based only on a stale timestamp.\n",{"name":5,"description":7},"main","07d02526f424fc814f8350d6b0b728e81576603d","upstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Foperational\u002Fremote-compute-ops",0,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot","2026-11-14 18:25:27",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill remote-compute-ops",{"tool":36,"command":37},"bunx","bunx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill remote-compute-ops",{"tool":39,"command":40},"pnpm","pnpm dlx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill remote-compute-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Foperational\u002Fremote-compute-ops\u002FSKILL.md",true,[44,50,54,58],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",272,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Foperational\u002Fremote-compute-ops\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fmassed-compute-recipes.md",4286,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Foperational\u002Fremote-compute-ops\u002Freferences\u002Fmassed-compute-recipes.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fprovider-matrix.md",3838,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Foperational\u002Fremote-compute-ops\u002Freferences\u002Fprovider-matrix.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Ftransport-safety.md",5164,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Foperational\u002Fremote-compute-ops\u002Freferences\u002Ftransport-safety.md",[63,69,76,83,90,97],{"skillNo":64,"name":65,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M78BHH6VNT0MKZXGMP2F50X1","owner-voice","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fowner-voice\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M78BHD34XJHAK6EMZ7J1M80X","humanize-russian","Редактировать русский текст для ясности и естественного звучания, сохраняя факты,\nтермины, источники и жанр. Использовать когда: убрать канцелярит, сделать текст\nживее, отредактировать русский черновик или статью перед публикацией.\nНе определяет авторство и не обещает обход детекторов. Для английского —\nhumanize-english; для структуры и доказательств — article-structure-review.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fhumanize-russian\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M78BH9D09HCA7ECZMPEEAE5Y","humanize-english","Edit English drafts for clear, natural language while preserving facts, uncertainty,\ntechnical meaning, citations and genre. Use when: humanize this text, remove AI-style\nfiller, improve English prose, or edit an English article before publication.\nNot an authorship detector or a promise to bypass one. For Russian use\nhumanize-russian; for thesis\u002Fevidence and structure use article-structure-review.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fhumanize-english\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M78BH44Q25YMA16MC6FKZ2WY","caveman","Ultra-compressed reply mode. Cuts output tokens ~65-75% by answering in terse \"caveman\" style while keeping full technical accuracy, and shapes what survives: action first, state restated every turn, concrete time estimates, visible wins. Intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says \"caveman\", \"talk like caveman\", \"use caveman\", \"less tokens\", \"be brief\", or Russian \"пещерный режим\", \"говори как пещерный\", \"кратко\", \"меньше токенов\", \"экономь токены\" — or invokes \u002Fcaveman. Preserves the user's language (Russian in → Russian caveman out). Off only: \"stop caveman\" \u002F \"normal mode\" \u002F \"обычный режим\". Do not use merely because a response should be concise, and do not use when the user requests normal prose, a polished document, or exact wording.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fcaveman\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M78BGY0JTMTW3J3YE5RQTHCK","article-structure-review","Проверить структуру технической статьи после черновика: задача читателя, жанр,\nопора значимых утверждений на доказательства и честные ограничения.\nUse after the first draft, before publication. Исправлять структуру, когда это\nвходит в запрос; не создавать обязательный конвейер из других навыков.\nДля локальной языковой редактуры — humanize-english или humanize-russian.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Farticle-structure-review\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M78BGRJYZGK1TNTCHWGY32W3","video-post-production","Video post-production rules: audio mastering, color, captions, platform export. Use when: 'add music', 'add voiceover', 'export for tiktok', 'add captions', 'color grade', 'audio levels', 'master audio', 'export settings', 'platform requirements'. Covers FFmpeg patterns, audio chain, subtitle standards, and platform-specific export configs. Do NOT use to generate or animate the video frames\u002Fscenes in code (use remotion-production-guide), to write the script (use video-narrative-arc), or to evaluate script quality (use script-evaluator); this is the finishing stage applied to an already-rendered video.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fvideo-production\u002Fvideo-post-production\u002FSKILL.md",[],[]]