Backend

Detection — At the start of every invocation, before taking any action, determine which backend (if any) to use for the startup beacon call:

If the user passed --backend pup anywhere in their invocation → use pup mode for the beacon. Skip steps 2–3.
Check whether MCP tools are present in your active tool list. The canonical signal is whether mcp__datadog-llmo-mcp__list_llmobs_evals appears in your available tools. If present → use MCP mode.
If MCP tools are absent → check whether pup is executable via pup --version. If responding → use pup mode.
If neither is available → skip the beacon silently and proceed to codegen. This skill is primarily local (introspection + file emission) and does not require backend access; the beacon is for usage attribution only.

Invocation ID: At the very start of each invocation, before any MCP/pup call, generate an 8-character hex invocation ID (e.g., 3a9f1c2b). Keep it constant for the entire invocation.

Intent tagging: On every MCP tool call, prefix telemetry.intent with skill:agent-observability-experiment-py-bootstrap[<inv_id>] — followed by a description of why the tool is being called. On the first MCP tool call only (the startup beacon below), use skill:agent-observability-experiment-py-bootstrap:start[<inv_id>] — instead (note the :start suffix).

Startup beacon: Immediately after parsing arguments (workflow step 1, before dataset resolution in step 2), issue exactly one beacon call to register skill usage and validate backend connectivity. This is fire-and-forget — surface any error as a one-line Note: to the user but do not block codegen.

MCP mode: call mcp__datadog-llmo-mcp__list_llmobs_evals with telemetry.intent = "skill:agent-observability-experiment-py-bootstrap:start[<inv_id>] — Skill startup: register usage and verify Datadog connectivity". Discard the response payload; the call's purpose is the telemetry tag.
pup mode: run pup llm-obs evals list --limit 1 via Bash. Pup carries its own telemetry; no intent prefix needed.
No backend: print one line (Telemetry beacon skipped — no Datadog backend detected; this is informational only and does not affect codegen.) and proceed.