Content
88%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A strong orchestrator skill: concrete, well-gated, and loaded with knowledge the docs do not carry, with excellent executable detail and clear navigation to its reference files. The main costs are repetition of key facts and inlining of docs-tree detail that duplicates what docs-map.md is for, which inflate token cost without adding guidance.
Suggestions
State the 'no reusable UI, you write it yourself' fact once (the table row or the paragraph, not both plus the Step 1 bullet) and let the single statement plus the ui.md link carry it.
Move the Chat-tree page-level detail (fence-label table, 301-redirect list, sample-project broken link) into docs-map.md, keeping only the one-sentence rule 'take label="Unity" blocks only; label="C#" is the server SDK' in SKILL.md.
Trim asides that justify rather than instruct (e.g. quoting the '//StreamTodo: expose CallRinging event?' source comment) to a bare statement of the gap, keeping the rule and the workaround.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with curated, non-obvious knowledge (version floors, the fence-label trap, redirect quirks, the source ladder) and assumes Claude's competence throughout. It slips below the top anchor on repetition and wordiness: 'Neither SDK ships reusable UI' is stated three times (table row, the paragraph after, and the Step 1 UI bullet), and passages like the ringing-event aside ('the source literally reads `//StreamTodo: expose CallRinging event?`') could be trimmed without losing the instruction. | 4 / 5 |
Actionability | Fully executable guidance throughout: a copy-paste read-only probe script, an exact URL transformation rule ('take the page URL, drop the trailing /, add .md') with worked examples, exact on-disk source paths per rung, concrete per-situation action tables, and a literal citation format ('Source: [Title](https://getstream.io/...)'). These cover the common cases directly. | 5 / 5 |
Workflow Clarity | A clear, gated sequence - Step 0's three gates (product, version/target, feature support) act as explicit validation checkpoints before any code, and each gate has a decision table spelling out the hard-stop outcomes. Feedback loops are present at every fallback point: 'If the feature is not in the map, fetch the live index', the rung ladder's 'Stop at the first rung that answers the question', and the URL-grounding rule preventing invented paths. | 5 / 5 |
Progressive Disclosure | Good structure: a 'What this skill carries' table signals five one-level-deep references (RULES.md, setup.md, ui.md, platforms.md, docs-map.md), each with a description of what it holds, and links are used consistently at the point of need. It falls short of the top anchor because the ~190-line body inlines substantial detail that the reference files exist to carry - the fence-label table, the 301-redirect caveats, and the per-page code-kind commentary overlap with docs-map.md's stated purpose, and the Gate 3 feature-gap lists could live in a reference. | 4 / 5 |
Total | 18 / 20 Passed |