What problem does it solve? SRS and Oryx projects ship large documentation sets spanning the C++ media server, Oryx platform, website pages, changelogs, and the next-generation Go proxy. Without a router, agents waste context loading irrelevant documents or grep broadly across documentation trees, producing slow and unreliable answers. ## Core Features & Use Cases - Reference Router: Maps task types (RTMP, WebRTC, HLS, SRT, DVR, HTTP callbacks, security, performance, and more) to the smallest relevant set of trusted documentation files. - Path Resolution Rules: Distinguishes bundled skill-relative paths from repository-relative paths, including special handling for the Oryx checkout at the project-root oryx/ path. - Documentation Maintenance: Defines rules for keeping the router updated when trusted documents are added, removed, renamed, or change responsibility. - Use Case: When asked how to configure SRS HTTP callbacks for stream authentication, the skill routes directly to references/cpp-docs/doc/http-callback.md instead of scanning the entire documentation tree. ## Quick Start Ask the agent to find the trusted SRS documentation for configuring HLS low-latency delivery and it will route to the correct reference file.
