terminalx-per-workspace-env
Skill0 starsChanged 3 months agoMITView on GitHub
Set up, review, debug, or validate TerminalX per-workspace environment recipes — on-demand, disposable runtimes (cloud sandboxes, VMs, or local) created fresh for each workspace. Covers first-time setup (provider prerequisites, the reusable base snapshot, the coding-agent auth snapshot, credentials, and state), not just the per-workspace lifecycle scripts. Use to stand up per-workspace environments, fix an `environmentRecipes` entry in `terminalx.yaml`, scaffold provider lifecycle scripts, or resolve an `terminalx vm recipe doctor` failure.
In this repository7 other files it gives its agents.
- computer-useSkill
- linear-ticketsSkill
- orchestrationSkill
- terminalx-cliSkill
- terminalx-emulator-androidSkill
- terminalx-emulatorSkill
- terminalx-linearSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
If the TERMINALX_CLI_COMMAND environment variable is set, use its value.
- Distinctive: line 44
If the selected executable cannot run, report its exact error and stop.
- Distinctive: line 58
Don't guess subcommands or flags from memory or from a cached copy of this stub.
- Very specific: line 65
Use this fallback only when the selected binary explicitly reports that skills get is an unknown command.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Per-Workspace Environments
This file is a discovery stub, not the usage guide. The full, version-matched per-workspace
environment reference is served by the terminalx binary itself — kept out of this file on
purpose so it can never drift from the binary that will actually run your commands.
Engage TerminalX whenever you set up, review, debug, or validate a per-workspace environment
recipe — the on-demand, disposable runtimes (cloud sandboxes, VMs, or local) created fresh
for each workspace. This covers first-time setup (provider prerequisites, the reusable base
snapshot, the coding-agent auth snapshot, credentials, and state), not just the
per-workspace lifecycle scripts. Use it to stand up per-workspace environments, fix an
environmentRecipes entry in terminalx.yaml, scaffold provider lifecycle scripts, or resolve
an terminalx vm recipe doctor failure. TerminalX is a thin wrapper: you guide, detect, and scaffold;
you never own the user's cloud account, billing, images, or credentials, and never spend
money without an explicit user OK.
Resolve the CLI for this session
Choose the executable once and reuse it for every later command:
- If the
TERMINALX_CLI_COMMANDenvironment variable is set, use its value. TerminalX exports this for managed WSL sessions. - Otherwise, in a dev checkout whose session exposes
TERMINALX_DEV_REPO_ROOT, useterminalx-dev. - Otherwise, on Linux outside a TerminalX-managed terminal, use
terminalx-ide. That is the executable name the Linux package installs; bareterminalxis not on PATH outside TerminalX's terminals. - Otherwise, use
terminalx.
Below, TERMINALX is a placeholder for the executable you resolved. Substitute it before
running anything; do not create a shell variable or run TERMINALX literally. This works the
same way in POSIX shells, PowerShell, and cmd.exe.
If the selected executable cannot run, report its exact error and stop. Do not fall through to another executable, which could silently target a different TerminalX build.
Load the full guide before running TerminalX commands
TERMINALX skills get terminalx-per-workspace-envThat prints the complete, version-matched guide for the exact binary that will handle your
next commands — provider setup, base and auth snapshots, environmentRecipes in
terminalx.yaml, lifecycle scripts, and terminalx vm recipe doctor. Read it first, then run the
specific command you need.
Don't guess subcommands or flags from memory or from a cached copy of this stub. They
change between TerminalX releases, and this file deliberately no longer lists them. Confirm the
app is up with TERMINALX status --json (start it with TERMINALX open --json if needed), and
prefer --json for agent-driven calls.
If an older TerminalX does not recognize skills get
Use this fallback only when the selected binary explicitly reports that skills get is an
unknown command. Another failure is not proof of an older binary; report it rather than
guessing or changing executables. For a confirmed pre-guide binary, use only this bounded,
read-only bootstrap to orient. Do not dead-end and do not invent commands:
TERMINALX status --json
TERMINALX vm recipe doctor <recipe-id> --repo-path <repo> --jsonThe doctor command above is the free static check. Never add --provision without the
user's explicit approval because it creates provider resources and may spend money.
Then tell the user that updating TerminalX restores the full, version-matched guide via
TERMINALX skills get terminalx-per-workspace-env. Beyond these commands, ask the user rather than
guessing a command surface this older binary may not support.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

