Tessl • The management layer for AI agent skills

SkillPublic

stream-flutter

Build, integrate, review, migrate to, and answer how-to questions for Stream Chat, Video, and Feeds in Flutter / Dart apps. Supports stream_chat_flutter (pre-built Chat UI), stream_chat_flutter_core (custom Chat UI), stream_video_flutter (calls, ringing, audio rooms, livestreaming), and stream_feeds (Activity Feeds v3, no pre-built UI). Routes each request to the exact official Flutter docs page, fetches it live, and applies it - with a curated setup flow, a push / ringing runbook, design-matching and custom-UI runbooks, a Sendbird -> Stream Chat migration runbook, a read-only integration review before going live (including livestream launches), and Flutter-specific pitfalls.

1.07x

Quality

88%

Does it follow best practices?

Impact

88%

1.07x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

An exemplary orchestrator skill: concrete and executable mechanisms (the .md docs convention, index routing, citation discipline), a clearly sequenced workflow with real validation checkpoints, and clean one-level-deep progressive disclosure to ~10 purpose-labeled runbooks. The only trimmable fat is a few paragraphs that duplicate design-matching.md detail inline. Note: the referenced runbook files (RULES.md, docs-map.md, setup.md, etc.) were not present in the provided review bundle, so progressive disclosure was scored on the reference structure as written.

Dimension	Reasoning	Score
Conciseness	The body is dense and directive with no padding on concepts Claude already knows, but the styling-depth paragraph ("A reference design is a checklist of regions...") and the workplace/Slack archetype paragraph restate detail that belongs in design-matching.md and could be trimmed.	4 / 5
Actionability	Fully executable guidance throughout: the exact .md URL transformation rule with a worked example, live index URLs in a table, "Fetch at most 3 pages per request", the citation format "Source: [Title](https://getstream.io/...)", and an explicit escalation path to SDK source at the pubspec.lock-pinned version.	5 / 5
Workflow Clarity	Clear sequenced workflow (Step 0 classify -> setup -> docs lookup -> apply -> cite) with explicit validation checkpoints: URL-grounding rules, "Never answer SDK specifics from training data", one-question ambiguity resolution, and a run/seed/compare/iterate verification loop for design matching.	5 / 5
Progressive Disclosure	A true overview file: it routes each mode to one-level-deep runbooks, every reference is a well-signaled markdown link with its purpose, and a "What this skill carries" section enumerates the whole bundle; no SDK dumps are inlined.	5 / 5
	Total	19 / 20 Passed

Description

82%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 highly specific, well-scoped description that names concrete actions, packages, and features with excellent natural trigger terms and minimal conflict risk. Its only real weakness is the missing explicit "Use when..." trigger clause, which leaves the "when to use" half implicit and caps completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when working on a Flutter/Dart app that integrates Stream Chat, Video, or Feeds, or when the user mentions stream_chat_flutter, stream_video_flutter, stream_feeds, or migrating from Sendbird."

Move the when-to-use guidance near the front of the description so trigger conditions are not buried after the long capability enumeration.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Build, integrate, review, migrate to, and answer how-to questions") scoped to named packages (stream_chat_flutter, stream_chat_flutter_core, stream_video_flutter, stream_feeds) and concrete features (calls, ringing, audio rooms, livestreaming, Sendbird migration, integration review), giving comprehensive coverage of the skill's surface.	5 / 5
Completeness	The "what" is explicit and detailed (orchestration actions, per-package support, runbooks), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural user phrases are comprehensively covered: "Stream Chat", "Flutter / Dart", "calls", "ringing", "push", "livestreaming", "Sendbird", "Activity Feeds", plus exact package names that act as precise triggers; only trivial synonyms (e.g. "in-app chat", "video calling") are absent.	5 / 5
Distinctiveness Conflict Risk	Clear niche (Stream's Flutter SDKs) with distinct triggers — exact package names, "Sendbird -> Stream Chat migration", "Activity Feeds v3" — making confusion with generic Flutter or non-Stream skills very unlikely; only negligible overlap with sibling Stream-platform skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 33 missing, 2 suspicious	Warning

	Total	14 / 16 Passed

Repository: GetStream/agent-skills
Path: skills/stream-flutter/SKILL.md
Revision: 85f8ed2

Reviewed: 1 hour ago

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.

stream-flutter

Table of Contents

Is this your skill?