Red5 published a review of the agent skills available for building live streaming apps, and the unusual thing about it is the list. A vendor writing about skills could have written about its own. Red5 reviewed four public offerings instead — its own red5pro/red5pro-skills, Agora’s AgoraIO/skills, Bitmovin’s product skills, and Bitmovin’s separate video-dev-skill — and evaluated them against criteria any of the four could fail. The protocol list the skills have to reason about explains why the category exists at all: WebRTC, RTMP, RTSP, SRT, WHIP, WHEP, enhanced RTMP, Zixi, HLS and DASH, across players from hls.js and Shaka to AVPlayer and ExoPlayer. That is not a surface anyone holds in their head, and it is exactly the kind a model will confidently get wrong.
The criteria are the useful part. Portability first: “a skill is more practical when developers can use it with their preferred assistant without rebuilding its architecture or copying a large prompt into every session.” Then a refusal to let the category oversell itself — “the best agent skills make these controls easier to apply. They do not remove the need for them” — and a line about accountability that would sit comfortably in any code-review policy: “a good skill helps an AI assistant write less speculative code. A good engineering team still decides whether that code belongs in the product.” The one soft spot is latency: Red5 Pro is described as ultra-low latency, with no number attached, in a piece that is otherwise careful to be specific.
Here the catalog has something unusual to report: it already agrees. Red5 has its skills registered — both of them, red5pro and red5-cloud-pubnub, mirrored from the first-party repository alongside its AGENTS.md, with the npx red5pro-skills installer noted. The APIs those skills drive are in the record too, 17 pages of them: the Red5 Pro WebRTC SDK and the iOS and Android SDKs on the client side, and on the server the Provision API, the RTMP Restreamer API, the Mixers API and the Admin API.
Red5 scores 65.6, strong on the Kin Score — access clarity 85.5, discoverability 81.5, developer ergonomics 78.6 — among the better records in media infrastructure. Agent Readiness is 28.6, agent-ready, with agent_skills, event_surface_described, error_semantics and openapi_examples lit. After a run of posts where a provider wrote the definitive guide to a thing its own contract does not declare, this is the other case, and it deserves saying plainly: the skills Red5 wrote about exist, are public, and are in the catalog. What is dark is narrower. mcp_server is unlit, which fits a company that chose skills as its agent surface, and idempotency is unlit on a provisioning API, where a retried create is a second stream you are paying for.