How do I install the Manta Per Workspace Env skill?

Run npx skillmds@latest add paidaxingyo666/manta-per-workspace-env in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Manta Per Workspace Env safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Manta Per Workspace Env?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Manta Per Workspace Env free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Manta Per Workspace Env?

paidaxingyo666 (@paidaxingyo666) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Manta Per Workspace Env by paidaxingyo666

Name: Manta Per Workspace Env
Author: paidaxingyo666

Manta Per Workspace Env

Set up, review, debug, or validate a Manta per-workspace environment recipe: the on-demand, disposable runtime (cloud sandbox, VM, SSH host, or local container) Manta creates fresh for each workspace. Use to stand up a new recipe end to end, fix an `environmentRecipes` entry in `manta.yaml`, scaffold provider lifecycle scripts, or resolve an `manta vm recipe doctor` failure. Use `manta-cli` for ordinary worktree and workspace creation with no recipe involved.

File contents

Per-Workspace Environments

This discovery stub loads the version-matched guide from the Manta executable used for this session.

Resolve the CLI for this session

Choose the executable once and reuse it for every later command:

If the MANTA_CLI_COMMAND environment variable is set, use its value. Manta exports this for managed WSL sessions.
Otherwise, in a dev checkout whose session exposes MANTA_DEV_REPO_ROOT, use manta-dev.
Otherwise, on Linux outside a Manta-managed terminal, use manta-ide. Never run bare manta there — outside Manta's terminals it normally resolves to the GNOME Orca screen reader (/usr/bin/orca) and starts speech on the user's machine.
Otherwise, use manta.

Below, MANTA is a placeholder for the executable you resolved. Substitute it before running anything; do not create a shell variable or run MANTA 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 Manta build.

Load the version-matched guide before running Manta commands

MANTA skills get manta-per-workspace-env

Prefer --json. Use the selected executable's --help for commands or flags the guide does not cover. If a command reports that Manta is not running, start it with MANTA open --json and retry. If skills get is unknown, explain that updating Manta restores the guide; use --help for read-only discovery and do not guess unsupported commands.

---name: manta-per-workspace-envdescription: Set up, review, debug, or validate a Manta per-workspace environment recipe: the on-demand, disposable runtime (cloud sandbox, VM, SSH host, or local container) Manta creates fresh for each workspace. Use to stand up a new recipe end to end, fix an `environmentRecipes` entry in `manta.yaml`, scaffold provider lifecycle scripts, or resolve an `manta vm recipe doctor` failure. Use `manta-cli` for ordinary worktree and workspace creation with no recipe involved.---# Per-Workspace EnvironmentsThis discovery stub loads the version-matched guide from the Manta executable used for this session.## Resolve the CLI for this sessionChoose the executable once and reuse it for every later command:- If the `MANTA_CLI_COMMAND` environment variable is set, use its value. Manta exports this for managed WSL sessions.- Otherwise, in a dev checkout whose session exposes `MANTA_DEV_REPO_ROOT`, use `manta-dev`.- Otherwise, on Linux outside a Manta-managed terminal, use `manta-ide`. Never run bare `manta` there — outside Manta's terminals it normally resolves to the GNOME Orca screen reader (`/usr/bin/orca`) and starts speech on the user's machine.- Otherwise, use `manta`.Below, `MANTA` is a placeholder for the executable you resolved. Substitute it beforerunning anything; do not create a shell variable or run `MANTA` literally. This works thesame way in POSIX shells, PowerShell, and cmd.exe.If the selected executable cannot run, report its exact error and stop. Do not fall throughto another executable, which could silently target a different Manta build.## Load the version-matched guide before running Manta commands```textMANTA skills get manta-per-workspace-env```Prefer `--json`. Use the selected executable's `--help` for commands or flags the guide doesnot cover. If a command reports that Manta is not running, start it with `MANTA open --json`and retry. If `skills get` is unknown, explain that updating Manta restores the guide; use`--help` for read-only discovery and do not guess unsupported commands.

Frequently asked questions