stream-flutter

Build and integrate Stream Chat, Video, and Feeds in Flutter apps. Use for Flutter/Dart project work with Stream package setup, auth wiring, and widget blueprints. Supports stream_chat_flutter (pre-built Chat UI), stream_chat_flutter_core (custom Chat UI), stream_video_flutter (Video calling and livestreaming), and stream_feed / stream_feed_flutter_core (Activity Feeds, no pre-built UI).

1.81x

Quality

—

Does it follow best practices?

Impact

98%

1.81x

Average score across 2 eval scenarios

Securityby

Risky

Do not use without reviewing

Quality

Content

77%

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

A well-organized router/execution-flow skill with strong actionability and clear workflow sequencing including validation feedback loops. Its weaknesses are content redundancy that bloats token usage, and three core referenced files (RULES.md, builder.md, sdk.md) that are absent from the bundle despite being load-bearing.

Suggestions

Add the missing RULES.md, builder.md, and sdk.md to the bundle, or remove/redirect their references, since every track routes through them and their absence breaks core navigation.

De-duplicate the references file listing (it appears in both 'Reference layout' and 'Track C - Reference lookup') and consolidate the guest-viewer/permission grant guidance to reduce token bloat.

Tighten repeated prose such as the channel-seeding member instructions (stated in both C3 and its follow-up paragraph) to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is dense and procedural without explaining concepts Claude already knows, but it is lengthy (~340 lines) with notable redundancy: the references file list appears twice (Reference layout and Track C), and grant/permission guidance is restated across the guest-viewer note and Permissions awareness sections.	2 / 3
Actionability	Provides fully executable, copy-paste-ready bash commands with complete JSON request bodies (UpdateUsers, GetOrCreateChannel, UpdateChannel), a concrete project-detection probe script, and explicit phase tables, matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Sequences a clear multi-step flow (classify -> credentials -> probe -> track) with explicit validation checkpoints and feedback loops: 401/CLI-failure fallbacks, the v10 version gate ('Only proceed... once the project resolves a v10 dependency'), and A4/B4 verify phases that re-state permission prerequisites.	3 / 3
Progressive Disclosure	Reference layout is well-signaled and one-level-deep with a clear flat naming scheme, and all references/*.md files exist; however the load-bearing core links RULES.md, builder.md, and sdk.md (routed to by every track) are missing from the bundle, breaking the central navigation.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 strong, third-person description that states concrete capabilities, names the relevant packages, and provides an explicit 'Use for' trigger clause covering both what and when. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Build and integrate Stream Chat, Video, and Feeds', 'package setup, auth wiring, and widget blueprints') and enumerates the specific packages with their capabilities, matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what it does ('Build and integrate...') and when to use it ('Use for Flutter/Dart project work with Stream package setup...'), with an explicit 'Use for' trigger clause.	3 / 3
Trigger Term Quality	Natural terms a user would say are well covered ('Flutter/Dart project work', 'Stream', 'Chat, Video, and Feeds', plus package names like 'stream_chat_flutter'); the 'Use for' clause grounds it in real phrasing.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (Stream SDK integration in Flutter) with package-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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: 18 missing	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.