Role
os-environment-probe asks the user which AI environments they have access to, then
verifies each claimed environment by running a lightweight probe command. Results are
written to context/memory/environment.md — a single source of truth that downstream
skills read to make delegation decisions without asking the user again.
Environment Interview
Ask the user these questions (one prompt, multiple-choice, keep it brief):
Which of these AI tools do you currently have active on this machine? (Select all that apply)
A. Claude Code only B. Claude Code + GitHub Copilot CLI (Pro or Business plan) C. Claude Code + Agy CLI (Antigravity — gemini-3.5-flash backend) D. Cursor (Claude or GPT backend) E. Other (describe)
Wait for their answer before probing.
Probe Commands
For each claimed environment, verify it is actually callable:
| Environment | Probe command | Pass condition |
|---|---|---|
| Copilot CLI | gh copilot explain "test" 2>&1 | head -3 |
No "not authenticated" or "command not found" |
| Agy CLI | agy --version 2>&1 | head -1 |
Outputs a version string |
| Cursor | cursor --version 2>&1 | head -1 |
Outputs a version string |
| Claude Code | always present | — |
Report each probe result to the user:
- Pass: "✓ Copilot CLI — confirmed"
- Fail: "✗ Copilot CLI — not found or not authenticated (skipping)"
Only write environments that pass to the profile.
Procedure
- Run the Environment Interview.
- Run the Probe Commands for each claimed environment; only environments that pass get written.
- Write
context/memory/environment.mdin the format inreferences/detailed-reference.md. - Downstream skills read this file: os-evolution-planner picks its brainstorm backend
(Copilot CLI → Agy CLI → Claude Haiku subagent, in that priority order); os-architect picks
its dispatch backend for Path B/C executions. If
environment.mdis missing, both default to Claude-only mode and offer to run this skill first. - Re-probe: running this skill again overwrites
context/memory/environment.mdwith fresh results — safe to re-run whenever the user's available environments change.
Output format, smoke tests, gotchas, and support-file details are in
references/detailed-reference.md.