Isolated Workspace

The name/description (isolated git workspace) aligns with the SKILL.md. It only uses git, project files (package.json, requirements.txt, etc.), and standard build/test commands; there are no unrelated env vars, binaries, or installs requested.

Instructions stay within the stated purpose (select/verify an isolation directory, create a branch, install deps, run tests). Important security note: running npm/pip/cargo/go commands and project tests can execute code from third-party dependencies or repository scripts (postinstall, setup.py, build.rs, test suites). The SKILL.md does not mandate explicit user confirmation before running installations and tests, so if executed autonomously it could run arbitrary code in the host environment. The skill also commits .gitignore changes to the repository, which is expected but is writable repo modification.

There is no install spec and no code files—this is instruction-only. That minimizes disk-write and supply-chain risks from skill installation itself.

The skill does not request environment variables, credentials, or config paths. It operates on repository files and runs standard developer tooling; this is proportionate to the stated purpose. Note: the commands will use network access to fetch packages and will run with the agent's user privileges.

always is false and the skill does not request persistent presence or modify other skills. It does instruct committing changes to the repository (e.g., adding .gitignore), which is within scope but is a persistent repo change the user should review.