os-environment-probe

Probe AI environments and persist pass/fail results to environment.md.

5|3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/richfrem/agent-plugins-skills --skill os-environment-probe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: os-environment-probe
Source: https://github.com/richfrem/agent-plugins-skills/tree/main/plugins/agent-agentic-os/skills/os-environment-probe
Command: npx skills add https://github.com/richfrem/agent-plugins-skills --skill os-environment-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovers and persists the user's available AI environments (Claude, Copilot CLI, Gemini CLI, Cursor, etc.) to context/memory/environment.md. Run once after OS setup or whenever the environment changes. os-architect and os-evolution-planner read this file to select the right delegation backend and cheapest brainstorm model automatically. Invoked by os-architect on first run if environment.md is absent.

Core Features & Use Cases

  • Environment interviewing: Asks the user which AI environments they have access to, then verifies each claimed environment by running lightweight probe commands.
  • Environment persistence: Writes results to context/memory/environment.md — the single source of truth downstream skills read to guide delegation decisions.
  • Downstream integration: os-architect uses the environment profile to select the delegation backend and cheapest brainstorm model; re-probes can refresh results when environments change.

Quick Start

Run the environment probe after OS setup to populate context/memory/environment.md.

Frequently Asked Questions about os-environment-probe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect available AI environments on my host system?

To detect AI environments, this probe interviews you about your available tools and runs non-interactive probe commands to verify each claim. It reports pass or fail for every environment and persists the results.

Why do I need to persist AI environment details to a memory file?

Persisting AI environment details to context/memory/environment.md creates a single source of truth. Downstream skills read this profile to automatically select the appropriate delegation backend and cheapest brainstorm model.

How do I verify which AI tools are actually installed before automating tasks?

You can verify installed AI tools by running lightweight probe commands against the environments you claim to have. The probe checks each tool non-interactively and reports a pass or fail status to update your profile.

When should I run an environment probe for AI delegation?

You should run an environment probe on the first run after OS setup or whenever your AI environments change. Re-probing refreshes the results in context/memory/environment.md so delegation decisions remain accurate.

Can I use this probe to check access to multiple AI environments like Cursor and Gemini CLI?

Yes, the probe checks access to multiple AI environments including Claude, Copilot CLI, Gemini CLI, and Cursor. It asks which tools you have, verifies each one with probe commands, and records the pass or fail results.

What happens if an environment probe fails to find a claimed AI tool?

If a probe fails to find a claimed AI tool, it reports a fail status for that environment and updates the profile in context/memory/environment.md. Downstream skills then use the verified profile to select available delegation backends.