What problem does it solve? When a response is slow, it is hard to tell which part — database, cache, auth, or an upstream call — caused the delay. This Skill instruments request handlers with a TimingCollector so every response carries a Server-Timing header that browser network panels display as per-segment timings. ## Core Features & Use Cases - Per-request timing collection: A TimingCollector lives for one request; its measure method wraps any async operation, records its duration, and returns the resolved value unchanged. - Header rendering: toString renders the header value and toHeaders writes it onto a Headers object, including copying immutable response headers into a new Response. - Zero-dependency and runtime-agnostic: The package has no dependencies and runs on any runtime that provides the standard Headers API. - Use Case: Wrap a findUserById database call with collector.measure("db", "findUserById", ...) and return the response with collector.toHeaders() so the browser network panel shows Server-Timing: db;desc="findUserById";dur=12.34. ## Quick Start Add @sdxc/server-timing as a workspace dependency and wrap my request handler's database and cache calls with a TimingCollector so every response includes a Server-Timing header.