CtrlK
BlogDocsLog inGet started
Tessl Logo

stream-docs

Search live Stream SDK documentation for Chat, Video, Feeds, and Moderation. Look up how a Stream React/iOS/Android/Node/Flutter/Unity/Angular hook, component, or method works. Answer how-to questions about any Stream SDK across every framework and version. Triggers on 'docs', 'documentation', explicit SDK tokens (Chat React, Video iOS, Feeds Node, Moderation), and 'how do I ... in <framework>' phrasing.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 lean compatibility skill: it captures genuinely non-obvious operational details (stderr redirect behavior, citation requirements, install-gated fallback) in a compact body with an explicit primary/fallback decision point. The only improvements are a worked example of a typical lookup and a concrete location for the referenced 'stream skill'.

DimensionReasoningScore

Conciseness

About 20 lean lines with zero padding; every sentence conveys non-obvious operational knowledge (the 2>&1/stdout pitfall, the citation URL pattern, the install-gated fallback). Matches the 'every token earns its place' anchor.

5 / 5

Actionability

Concrete commands are given (`getstream docs`, `getstream docs -h`, `$(getstream docs <id>)`) plus a concrete fallback URL, but there is no worked example of the common end-to-end case (locating a page, reading it, answering), and 'Refer to stream skill for CLI guidance' points to no path. Mostly executable with minor gaps — anchor 4.

4 / 5

Workflow Clarity

A simple, single-purpose skill whose single action (use `getstream docs`, cite each page) is unambiguous, with an explicitly conditioned fallback path ('Only when the CLI cannot be installed, fall back to fetching ...'). The simple-skill exception applies; no destructive or batch operations require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is well under 50 lines and self-contained with no bundle files, so no external references are needed; however, the pointer to the 'stream skill' gives no path or location, a minor navigation gap versus the cleanly organized anchor 5.

4 / 5

Total

18

/

20

Passed

Description

83%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 strong description: it clearly states concrete capabilities across all Stream products and SDKs and provides an explicit, well-formed trigger clause. The main gaps are a slightly generic 'answer how-to questions' phrasing and a few missing natural synonyms ('getstream', 'stream.io') in the trigger list.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Search live Stream SDK documentation', 'Look up how a ... hook, component, or method works', 'Answer how-to questions') with full product and framework enumeration; 'Answer how-to questions about any Stream SDK' is somewhat generic, so it falls just below the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both what ('Search live Stream SDK documentation ... Look up how a ... hook, component, or method works ... Answer how-to questions') and when ('Triggers on 'docs', 'documentation', explicit SDK tokens ..., and 'how do I ... in <framework>' phrasing') with concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Good coverage of natural phrases ('docs', 'documentation', 'how do I ... in <framework>') plus specific SDK tokens (Chat React, Video iOS, Feeds Node, Moderation), but misses common synonyms users would say such as 'getstream', 'stream.io', or 'Stream API'.

4 / 5

Distinctiveness Conflict Risk

The Stream product names and SDK tokens carve out a clear niche, but the bare 'docs'/'documentation' triggers are broad and could overlap with other documentation-lookup skills; minor overlap risk, matching anchor 4.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
GetStream/agent-skills
Reviewed

Table of Contents

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.