create-otel-instrumentation-reportlisted

# Create an OTel Instrumentation Report An instrumentation investigation that vanishes with the conversation must be redone from scratch the next time the stack changes. This skill defines the file contract that persists it: reports live **in the investigated repository**, so git versions them, PRs review them, and every user of the repo shares them — the next SDD instrumentation wave starts from what the last investigation already established. ## Where reports live ```text <investigated-repo-root>/.odd/otel-instrumentation-reports/YYYY-MM-DD-HHmm-<run_name>.md ``` - `YYYY-MM-DD-HHmm` is the investigation's **UTC** start time — to the minute so two same-day runs never collide, and a plain directory listing sorts chronologically. Compute it, and the `date:` field, with `date -u`, never from the local clock: a session that crosses local midnight while UTC has not names the wrong day. - `<run_name>` is a short kebab-case slug naming what was investigated (e.g. `mcp-server-python`, `checkout-monorepo-full`). Name the content, not the date. - Create the directory if it does not exist. The files are meant to be **committed**: leave them tracked, never add them to `.gitignore`. ## The file format A YAML frontmatter, then the complete report: ```markdown --- project: oddyssey/src/mcp-server stack: local # local | the remote backend name (grafana, datadog, ...) run_name: mcp-server-python date: 2026-08-23 revision: 2299d4c # optional: