container-probe

Report the container environment marker, hostname, and working directory of the current session.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/74th/test-llm-agent --skill container-probe-74th
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: container-probe
Source: https://github.com/74th/test-llm-agent/tree/main/20260922-claude-managed-agents/skills/container-probe
Command: npx skills add https://github.com/74th/test-llm-agent --skill container-probe-74th

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running AI agents across multiple containers or managed environments, it is hard to verify which environment a session's tools actually execute in and whether a skill was loaded and followed. This Skill provides a deterministic probe that confirms the execution context. ## Core Features & Use Cases - Environment Marker Check: Reads /etc/cma-verification-marker and reports its contents, or MISSING if absent. - Fixed Output Format: Emits exactly three parseable lines (marker, hostname, workdir) so a verification driver can mechanically distinguish a correctly loaded skill from an unattached one. - Use Case: A verification harness asks the agent to "probe the container" and parses the three-line response to confirm the session runs in the expected container with the expected marker file. ## Quick Start Ask the agent to probe the container and report the environment marker, hostname, and working directory.

Frequently Asked Questions about container-probe

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

FAQPage Schema
How do I check which container my agent session is running in?▼

Invoke the probe to read /etc/cma-verification-marker, run hostname, and print the working directory after cd /workspace. The three-line output identifies the exact container environment of the session.

How to verify an AI agent skill was loaded and followed?▼

Ask the agent to probe the container and check for the fixed three-line CONTAINER_PROBE output. Free-text answers or a missing marker line indicate the skill was not attached or not read.

What happens if the verification marker file does not exist?▼

If /etc/cma-verification-marker is missing, the probe reports the literal string MISSING for the marker line instead of the command's error text, keeping the output format parseable.

What tools does the container probe require?▼

The probe requires bash and read tool access to run cat, hostname, and cd /workspace && pwd. Without shell access the environment facts cannot be gathered.

Why does the probe output have no extra commentary?▼

The caller parses the output mechanically, so the probe prints exactly three lines in a fixed order with no summaries or explanations. Extra text would break automated verification.