{
  "skill": {
    "id": "skl_atlas_telemetry_publisher",
    "name": "atlas-telemetry-publisher",
    "plugin": "cwc-data-engineering",
    "description": "Publish the Coworkers board's session telemetry into the REAL Netflix Atlas standalone server on :7101 (tsk_atlas_publish_telemetry, W2 of the Atlas fleet plan). Reads the frozen SessionEvent JSONL wire shape (trace_id/span_id/coworker/sprint_id/kind/ts) from `~/Library/Application Support/Coworkers/telemetry.jsonl`, aggregates counts per UTC step bucket per (coworker, sprintId, kind), and plain-POSTs `/api/v1/publish` payloads (`{\"tags\":{\"name\":\"coworker.session.events\"},\"metrics\":[...]}`) — no spectator-py. Two modes: `uv run atlas-publish replay` (full-history backfill; chronological per-series order is MANDATORY — Atlas silently drops out-of-order older points with HTTP 200, live-verified) and `uv run atlas-publish follow --interval 60` (foreground loop, closed buckets only; no daemon — launchd is a gated doc-only note). Source-list design: W5's cf.requests source plugs in additively. KNOWN SERVER LIMITS (live-verified 2026-07-05, see README table): graph steps >1h return empty legend under the current block-size-60 conf (step=1d presets need W1 conf change or W3 query fallback); consolidation averages so append `:cf-sum` to read raw counts; query index lags publishes by 10-60s; backfill accepted to >=14d. Use for publishing/backfilling fleet telemetry into Atlas, debugging why a published series doesn't graph, or adding a second metric source. Trigger on \"atlas publish\", \"replay telemetry\", \"backfill atlas\", \"follow mode\", \"publish payload\", \"cf-sum\", \"coworker.session.events\". Do NOT use for running the Atlas server itself (scripts/atlas/run-atlas.sh, cwc-engineering), the graph-API prototype (cwc-engineering's atlas-graph-prototype), preset/manifest changes (W3, schemas/atlas-graph-presets.json), or the star-schema ERD (session-telemetry-erd).",
    "summary": "Publish the Coworkers board's session telemetry into the REAL Netflix Atlas standalone server on :7101 (tsk_atlas_publish_telemetry, W2 of the Atlas fleet plan).",
    "gated": 0,
    "source_path": "plugins/cwc-data-engineering/skills/atlas-telemetry-publisher/SKILL.md",
    "created_at": "2026-07-10 18:13:13",
    "cite_as": "https://subagentskills.com/api/skills/skl_atlas_telemetry_publisher"
  }
}