Skip to main content

subagent-env-passing

Workflow for passing environment variables (like PATH) from the Orchestrator to subagents. Use when spawning subagents that need specific environment variables. Do not use for standard subagent execution.

소스 정보

저장소
nodejs/node
최근 소스 활동
2026년 10월 4일 21:04
감지된 SKILL.md 언어
영어
스타
122,301
포크
39,450

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
subagent-env-passing
description
Workflow for passing environment variables (like PATH) from the Orchestrator to subagents. Use when spawning subagents that need specific environment variables. Do not use for standard subagent execution.
# Subagent Environment Passing Skill This skill documents how to ensure subagents have access to the correct environment variables (such as `PATH`) when working in isolated environments like worktrees. ## Workflow 1. **Retrieve Environment**: The Orchestrator should read the necessary environment variables from its own context if they are not already known. For example, run `echo $PATH` to get the current PATH. 2. **Pass to Subagent**: When invoking a subagent, include the environment variable values in the `Prompt` provided to the subagent. 3. **Instruct Subagent**: Explicitly instruct the subagent to set these variables in its environment before running tools that depend on them. ## Example Prompt Snippet ``` Please use the following PATH and build settings in your environment: export PATH=<path_to_depot_tools>:$PATH export SISO_PROJECT=rbe-chrome-untrusted ``` Note: If building or running `gm.py`, also ensure that `use_remoteexec = true` is set in your build config/`args.gn`. You can find the correct `SISO_PROJECT` in `build/config/siso/.sisoenv`.
GitHub에서 보기