stream-swift

Build, integrate, migrate to, and answer how-to questions for Stream Chat, Video, and Feeds in Swift / SwiftUI / UIKit / iOS apps. Routes each request to the exact official iOS docs page, fetches it live, and applies it - with a curated setup flow, a Sendbird -> Stream Chat migration runbook, and iOS-specific pitfalls.

1.59x

Quality

—

Does it follow best practices?

Impact

97%

1.59x

Average score across 2 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

50%

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

A densely expert orchestrator body with a clear classification-to-docs-lookup workflow and good one-level-deep reference signaling, undermined by verbose run-on paragraphs and - critically - a bundle whose seven referenced files are all missing. The structure is sound but the progressive disclosure leads nowhere.

Suggestions

Break the two giant run-on paragraphs (the Sendbird-migration mode and the styling-depth flag) into bulleted routing rules and trap lists so the guidance is scannable instead of a wall of prose.

Ship the referenced bundle files (RULES.md, docs-map.md, setup.md, push.md, design-matching.md, custom-ui.md, sendbird-migration.md) alongside SKILL.md, or inline the essential parts - currently every "See X.md" link is a dead end.

Add crisp, formatted validation checkpoints (e.g. explicit build -> run -> seed -> compare -> iterate checklist) for the migration and design-matching workflows instead of embedding them in narrative prose.

Dimension	Reasoning	Score
Conciseness	The body is substantive and avoids explaining concepts Claude already knows, but it is verbose: two enormous run-on paragraphs (the Sendbird-migration mode and the styling-depth flag) pack routing rules, axes, and traps into prose that could be tightened into lists.	2 / 3
Actionability	Concrete routing guidance is present (the drop-/-add-.md URL convention with an example, the live index table, numbered lookup steps, a citation format), but the executable code and commands are deferred to referenced files rather than being copy-paste ready in the body.	2 / 3
Workflow Clarity	A clear Step 0 -> Step 1 -> Setup sequence exists with feedback loops (escalate to SDK source when docs fall short, ask one question if ambiguous, build/run/compare/iterate for design matching), but the checkpoints are buried in dense prose rather than crisply formatted, and substantial migration/build operations are involved.	2 / 3
Progressive Disclosure	The overview is well-organized with clearly signaled one-level-deep markdown links to RULES.md, docs-map.md, setup.md, push.md, design-matching.md, custom-ui.md, and sendbird-migration.md, but none of these referenced files exist in the bundle and there are no references/scripts/assets directories, so the navigation is broken in practice.	2 / 3
	Total	8 / 12 Passed

Description

82%

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

A specific, well-targeted description that names concrete actions and natural product/framework trigger terms with low conflict risk. Its only real gap is the missing explicit "Use when..." trigger clause, which caps completeness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions - "Build, integrate, migrate to, and answer how-to questions", "Routes each request to the exact official iOS docs page, fetches it live, and applies it" - plus a setup flow, a Sendbird migration runbook, and iOS pitfalls.	3 / 3
Completeness	The "what" is strong and explicit, but there is no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Covers natural terms users would say - "Stream Chat, Video, and Feeds", "Swift / SwiftUI / UIKit / iOS", "Sendbird -> Stream Chat migration" - which are exactly the product and framework names a user would mention.	3 / 3
Distinctiveness Conflict Risk	A clear niche - Stream Chat/Video/Feeds on iOS plus Sendbird migration - with distinct product-specific triggers that are unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: 28 missing, 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: GetStream/agent-skills
Commit: b81d80e

Reviewed: 4 days 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.