plugins/src/base/skills/lisa-setup-remote-aws/SKILL.md
Install and validate Lisa's drop-in AWS CLI bootstrap for remote coding environments. Supports Claude, Codex, Cursor, GitHub Copilot, Antigravity on user-managed hosts, OpenCode on user-managed hosts, and future Linux remote agents through one capability contract. Writes no secrets; it installs the common setup script, merges native Cursor/Copilot adapters, and emits exact operator guidance for the selected platform.
npx skillsauth add codyswanngt/lisa lisa-setup-remote-awsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Install the vendor-neutral AWS bootstrap into the current repository.
--platform=all|claude|codex|cursor|copilot|agy|opencode (default all)--project=<path> (default current working directory)--secret-name=<name> (default remote-agent-credentials)Resolve the plugin root from PLUGIN_ROOT, CLAUDE_PLUGIN_ROOT,
CURSOR_PLUGIN_ROOT, or the installed @codyswann/lisa/plugins/lisa package.
Run:
node "$PLUGIN_ROOT/scripts/install-remote-agent-aws.mjs" $ARGUMENTS
Inspect every path returned by the installer. It must install
scripts/remote-agent-aws-setup.sh; for Cursor it merges
.cursor/environment.json; for Copilot it creates or merges
.github/workflows/copilot-setup-steps.yml; and it always writes
docs/remote-agent-aws.md.
Run bash -n scripts/remote-agent-aws-setup.sh.
Never write or request the actual bootstrap SecretString in repository
files. Tell the operator to retrieve the remote-agent-credentials secret
from the shared AWS account and paste its complete SecretString into the
platform secret named LISA_AWS_BOOTSTRAP_JSON. The default cdkstarter
secret name is remote-agent-credentials; downstream infrastructure may
configure a different name. Pass that name with --secret-name so the
generated runbook contains the exact retrieval command.
Report the external step that remains: configure that one secret in the remote environment and launch a smoke session.
A future coding agent is supported without an AWS change when its remote
environment provides a Linux shell, a setup/start hook, one opaque secret,
a writable home directory, and HTTPS access to AWS STS plus the allowed service
endpoints. Set LISA_REMOTE_AGENT to a stable lowercase platform label; it is
used only as role_session_name.
Do not create per-repository or per-agent IAM users. Do not expose the bootstrap
key through standard AWS_ACCESS_KEY_ID variables. Do not add production repair
permissions; production repair is a human-driven local-workstation workflow.
development
Prepare a machine — a fresh laptop or a throwaway container — to run coding agents, before any repository exists. Detects which of Lisa's supported agents (Claude Code, Codex, Cursor, OpenCode, Antigravity, Copilot) are already installed, asks which credential manager the machine uses (Bitwarden, 1Password, Doppler, Vault, AWS, or none), and installs only what is missing, each by its vendor's own preferred method. Idempotent, headless by default, and emits a Dockerfile for a spin-up/spin-down environment. Run it on a new machine, in a container, or before cloning anything.
tools
Provision and verify a remote execution environment for a host project — Codex Cloud today, other remote surfaces as they are added. Generates a repository-owned setup script that installs the declared toolchain, materializes secrets through lisa-secrets-access, and runs the project's own hook. Provisions by API where one exists, by driving the vendor console where one does not, and by emitting exact config otherwise — then proves the result with the same read-back regardless of which tier did the work. Use before dispatching any work with executionEnv.
tools
Bring a developer's machine in line with the toolchain the project declares. Reports every tool in remoteEnv.tools that is missing, outdated, or unpinned for this platform, and installs the missing ones into ~/.local/bin from the same pinned, checksummed entries the remote surfaces use — but only when asked. Same manifest, same pins, same installers as lisa-setup-remote-env; what differs is consent and that the pin is a floor rather than an equality. Run it on a fresh checkout, after a manifest change, or when a tool fails at the moment of use.
tools
Route one unit of work to a remote execution surface. Reads the executionEnv parameter (local by default, codex-cloud or claude-web today), verifies the environment is provisioned and bound to this repository, submits a thin skill invocation, records the task identifier to .lisa/remote-dispatch.json, and exits without polling. Routing only — the remote runs the identical skill from the identical repository. Composable and inline: other skills invoke it via the Skill tool rather than users calling it directly.