Individual skill
tensorpool-gpu-cloud
Safely inspect and operate TensorPool GPU clusters and jobs using the current tp CLI, with explicit approval before any billable or destructive action.
backend/cli/skills/cloud-compute/tensorpool/SKILL.md
Source commit a08e0ad0ad3d6448123039ee4659163eb2e35d99
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 4,353
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- bun Repository topic
- cli Repository topic
- llm Repository topic
- ml Repository topic
- open-source Repository topic
- research Repository topic
- science Repository topic
- ai-agent Repository topic
- infrastructure Declared skill tag
- gpu-cloud Declared skill tag
- tensorpool Declared skill tag
- clusters Declared skill tag
- jobs Declared skill tag
- ssh Declared skill tag
- devops Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# TensorPool GPU Cloud
Use this skill for TensorPool cluster, job, and storage workflows. Treat provider availability, instance names, quotas, and prices as live data: inspect them at execution time and never rely on values copied into a skill.
## OpenScience credential boundary
- A key saved in **Customize > Compute > TensorPool** is encrypted control-plane data. It is not exported into Bash, Task, notebooks, kernels, plugins, or MCP servers.
- Use `provider_compute` with `account`, `list_resources`, `resource_status`, `list_jobs`, or `job_status` for live reads. OpenScience selects the exact reviewed `tp` argv, admits the key only to that isolated child, and marks `last_used` only after success.
- **Test connection** uses the same boundary for exactly `tp --no-input me`.
- The saved key is admitted only when **Test connection** approves a root/admin-managed, non-writable `tp` executable. A normal user-owned pip, pipx, or Homebrew install is credential-only and cannot be used by `provider_compute`; use an administrator-managed install or wait for a managed/native adapter.
- Never print, echo, persist, or ask the user to paste a saved key into chat.
- A generic agent shell can use `tp` only when the user has independently authenticated that shell. The saved credential cannot create, submit, edit, attach, destroy, or otherwise mutate resources; do not ask the user to weaken this boundary.
## Current CLI contract