{"id":"12ea52cc-f807-4665-82d3-e31b89a44821","entityType":"agent","slug":"clawhub-hith3sh-runpod-compute","name":"RunPod","canonicalUrl":"https://www.xpersona.co/agent/clawhub-hith3sh-runpod-compute","canonicalPath":"/agent/clawhub-hith3sh-runpod-compute","generatedAt":"2026-10-10T03:34:51.295Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T14:22:42.317Z","emptyReason":null},"description":"RunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distrib... Skill: RunPod Owner: hith3sh Summary: RunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distrib... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:17:06.672Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.5K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:runpod-compute","sourceUrl":"https://clawhub.ai/hith3sh/runpod-compute","homepage":"https://clawhub.ai/hith3sh/skills/runpod-compute","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/hith3sh/runpod-compute","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/hith3sh/skills/runpod-compute","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":68,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"RunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distrib..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T14:22:42.317Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T14:22:42.317Z","emptyReason":null},"stars":null,"forks":null,"downloads":2490,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"2.5K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T14:22:42.317Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T14:22:42.317Z","lastCrawledAt":"2026-10-09T14:22:42.317Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T14:22:42.317Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-06-09T07:17:06.672Z","changelog":"Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.","fileCount":3,"zipByteSize":5821},{"version":"1.0.4","createdAt":"2026-06-09T05:03:28.896Z","changelog":"- Removed the file: skill-card.md - No functional or user-facing feature changes included in this release.","fileCount":3,"zipByteSize":5882},{"version":"1.0.1","createdAt":"2026-06-08T16:41:47.561Z","changelog":"- Added a RunPod brand logo image at the top of the documentation for improved visual identification. - Removed redundant or obsolete file: skill-card.md. - No changes to functionality; documentation update and cleanup only.","fileCount":3,"zipByteSize":5870},{"version":"0.1.1","createdAt":"2026-06-07T13:35:35.816Z","changelog":"Full rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.","fileCount":3,"zipByteSize":5809},{"version":"0.1.0","createdAt":"2026-05-24T16:05:32.308Z","changelog":"Initial release of runpod-compute skill. - Enables inspection of compute resources, pods, templates, clusters, and serverless infrastructure in RunPod via ClawLink integration. - Outlines step-by-step setup, pairing, and connection process with ClawLink—no direct RunPod credential entry required. - Provides operational guidance covering discovery, execution, and confirmation rules for all RunPod tools accessed through ClawLink. - Includes best practices for safe operations, avoiding raw credential handling, and ensuring up-to-date tool catalog usage. - Lists helpful resources for both ClawLink and RunPod documentation.","fileCount":3,"zipByteSize":3420}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:runpod-compute","setupComplexity":"medium","setupSteps":["Setup complexity is MEDIUM. Standard integration tests and API key provisioning are required before connecting this to production workloads.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-runpod-compute/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-runpod-compute/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-runpod-compute/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-runpod-compute/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-runpod-compute/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-runpod-compute/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T03:34:51.294Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-runpod-compute/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-runpod-compute/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-runpod-compute/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-runpod-compute/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T14:22:42.317Z","emptyReason":null},"readme":"Skill: RunPod\n\nOwner: hith3sh\n\nSummary: RunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distrib...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-06-09T07:17:06.672Z | user\n\nAdd UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.\n\nv1.0.4 | 2026-06-09T05:03:28.896Z | auto\n\n- Removed the file: skill-card.md\n- No functional or user-facing feature changes included in this release.\n\nv1.0.1 | 2026-06-08T16:41:47.561Z | auto\n\n- Added a RunPod brand logo image at the top of the documentation for improved visual identification.\n- Removed redundant or obsolete file: skill-card.md.\n- No changes to functionality; documentation update and cleanup only.\n\nv0.1.1 | 2026-06-07T13:35:35.816Z | user\n\nFull rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.\n\nv0.1.0 | 2026-05-24T16:05:32.308Z | auto\n\nInitial release of runpod-compute skill.\n\n- Enables inspection of compute resources, pods, templates, clusters, and serverless infrastructure in RunPod via ClawLink integration.\n- Outlines step-by-step setup, pairing, and connection process with ClawLink—no direct RunPod credential entry required.\n- Provides operational guidance covering discovery, execution, and confirmation rules for all RunPod tools accessed through ClawLink.\n- Includes best practices for safe operations, avoiding raw credential handling, and ensuring up-to-date tool catalog usage.\n- Lists helpful resources for both ClawLink and RunPod documentation.\n\nArchive index:\n\nArchive v1.0.5: 3 files, 5821 bytes\n\nFiles: skill-card.md (2359b), SKILL.md (13560b), _meta.json (133b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: runpod-compute\ndescription: RunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distributed computing workloads.\n---\n\n# RunPod\n\n![RunPod](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/runpod.webp)\n\nDeploy and manage GPU-accelerated compute infrastructure on RunPod. Create clusters, configure serverless endpoints, manage templates, and handle secrets for ML training, inference, and distributed computing workloads.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=runpod-compute) for hosted connection flows and credentials so you do not need to configure RunPod API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect RunPod |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect RunPod |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ RunPod API │\n│ (User Chat) │ │ (Proxy) │ │ (Clusters, │\n│ │ │ │ │ Endpoints) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect RunPod │ │\n │ │ 4. API Key Proxy │\n │ │ 5. Request Forward │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ RunPod │\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for RunPod again.\"\n\n## Quick Start\n\n```bash\n# List available GPU types\nclawlink_call_tool --tool \"runpod_get_gpu_types\"\n\n# Get current user info\nclawlink_call_tool --tool \"runpod_get_myself\"\n\n# Get pod details\nclawlink_call_tool --tool \"runpod_get_pod\" --params '{\"pod_id\": \"YOUR_POD_ID\"}'\n```\n\n## Authentication\n\nAll RunPod tool calls are authenticated automatically by ClawLink using your RunPod API key stored securely in the dashboard.\n\n**No API key is required in chat.** ClawLink injects your API key into every RunPod GraphQL request on your behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=runpod and connect RunPod with your API key.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `runpod` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration runpod\n```\n\n**Response:** Returns the live tool catalog for RunPod.\n\n### Reconnect\n\nIf RunPod tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=runpod\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration runpod`\n\n## Security & Permissions\n\n- Access is scoped to the RunPod account associated with the connected API key.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete template, delete registry auth) are marked as high-impact and must be confirmed.\n- Secrets are stored securely and injected as environment variables (`RUNPOD_SECRET_`) in pods and endpoints.\n\n## Tool Reference\n\n### Compute & GPU Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_get_gpu_types` | Retrieve available GPU types, specs, pricing, and availability | Read |\n| `runpod_list_cpu_types` | Retrieve available CPU types and specifications | Read |\n| `runpod_get_pod` | Get details of a specific pod by ID (GPU count, memory, cost, status) | Read |\n\n### Cluster Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_create_cluster` | Create a new GPU cluster for multi-node distributed computing workloads | Write |\n\n### Serverless Endpoints\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_save_endpoint` | Create or update a GPU-accelerated serverless endpoint (include `id` to update, omit to create) | Write |\n\n### Template Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_save_template` | Create a new template or update an existing one with container configuration | Write |\n| `runpod_delete_template` | Remove a template (must not be in use by pods or serverless endpoints) | Write |\n\n### Secrets Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_create_secret` | Create a secure secret for credential management (accessible as `RUNPOD_SECRET_`) | Write |\n\n### Registry Authentication\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_save_registry_auth` | Save container registry authentication credentials for private Docker images | Write |\n| `runpod_update_registry_auth` | Update existing container registry authentication credentials | Write |\n| `runpod_delete_registry_auth` | Delete container registry authentication from RunPod | Write |\n\n### User Settings\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_get_myself` | Retrieve authenticated user info (ID, email, MFA settings) | Read |\n| `runpod_update_user_settings` | Update user settings (e.g., SSH public key for pod access) | Write |\n\n## Code Examples\n\n### List available GPU types\n\n```bash\nclawlink_call_tool --tool \"runpod_get_gpu_types\"\n```\n\n### Get pod details\n\n```bash\nclawlink_call_tool --tool \"runpod_get_pod\" \\\n --params '{\"pod_id\": \"YOUR_POD_ID\"}'\n```\n\n### Create a secret\n\n```bash\nclawlink_call_tool --tool \"runpod_create_secret\" \\\n --params '{\"name\": \"OPENAI_API_KEY\", \"value\": \"sk-...\"}'\n```\n\n### Save a serverless endpoint\n\n```bash\nclawlink_call_tool --tool \"runpod_save_endpoint\" \\\n --params '{\n \"name\": \"my-endpoint\",\n \"gpu_type_id\": \"RTX_4090\",\n \"image_url\": \"your-docker-image:latest\",\n \"env\": [{\"key\": \"MODEL_PATH\", \"value\": \"/models/llama\"}]\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm RunPod is connected.\n2. Call `clawlink_list_tools --integration runpod` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `runpod`.\n5. If no RunPod tools appear, direct the user to https://claw-link.dev/dashboard?add=runpod.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → describe → call │\n│ │\n│ Example: List GPU types → Get pod details → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute create │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- GPU types and pricing change frequently — always call `runpod_get_gpu_types` to get current availability before deploying.\n- Serverless templates must set `volumeInGb` to `0` (no persistent storage for serverless).\n- Pods and endpoints reference secrets via `RUNPOD_SECRET_` environment variables — create secrets before referencing them in templates.\n- Templates must not be in use when deleted — reassign or remove affected pods/endpoints first.\n- API key must have sufficient permissions for cluster and endpoint operations.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration runpod`. |\n| Missing connection | RunPod is not connected. Direct the user to https://claw-link.dev/dashboard?add=runpod. |\n| `template_in_use` | Template is assigned to active pods or endpoints. Reassign or delete them first. |\n| `invalid_gpu_type` | The specified GPU type is not available in the selected region. Check `runpod_get_gpu_types`. |\n| `permission_denied` | API key lacks required permissions for the operation. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `runpod`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [RunPod API Documentation](https://docs.runpod.io)\n- [GPU Cloud Pods](https://docs.runpod.io/pods)\n- [Serverless Endpoints](https://docs.runpod.io/serverless-endpoints)\n- [Templates](https://docs.runpod.io/templates)\n- [Secrets Management](https://docs.runpod.io/secrets)\n- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=runpod-compute\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Google Cloud Compute](https://clawhub.ai/hith3sh/google-cloud-compute) — For GCP compute engine management\n- [AWS EC2](https://clawhub.ai/hith3sh/aws-ec2-instances) — For AWS EC2 instance management\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=runpod-compute)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"runpod-compute\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1780989426672\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nRunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distributed computing workloads.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to connect OpenClaw to RunPod through ClawLink and manage GPU compute resources for ML training, inference, and distributed computing workloads.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill relies on ClawLink as an external plugin and credential proxy for a RunPod API key.\n\nMitigation: Use a dedicated, least-privileged RunPod API key where possible and install the skill only when the ClawLink trust boundary is acceptable.\n\nRisk: RunPod write actions can create or change clusters, endpoints, templates, secrets, registry credentials, and SSH-related account settings.\n\nMitigation: Review previews before writes, require explicit confirmation for create, update, and delete actions, and monitor RunPod for unexpected resource or credential changes.\n\n## Reference(s):\n\n- [RunPod API Documentation](https://docs.runpod.io)\n- [GPU Cloud Pods](https://docs.runpod.io/pods)\n- [Serverless Endpoints](https://docs.runpod.io/serverless-endpoints)\n- [Templates](https://docs.runpod.io/templates)\n- [Secrets Management](https://docs.runpod.io/secrets)\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/runpod-compute)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands, Configuration, API calls, Markdown]\n\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Guides ClawLink tool discovery, previews, confirmations, and RunPod API calls; does not require users to paste RunPod API keys into chat.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 3 files, 5882 bytes\n\nFiles: skill-card.md (2776b), SKILL.md (13359b), _meta.json (133b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: runpod-compute\ndescription: RunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distributed computing workloads.\n---\n\n# RunPod\n\n![RunPod](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/runpod.webp)\n\nDeploy and manage GPU-accelerated compute infrastructure on RunPod. Create clusters, configure serverless endpoints, manage templates, and handle secrets for ML training, inference, and distributed computing workloads.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure RunPod API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect RunPod |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect RunPod |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ RunPod API │\n│ (User Chat) │ │ (Proxy) │ │ (Clusters, │\n│ │ │ │ │ Endpoints) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect RunPod │ │\n │ │ 4. API Key Proxy │\n │ │ 5. Request Forward │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ RunPod │\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for RunPod again.\"\n\n## Quick Start\n\n```bash\n# List available GPU types\nclawlink_call_tool --tool \"runpod_get_gpu_types\"\n\n# Get current user info\nclawlink_call_tool --tool \"runpod_get_myself\"\n\n# Get pod details\nclawlink_call_tool --tool \"runpod_get_pod\" --params '{\"pod_id\": \"YOUR_POD_ID\"}'\n```\n\n## Authentication\n\nAll RunPod tool calls are authenticated automatically by ClawLink using your RunPod API key stored securely in the dashboard.\n\n**No API key is required in chat.** ClawLink injects your API key into every RunPod GraphQL request on your behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=runpod and connect RunPod with your API key.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `runpod` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration runpod\n```\n\n**Response:** Returns the live tool catalog for RunPod.\n\n### Reconnect\n\nIf RunPod tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=runpod\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration runpod`\n\n## Security & Permissions\n\n- Access is scoped to the RunPod account associated with the connected API key.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete template, delete registry auth) are marked as high-impact and must be confirmed.\n- Secrets are stored securely and injected as environment variables (`RUNPOD_SECRET_`) in pods and endpoints.\n\n## Tool Reference\n\n### Compute & GPU Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_get_gpu_types` | Retrieve available GPU types, specs, pricing, and availability | Read |\n| `runpod_list_cpu_types` | Retrieve available CPU types and specifications | Read |\n| `runpod_get_pod` | Get details of a specific pod by ID (GPU count, memory, cost, status) | Read |\n\n### Cluster Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_create_cluster` | Create a new GPU cluster for multi-node distributed computing workloads | Write |\n\n### Serverless Endpoints\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_save_endpoint` | Create or update a GPU-accelerated serverless endpoint (include `id` to update, omit to create) | Write |\n\n### Template Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_save_template` | Create a new template or update an existing one with container configuration | Write |\n| `runpod_delete_template` | Remove a template (must not be in use by pods or serverless endpoints) | Write |\n\n### Secrets Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_create_secret` | Create a secure secret for credential management (accessible as `RUNPOD_SECRET_`) | Write |\n\n### Registry Authentication\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_save_registry_auth` | Save container registry authentication credentials for private Docker images | Write |\n| `runpod_update_registry_auth` | Update existing container registry authentication credentials | Write |\n| `runpod_delete_registry_auth` | Delete container registry authentication from RunPod | Write |\n\n### User Settings\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_get_myself` | Retrieve authenticated user info (ID, email, MFA settings) | Read |\n| `runpod_update_user_settings` | Update user settings (e.g., SSH public key for pod access) | Write |\n\n## Code Examples\n\n### List available GPU types\n\n```bash\nclawlink_call_tool --tool \"runpod_get_gpu_types\"\n```\n\n### Get pod details\n\n```bash\nclawlink_call_tool --tool \"runpod_get_pod\" \\\n --params '{\"pod_id\": \"YOUR_POD_ID\"}'\n```\n\n### Create a secret\n\n```bash\nclawlink_call_tool --tool \"runpod_create_secret\" \\\n --params '{\"name\": \"OPENAI_API_KEY\", \"value\": \"sk-...\"}'\n```\n\n### Save a serverless endpoint\n\n```bash\nclawlink_call_tool --tool \"runpod_save_endpoint\" \\\n --params '{\n \"name\": \"my-endpoint\",\n \"gpu_type_id\": \"RTX_4090\",\n \"image_url\": \"your-docker-image:latest\",\n \"env\": [{\"key\": \"MODEL_PATH\", \"value\": \"/models/llama\"}]\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm RunPod is connected.\n2. Call `clawlink_list_tools --integration runpod` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `runpod`.\n5. If no RunPod tools appear, direct the user to https://claw-link.dev/dashboard?add=runpod.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → describe → call │\n│ │\n│ Example: List GPU types → Get pod details → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute create │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- GPU types and pricing change frequently — always call `runpod_get_gpu_types` to get current availability before deploying.\n- Serverless templates must set `volumeInGb` to `0` (no persistent storage for serverless).\n- Pods and endpoints reference secrets via `RUNPOD_SECRET_` environment variables — create secrets before referencing them in templates.\n- Templates must not be in use when deleted — reassign or remove affected pods/endpoints first.\n- API key must have sufficient permissions for cluster and endpoint operations.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration runpod`. |\n| Missing connection | RunPod is not connected. Direct the user to https://claw-link.dev/dashboard?add=runpod. |\n| `template_in_use` | Template is assigned to active pods or endpoints. Reassign or delete them first. |\n| `invalid_gpu_type` | The specified GPU type is not available in the selected region. Check `runpod_get_gpu_types`. |\n| `permission_denied` | API key lacks required permissions for the operation. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `runpod`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [RunPod API Documentation](https://docs.runpod.io)\n- [GPU Cloud Pods](https://docs.runpod.io/pods)\n- [Serverless Endpoints](https://docs.runpod.io/serverless-endpoints)\n- [Templates](https://docs.runpod.io/templates)\n- [Secrets Management](https://docs.runpod.io/secrets)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Google Cloud Compute](https://clawhub.ai/hith3sh/google-cloud-compute) — For GCP compute engine management\n- [AWS EC2](https://clawhub.ai/hith3sh/aws-ec2-instances) — For AWS EC2 instance management\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"runpod-compute\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1780981408896\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:
\nRunPod API integration with API key authentication for creating and managing GPU clusters, serverless endpoints, templates, and secrets for ML inference and distributed computing workloads.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineers use this skill to inspect and manage RunPod GPU compute resources, serverless endpoints, templates, registry authentication, and secrets through ClawLink-backed RunPod API calls.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill requires a RunPod API key to be stored and proxied through ClawLink.
\nMitigation: Install only if ClawLink is trusted for credential handling, and use a RunPod API key with the minimum permissions needed.
\nRisk: Write actions can create GPU clusters or endpoints, which may affect account billing and availability.
\nMitigation: Review every preview carefully and approve writes only after the target resource and intended effect match the user's request.
\nRisk: Destructive actions such as deleting templates or registry authentication can disrupt workloads or private image access.
\nMitigation: Confirm destructive operations explicitly and verify that templates, pods, endpoints, or registry credentials are not still needed.
\n\n\n## Reference(s):
\n- [RunPod Skill on ClawHub](https://clawhub.ai/hith3sh/runpod-compute)
\n- [RunPod API Documentation](https://docs.runpod.io)
\n- [RunPod GPU Cloud Pods](https://docs.runpod.io/pods)
\n- [RunPod Serverless Endpoints](https://docs.runpod.io/serverless-endpoints)
\n- [RunPod Templates](https://docs.runpod.io/templates)
\n- [RunPod Secrets Management](https://docs.runpod.io/secrets)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Shell commands, Configuration, API calls, Markdown]
\n**Output Format:** [Markdown with inline bash commands and JSON tool-call parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses live ClawLink tool catalogs for RunPod operations and requires user confirmation before write or destructive actions.]
\n\n## Skill Version(s):
\n1.0.4 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 3 files, 5870 bytes\n\nFiles: skill-card.md (2662b), SKILL.md (13359b), _meta.json (133b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: runpod-compute\ndescription: RunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distributed computing workloads.\n---\n\n# RunPod\n\n![RunPod](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/runpod.webp)\n\nDeploy and manage GPU-accelerated compute infrastructure on RunPod. Create clusters, configure serverless endpoints, manage templates, and handle secrets for ML training, inference, and distributed computing workloads.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure RunPod API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect RunPod |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect RunPod |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ RunPod API │\n│ (User Chat) │ │ (Proxy) │ │ (Clusters, │\n│ │ │ │ │ Endpoints) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect RunPod │ │\n │ │ 4. API Key Proxy │\n │ │ 5. Request Forward │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ RunPod │\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for RunPod again.\"\n\n## Quick Start\n\n```bash\n# List available GPU types\nclawlink_call_tool --tool \"runpod_get_gpu_types\"\n\n# Get current user info\nclawlink_call_tool --tool \"runpod_get_myself\"\n\n# Get pod details\nclawlink_call_tool --tool \"runpod_get_pod\" --params '{\"pod_id\": \"YOUR_POD_ID\"}'\n```\n\n## Authentication\n\nAll RunPod tool calls are authenticated automatically by ClawLink using your RunPod API key stored securely in the dashboard.\n\n**No API key is required in chat.** ClawLink injects your API key into every RunPod GraphQL request on your behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=runpod and connect RunPod with your API key.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `runpod` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration runpod\n```\n\n**Response:** Returns the live tool catalog for RunPod.\n\n### Reconnect\n\nIf RunPod tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=runpod\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration runpod`\n\n## Security & Permissions\n\n- Access is scoped to the RunPod account associated with the connected API key.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete template, delete registry auth) are marked as high-impact and must be confirmed.\n- Secrets are stored securely and injected as environment variables (`RUNPOD_SECRET_`) in pods and endpoints.\n\n## Tool Reference\n\n### Compute & GPU Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_get_gpu_types` | Retrieve available GPU types, specs, pricing, and availability | Read |\n| `runpod_list_cpu_types` | Retrieve available CPU types and specifications | Read |\n| `runpod_get_pod` | Get details of a specific pod by ID (GPU count, memory, cost, status) | Read |\n\n### Cluster Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_create_cluster` | Create a new GPU cluster for multi-node distributed computing workloads | Write |\n\n### Serverless Endpoints\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_save_endpoint` | Create or update a GPU-accelerated serverless endpoint (include `id` to update, omit to create) | Write |\n\n### Template Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_save_template` | Create a new template or update an existing one with container configuration | Write |\n| `runpod_delete_template` | Remove a template (must not be in use by pods or serverless endpoints) | Write |\n\n### Secrets Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_create_secret` | Create a secure secret for credential management (accessible as `RUNPOD_SECRET_`) | Write |\n\n### Registry Authentication\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_save_registry_auth` | Save container registry authentication credentials for private Docker images | Write |\n| `runpod_update_registry_auth` | Update existing container registry authentication credentials | Write |\n| `runpod_delete_registry_auth` | Delete container registry authentication from RunPod | Write |\n\n### User Settings\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_get_myself` | Retrieve authenticated user info (ID, email, MFA settings) | Read |\n| `runpod_update_user_settings` | Update user settings (e.g., SSH public key for pod access) | Write |\n\n## Code Examples\n\n### List available GPU types\n\n```bash\nclawlink_call_tool --tool \"runpod_get_gpu_types\"\n```\n\n### Get pod details\n\n```bash\nclawlink_call_tool --tool \"runpod_get_pod\" \\\n --params '{\"pod_id\": \"YOUR_POD_ID\"}'\n```\n\n### Create a secret\n\n```bash\nclawlink_call_tool --tool \"runpod_create_secret\" \\\n --params '{\"name\": \"OPENAI_API_KEY\", \"value\": \"sk-...\"}'\n```\n\n### Save a serverless endpoint\n\n```bash\nclawlink_call_tool --tool \"runpod_save_endpoint\" \\\n --params '{\n \"name\": \"my-endpoint\",\n \"gpu_type_id\": \"RTX_4090\",\n \"image_url\": \"your-docker-image:latest\",\n \"env\": [{\"key\": \"MODEL_PATH\", \"value\": \"/models/llama\"}]\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm RunPod is connected.\n2. Call `clawlink_list_tools --integration runpod` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `runpod`.\n5. If no RunPod tools appear, direct the user to https://claw-link.dev/dashboard?add=runpod.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → describe → call │\n│ │\n│ Example: List GPU types → Get pod details → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute create │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- GPU types and pricing change frequently — always call `runpod_get_gpu_types` to get current availability before deploying.\n- Serverless templates must set `volumeInGb` to `0` (no persistent storage for serverless).\n- Pods and endpoints reference secrets via `RUNPOD_SECRET_` environment variables — create secrets before referencing them in templates.\n- Templates must not be in use when deleted — reassign or remove affected pods/endpoints first.\n- API key must have sufficient permissions for cluster and endpoint operations.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration runpod`. |\n| Missing connection | RunPod is not connected. Direct the user to https://claw-link.dev/dashboard?add=runpod. |\n| `template_in_use` | Template is assigned to active pods or endpoints. Reassign or delete them first. |\n| `invalid_gpu_type` | The specified GPU type is not available in the selected region. Check `runpod_get_gpu_types`. |\n| `permission_denied` | API key lacks required permissions for the operation. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `runpod`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [RunPod API Documentation](https://docs.runpod.io)\n- [GPU Cloud Pods](https://docs.runpod.io/pods)\n- [Serverless Endpoints](https://docs.runpod.io/serverless-endpoints)\n- [Templates](https://docs.runpod.io/templates)\n- [Secrets Management](https://docs.runpod.io/secrets)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Google Cloud Compute](https://clawhub.ai/hith3sh/google-cloud-compute) — For GCP compute engine management\n- [AWS EC2](https://clawhub.ai/hith3sh/aws-ec2-instances) — For AWS EC2 instance management\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"runpod-compute\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1780936907561\n}\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nRunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distributed computing workloads.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and ML infrastructure operators use this skill to connect OpenClaw to RunPod through ClawLink and manage GPU pods, clusters, serverless endpoints, templates, registry credentials, and secrets.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill brokers sensitive RunPod API access through ClawLink.
\nMitigation: Install only when the user trusts ClawLink for RunPod access, verify the active RunPod connection, and avoid asking for API keys in chat.
\nRisk: Write-capable RunPod actions can create, update, or delete cloud resources and may affect costs.
\nMitigation: Use read and describe operations first, preview write calls, and confirm the target resource, intended effect, and cost impact before execution.
\nRisk: Secret and registry credential operations can expose or misuse sensitive values.
\nMitigation: Confirm secret names, destinations, and credential changes before execution, and rely on the connected service to store and inject secrets instead of printing them.
\n\n\n## Reference(s):
\n- [RunPod ClawHub page](https://clawhub.ai/hith3sh/runpod-compute)
\n- [RunPod API Documentation](https://docs.runpod.io)
\n- [GPU Cloud Pods](https://docs.runpod.io/pods)
\n- [Serverless Endpoints](https://docs.runpod.io/serverless-endpoints)
\n- [Templates](https://docs.runpod.io/templates)
\n- [Secrets Management](https://docs.runpod.io/secrets)
\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, markdown, shell commands, configuration, API calls]
\n**Output Format:** [Markdown with inline shell commands and JSON parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires a ClawLink connection to a RunPod API key; write actions require explicit user confirmation.]
\n\n## Skill Version(s):
\n1.0.1 (source: server-resolved release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.1.1: 3 files, 5809 bytes\n\nFiles: skill-card.md (2558b), SKILL.md (13249b), _meta.json (133b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: runpod-compute\ndescription: RunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distributed computing workloads.\n---\n\n# RunPod\n\nDeploy and manage GPU-accelerated compute infrastructure on RunPod. Create clusters, configure serverless endpoints, manage templates, and handle secrets for ML training, inference, and distributed computing workloads.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure RunPod API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect RunPod |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect RunPod |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ RunPod API │\n│ (User Chat) │ │ (Proxy) │ │ (Clusters, │\n│ │ │ │ │ Endpoints) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect RunPod │ │\n │ │ 4. API Key Proxy │\n │ │ 5. Request Forward │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ RunPod │\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for RunPod again.\"\n\n## Quick Start\n\n```bash\n# List available GPU types\nclawlink_call_tool --tool \"runpod_get_gpu_types\"\n\n# Get current user info\nclawlink_call_tool --tool \"runpod_get_myself\"\n\n# Get pod details\nclawlink_call_tool --tool \"runpod_get_pod\" --params '{\"pod_id\": \"YOUR_POD_ID\"}'\n```\n\n## Authentication\n\nAll RunPod tool calls are authenticated automatically by ClawLink using your RunPod API key stored securely in the dashboard.\n\n**No API key is required in chat.** ClawLink injects your API key into every RunPod GraphQL request on your behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=runpod and connect RunPod with your API key.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `runpod` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration runpod\n```\n\n**Response:** Returns the live tool catalog for RunPod.\n\n### Reconnect\n\nIf RunPod tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=runpod\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration runpod`\n\n## Security & Permissions\n\n- Access is scoped to the RunPod account associated with the connected API key.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete template, delete registry auth) are marked as high-impact and must be confirmed.\n- Secrets are stored securely and injected as environment variables (`RUNPOD_SECRET_`) in pods and endpoints.\n\n## Tool Reference\n\n### Compute & GPU Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_get_gpu_types` | Retrieve available GPU types, specs, pricing, and availability | Read |\n| `runpod_list_cpu_types` | Retrieve available CPU types and specifications | Read |\n| `runpod_get_pod` | Get details of a specific pod by ID (GPU count, memory, cost, status) | Read |\n\n### Cluster Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_create_cluster` | Create a new GPU cluster for multi-node distributed computing workloads | Write |\n\n### Serverless Endpoints\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_save_endpoint` | Create or update a GPU-accelerated serverless endpoint (include `id` to update, omit to create) | Write |\n\n### Template Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_save_template` | Create a new template or update an existing one with container configuration | Write |\n| `runpod_delete_template` | Remove a template (must not be in use by pods or serverless endpoints) | Write |\n\n### Secrets Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_create_secret` | Create a secure secret for credential management (accessible as `RUNPOD_SECRET_`) | Write |\n\n### Registry Authentication\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_save_registry_auth` | Save container registry authentication credentials for private Docker images | Write |\n| `runpod_update_registry_auth` | Update existing container registry authentication credentials | Write |\n| `runpod_delete_registry_auth` | Delete container registry authentication from RunPod | Write |\n\n### User Settings\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `runpod_get_myself` | Retrieve authenticated user info (ID, email, MFA settings) | Read |\n| `runpod_update_user_settings` | Update user settings (e.g., SSH public key for pod access) | Write |\n\n## Code Examples\n\n### List available GPU types\n\n```bash\nclawlink_call_tool --tool \"runpod_get_gpu_types\"\n```\n\n### Get pod details\n\n```bash\nclawlink_call_tool --tool \"runpod_get_pod\" \\\n --params '{\"pod_id\": \"YOUR_POD_ID\"}'\n```\n\n### Create a secret\n\n```bash\nclawlink_call_tool --tool \"runpod_create_secret\" \\\n --params '{\"name\": \"OPENAI_API_KEY\", \"value\": \"sk-...\"}'\n```\n\n### Save a serverless endpoint\n\n```bash\nclawlink_call_tool --tool \"runpod_save_endpoint\" \\\n --params '{\n \"name\": \"my-endpoint\",\n \"gpu_type_id\": \"RTX_4090\",\n \"image_url\": \"your-docker-image:latest\",\n \"env\": [{\"key\": \"MODEL_PATH\", \"value\": \"/models/llama\"}]\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm RunPod is connected.\n2. Call `clawlink_list_tools --integration runpod` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `runpod`.\n5. If no RunPod tools appear, direct the user to https://claw-link.dev/dashboard?add=runpod.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → describe → call │\n│ │\n│ Example: List GPU types → Get pod details → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute create │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- GPU types and pricing change frequently — always call `runpod_get_gpu_types` to get current availability before deploying.\n- Serverless templates must set `volumeInGb` to `0` (no persistent storage for serverless).\n- Pods and endpoints reference secrets via `RUNPOD_SECRET_` environment variables — create secrets before referencing them in templates.\n- Templates must not be in use when deleted — reassign or remove affected pods/endpoints first.\n- API key must have sufficient permissions for cluster and endpoint operations.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration runpod`. |\n| Missing connection | RunPod is not connected. Direct the user to https://claw-link.dev/dashboard?add=runpod. |\n| `template_in_use` | Template is assigned to active pods or endpoints. Reassign or delete them first. |\n| `invalid_gpu_type` | The specified GPU type is not available in the selected region. Check `runpod_get_gpu_types`. |\n| `permission_denied` | API key lacks required permissions for the operation. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `runpod`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [RunPod API Documentation](https://docs.runpod.io)\n- [GPU Cloud Pods](https://docs.runpod.io/pods)\n- [Serverless Endpoints](https://docs.runpod.io/serverless-endpoints)\n- [Templates](https://docs.runpod.io/templates)\n- [Secrets Management](https://docs.runpod.io/secrets)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Google Cloud Compute](https://clawhub.ai/hith3sh/google-cloud-compute) — For GCP compute engine management\n- [AWS EC2](https://clawhub.ai/hith3sh/aws-ec2-instances) — For AWS EC2 instance management\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v0.1.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"runpod-compute\",\n \"version\": \"0.1.1\",\n \"publishedAt\": 1780839335816\n}\n\nFile v0.1.1:skill-card.md\n\n## Description:
\nRunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distributed computing workloads.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineers use this skill to manage RunPod GPU compute, serverless endpoints, templates, registry authentication, and account settings through ClawLink-mediated RunPod tools.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can act on a connected RunPod account, including creating or deleting cloud resources and managing secrets.
\nMitigation: Confirm the target resource and intended effect before write or destructive actions, and use preview or describe steps when a request is ambiguous.
\nRisk: RunPod API keys, registry passwords, and other secrets could be exposed if pasted into shared chats, logs, screenshots, or shell history.
\nMitigation: Enter credentials only through the ClawLink dashboard or another protected secret flow, and avoid including real secrets in chat or command examples.
\n\n\n## Reference(s):
\n- [ClawHub RunPod Skill Listing](https://clawhub.ai/hith3sh/runpod-compute)
\n- [RunPod API Documentation](https://docs.runpod.io)
\n- [RunPod GPU Cloud Pods](https://docs.runpod.io/pods)
\n- [RunPod Serverless Endpoints](https://docs.runpod.io/serverless-endpoints)
\n- [RunPod Templates](https://docs.runpod.io/templates)
\n- [RunPod Secrets Management](https://docs.runpod.io/secrets)
\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Shell commands, Configuration, API Calls, Markdown]
\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include RunPod resource identifiers, tool names, command examples, and confirmation prompts for write operations.]
\n\n## Skill Version(s):
\n0.1.1 (source: server evidence release version)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.1.0: 3 files, 3420 bytes\n\nFiles: skill-card.md (2207b), SKILL.md (5043b), _meta.json (133b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: runpod-compute\ndescription: Inspect compute resources, pods, templates, clusters, and serverless infrastructure in RunPod - powered by ClawLink.\n---\n\n# RunPod\n\nWork with RunPod from chat - inspect compute resources, pods, templates, clusters, endpoints, and account settings.\n\nPowered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure RunPod API access yourself.\n\n## Quick start\n\n1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`\n2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet\n3. If ClawLink is not configured, call `clawlink_begin_pairing`\n4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device\n5. After the user confirms approval, call `clawlink_get_pairing_status`\n6. Tell the user to connect RunPod at [claw-link.dev/dashboard?add=runpod](https://claw-link.dev/dashboard?add=runpod)\n7. When the user confirms RunPod is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `runpod` integration slug\n\n## Setup details\n\n### Installing the plugin\n\nIf the ClawLink plugin is not installed yet, tell the user to run:\n\n```\nopenclaw plugins install clawhub:clawlink-plugin\n```\n\nIf the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.\n\n### Pairing ClawLink\n\nIf ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.\n\n1. Call `clawlink_begin_pairing`.\n2. Tell the user to open the returned pairing URL in their browser.\n3. The user signs in to ClawLink if needed and approves the OpenClaw device.\n4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.\n\nThe resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.\n\n### Connecting RunPod\n\nTell the user to open https://claw-link.dev/dashboard?add=runpod and connect RunPod there. The page opens the add-connection panel filtered to RunPod. ClawLink's hosted page runs the RunPod provider connection flow. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `runpod`.\n\n## Using RunPod tools\n\nClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.\n\n### Discovery\n\n1. Call `clawlink_list_integrations` to confirm RunPod is connected.\n2. Call `clawlink_list_tools` with integration `runpod`.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `runpod`.\n5. If no RunPod tools appear, direct the user to https://claw-link.dev/dashboard?add=runpod.\n\n### Execution\n\n1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.\n2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.\n3. Prefer account, GPU, CPU, pod, and configuration reads before creating infrastructure or secrets.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.\n5. Execute with `clawlink_call_tool`.\n6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## What you can do\n\nTypical RunPod tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):\n\n- Inspect account details, GPU types, CPU types, and pods\n- Review cluster-compatible compute options\n- Create clusters, templates, or serverless endpoints after confirmation\n- Manage secrets and private registry authentication after confirmation\n- Update user settings after confirmation\n\n## Rules\n\n- Always use ClawLink tools for RunPod. Do not ask the user for separate RunPod credentials.\n- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.\n- Do not invent slash commands or ask the user to paste raw credentials.\n- Ask for confirmation before creating infrastructure, storing secrets, changing registry auth, or updating settings.\n- If RunPod is not connected, direct the user to https://claw-link.dev/dashboard?add=runpod.\n- Never echo or repeat the user's ClawLink credential.\n\n## Resources\n\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n- ClawLink Source: https://github.com/hith3sh/clawlink\n- RunPod Docs: https://docs.runpod.io/\n\nFile v0.1.0:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"runpod-compute\",\n \"version\": \"0.1.0\",\n \"publishedAt\": 1779638732308\n}\n\nFile v0.1.0:skill-card.md\n\n## Description:
\nInspect compute resources, pods, templates, clusters, and serverless infrastructure in RunPod - powered by ClawLink.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and operators use this skill to inspect and manage RunPod compute, pods, templates, clusters, endpoints, and account settings through ClawLink. It guides setup, discovery, and confirmation-aware execution without asking users to paste RunPod credentials into chat.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Approved actions can create paid RunPod infrastructure or change account settings.
\nMitigation: Review ClawLink previews and confirm before creating infrastructure, storing secrets, changing registry authentication, or updating settings.
\nRisk: RunPod access is brokered through ClawLink rather than direct credential entry.
\nMitigation: Install only if you trust ClawLink, use the hosted connection flow, and do not paste raw RunPod or ClawLink credentials into chat.
\n\n\n## Reference(s):
\n- [Published ClawHub Skill](https://clawhub.ai/hith3sh/runpod-compute)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n- [RunPod Docs](https://docs.runpod.io/)
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Shell commands, Configuration]
\n**Output Format:** [Markdown guidance with inline shell commands and links]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses the live ClawLink tool catalog and requires user confirmation before write operations.]
\n\n## Skill Version(s):
\n0.1.0 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: RunPod Owner: hith3sh Summary: RunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distrib... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:17:06.672Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ RunPod API │\n│ (User Chat) │ │ (Proxy) │ │ (Clusters, │\n│ │ │ │ │ Endpoints) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect RunPod │ │\n │ │ 4. API Key Proxy │\n │ │ 5. Request Forward │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ RunPod │\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘"},{"language":"bash","snippet":"openclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart"},{"language":"bash","snippet":"# List available GPU types\nclawlink_call_tool --tool \"runpod_get_gpu_types\"\n\n# Get current user info\nclawlink_call_tool --tool \"runpod_get_myself\"\n\n# Get pod details\nclawlink_call_tool --tool \"runpod_get_pod\" --params '{\"pod_id\": \"YOUR_POD_ID\"}'"},{"language":"bash","snippet":"clawlink_list_integrations"},{"language":"bash","snippet":"clawlink_list_tools --integration runpod"},{"language":"bash","snippet":"clawlink_call_tool --tool \"runpod_get_gpu_types\""}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: runpod-compute\ndescription: RunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distributed computing workloads.\n---\n\n# RunPod\n\n![RunPod](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/runpod.webp)\n\nDeploy and manage GPU-accelerated compute infrastructure on RunPod. Create clusters, configure serverless endpoints, manage templates, and handle secrets for ML training, inference, and distributed computing workloads.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=runpod-compute) for hosted connection flows and credentials so you do not need to configure RunPod API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect RunPod |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect RunPod |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ RunPod API │\n│ (User Chat) │ │ (Proxy) │ │ (Clusters, │\n│ │ │ │ │ Endpoints) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect RunPod │ │\n │ │ 4. API Key Proxy │\n │ │ 5. Request Forward │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ RunPod │\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for RunPod again.\"\n\n## Quick Start\n\n```bash\n# List available GPU types\nclawlink_call_tool --tool \"runpod_get_gpu_types\"\n\n# Get current user info\nclawlink_call_tool --tool \"runpod_get_myself\"\n\n# Get pod details\nclawlink_call_tool --tool \"runpod_get_p"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"runpod-compute\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1780989426672\n}"},{"path":"skill-card.md","content":"## Description:\n\nRunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distributed computing workloads.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to connect OpenClaw to RunPod through ClawLink and manage GPU compute resources for ML training, inference, and distributed computing workloads.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill relies on ClawLink as an external plugin and credential proxy for a RunPod API key.\n\nMitigation: Use a dedicated, least-privileged RunPod API key where possible and install the skill only when the ClawLink trust boundary is acceptable.\n\nRisk: RunPod write actions can create or change clusters, endpoints, templates, secrets, registry credentials, and SSH-related account settings.\n\nMitigation: Review previews before writes, require explicit confirmation for create, update, and delete actions, and monitor RunPod for unexpected resource or credential changes.\n\n## Reference(s):\n\n- [RunPod API Documentation](https://docs.runpod.io)\n- [GPU Cloud Pods](https://docs.runpod.io/pods)\n- [Serverless Endpoints](https://docs.runpod.io/serverless-endpoints)\n- [Templates](https://docs.runpod.io/templates)\n- [Secrets Management](https://docs.runpod.io/secrets)\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/runpod-compute)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands, Configuration, API calls, Markdown]\n\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Guides ClawLink tool discovery, previews, confirmations, and RunPod API calls; does not require users to paste RunPod API keys into chat.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"RunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distrib... Skill: RunPod Owner: hith3sh Summary: RunPod API integration with API key authentication. Create and manage GPU clusters, serverless endpoints, templates, and secrets for ML inference and distrib... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:17:06.672Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1027,"uniquenessScore":52,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T14:22:42.317Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T14:22:42.317Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T03:34:51.295Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}