Name: stream-unity
Rating: 73.6 (1 reviews)
Author: GetStream

stream-unity

Build, integrate, and answer how-to questions for Stream Chat and Stream Video in Unity Engine games and apps. Use for Unity / C# / MonoBehaviour project work - the Chat .unitypackage and the Video UPM package, StreamChatClient / StreamVideoClient wiring, ConnectUserAsync and tokens, channels and messages, calls and participant tracks, camera and microphone devices, building the UI yourself on UGUI or UI Toolkit, IL2CPP, and Android / iOS / desktop / WebGL player settings. Triggers on unity, unity engine, unity 6, unity 2022, monobehaviour, .unitypackage, Packages/manifest.json, asmdef, il2cpp, ugui, rawimage, audiosource, webcamtexture, StreamChatClient, IStreamChatClient, IStreamChannel, StreamVideoClient, IStreamVideoClient, IStreamCall, StreamVideoTrack, in-game chat, unity video call. Chat and Video only - there is no Stream Feeds SDK for Unity.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly written, well-sequenced orchestrator for a genuinely complex two-SDK domain: it assumes competence, gates risky moves, and routes to docs precisely. Its one real weakness is that every detailed reference points at bundle files that are missing from the working directory, so progressive disclosure is promised but not shipped.

Suggestions

Ship the five referenced bundle files (RULES.md, setup.md, ui.md, platforms.md, docs-map.md) referenced by SKILL.md, or remove the references and inline the load-bearing parts so the skill is self-contained.

Add at least one minimal copy-paste Unity code block (e.g. the verified client wiring) in the body to lift actionability from mostly-executable to fully-executable.

Verify the live-index URLs (getstream.io/cli/docs/chat-unity.md and video-unity.md) resolve, since the body treats them as authoritative fallbacks.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence throughout: no basic-concept padding, every line carries Unity-specific knowledge the docs lack ("the client's hidden DontDestroyOnLoad runner", IL2CPP stripping, the fence-label trap). Dense tables rather than prose, so length is justified by information density.	5 / 5
Actionability	Concrete executable guidance (the read-only bash probe, exact version floors like "Never pin Chat below v5.4.0 on Unity 6", the .md URL convention), but the body routes to docs rather than carrying full copy-paste Unity code, leaving it just shy of the 'fully executable, copy-paste ready' anchor.	4 / 5
Workflow Clarity	A clear three-gate sequence before any code (product, version/target, feature support) with explicit hard stops ("Hard stop for Video"), a numbered Step 0/1/2 flow, and a source-of-truth ladder with 'Stop at the first rung' and 'Only proceed when valid' style checkpoints.	5 / 5
Progressive Disclosure	The overview references five files one level deep with a clear table and inline links, which would score higher, but the referenced files (RULES.md, setup.md, ui.md, platforms.md, docs-map.md) are not present in the bundle - only SKILL.md exists - so the navigation is signaled but not actually deliverable.	3 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: concrete capabilities, an explicit 'Use for'/'Triggers on' clause, comprehensive natural trigger terms including synonyms, and a clear niche with an explicit non-scope boundary. It hits the top anchor on all four dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Build, integrate, and answer how-to questions") plus a comprehensive set of concrete capability nouns (wiring, tokens, channels, tracks, IL2CPP, player settings), matching the 'multiple specific concrete actions; comprehensive coverage' anchor.	5 / 5
Completeness	Explicitly answers both what ("Build, integrate, and answer how-to questions for Stream Chat and Stream Video in Unity") and when ("Use for..." plus "Triggers on..."), matching the 'clearly and explicitly answers both what AND when' anchor.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural terms and synonyms ("unity, unity engine, unity 6, unity 2022", "in-game chat", "unity video call") plus file markers and type names, matching the 'comprehensive coverage including synonyms' anchor.	5 / 5
Distinctiveness Conflict Risk	A clear narrow niche (Stream Chat and Video in Unity Engine) with an explicit boundary statement ("Chat and Video only - there is no Stream Feeds SDK for Unity"), giving minimal conflict risk as the anchor requires.	5 / 5
	Total	20 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 19 missing	Warning

	Total	13 / 16 Passed

Repository: GetStream/agent-skills
Path: skills/stream-unity/SKILL.md
Commit: 7db97e6

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.