Name: stream-swift
Rating: 72.89 (1 reviews)
Author: GetStream

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

73%

Does it follow best practices?

Impact

97%

1.59x

Average score across 2 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/stream-swift/SKILL.md

Quality

Content

71%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 well-structured orchestrator skill with excellent progressive disclosure, strong actionability, and a clear sequenced workflow; its main weakness is verbosity in the styling-depth and strategy sections, where repeated emphasis could be trimmed.

Suggestions

Break the styling-depth paragraph (Step 0) into a short checklist or bullet list and remove the repeated exhortation sentences to improve token efficiency.

Trim the moralizing refrains ('is a FAIL, not a footnote', 'the common, expensive mistake') to a single concise warning each.

Consider collapsing the two large strategy paragraphs (lines 83 and 85) into the decision table plus one short prose paragraph to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	Information-dense and mostly earned, but the styling-depth paragraph (one ~500-word block) and repeated exhortation sentences ('a region left at the SDK default is a FAIL, not a footnote', 'over-choosing custom ... is the common, expensive mistake') could be tightened; it does not explain concepts Claude already knows, so it stays above a 2.	3 / 5
Actionability	Gives a concrete URL transformation with a worked example, a live index URL table, decision tables routing to named runbooks, and specific slot identifiers (makeMessageItemView, makeComposerInputTrailingView) — mostly executable guidance with minor gaps since most code lives in referenced files.	4 / 5
Workflow Clarity	Clear Step 0 (classify) -> Step 1 (docs lookup) -> Setup sequence with checkpoints (cite the page, escalate to source when docs fall short, build/run/seed/compare/iterate for design matching); minor validation gaps across the many branches keep it below 5.	4 / 5
Progressive Disclosure	A clear overview with well-signaled one-level-deep references ([text](file.md) links to RULES.md, setup.md, push.md, design-matching.md, custom-ui.md, sendbird-migration.md, docs-map.md), content appropriately split into dedicated runbooks, and easy navigation.	5 / 5
	Total	16 / 20 Passed

Description

75%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.

A specific, well-scoped description with strong trigger terms and clear distinctiveness, but it omits any explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' sentence listing the concrete trigger phrases (e.g. 'Use when building or integrating Stream Chat/Video/Feeds in an iOS app, migrating from Sendbird, or answering how-to questions about the Stream iOS SDKs').

Include a few natural synonyms or ecosystem terms users might say (e.g. 'StreamChat SDK', 'getstream.io', 'Swift package') to broaden trigger-term coverage toward a 5.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Build, integrate, migrate to, and answer how-to questions') across three named products plus the live-docs routing mechanism and a curated setup/migration/pitfalls bundle, giving comprehensive coverage rather than the minor gaps of a 4.	5 / 5
Completeness	The 'what' is explicit and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3 with 'when' only weakly implied.	3 / 5
Trigger Term Quality	Strong natural keywords ('how-to questions', 'Stream Chat, Video, and Feeds', 'Swift / SwiftUI / UIKit / iOS', 'migrate', 'Sendbird') that users would actually say, but lacks the synonym/extension breadth (e.g. no '.swift' / package-name variants) that would mark a 5.	4 / 5
Distinctiveness Conflict Risk	Narrows to Stream Chat/Video/Feeds in Swift/iOS specifically, a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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: 28 missing, 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: GetStream/agent-skills
Path: skills/stream-swift/SKILL.md
Commit: 1c67ee3

Reviewed: 3 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.