iii-stream

Durable real-time streams with a CRUD function surface plus reactive triggers that fire on item changes and WebSocket subscriber lifecycle — reach for it to build live backends without polling.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./engine/src/workers/stream/skills/SKILL.md

Quality

Content

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

The content is lean, well-structured, and actionable, covering functions, triggers, adapters, and boundaries without padding. Small gains are available from adding a join/leave handler example and surfacing the event payload shape.

Suggestions

Add a minimal `stream:join`/`stream:leave` handler example showing the event shape and the `{ unauthorized: true }` return, so the authorization-gate pattern is copy-paste ready.

Include a short example of the `stream` change-event payload (or a clear inline sketch) instead of deferring entirely to `iii get function info`, which would raise actionability and progressive_disclosure.

Tighten the overlap between the intro paragraph and the Reactive triggers section so the mutation list and lifecycle description are stated once.

Dimension	Reasoning	Score
Conciseness	The body assumes platform knowledge and focuses on non-obvious semantics (fire-and-forget dispatch, empty-as-wildcard, adapter fan-out limits); a little intro/Reactive-triggers redundancy and a couple of explanatory clauses keep it just below 5.	4 / 5
Actionability	Provides an executable `iii.registerTrigger` TypeScript example, a concrete function list, and a CLI command for payload shape; the deferred payload lookup and absence of a join/leave handler example are minor gaps.	4 / 5
Workflow Clarity	The trigger-binding sequence (register handler, then register trigger) is clearly laid out with config semantics; no validation checkpoints are needed because the task is not destructive or batch-oriented, leaving it just below 5.	4 / 5
Progressive Disclosure	Well-organized single-file structure with clear sections and inline references (Browser SDK, CLI command) rather than nested file pointers; with no bundle files the split is appropriate, but a payload-shape reference file could push it to 5.	4 / 5
	Total	16 / 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 well-crafted description that states both capability and trigger context concisely. It is specific and distinct, with only minor room to add synonyms or enumerate actions more fully.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete mechanisms — 'CRUD function surface', 'reactive triggers that fire on item changes and WebSocket subscriber lifecycle' — without vague fluff; falls short of 5 only because granular action coverage is summarized rather than enumerated.	4 / 5
Completeness	Explicitly answers both what ('Durable real-time streams with a CRUD function surface plus reactive triggers') and when ('reach for it to build live backends without polling') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Natural phrases a user would say appear — 'real-time streams', 'live backends without polling' — alongside technical terms; good coverage but missing common synonyms that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The reactive-trigger-plus-subscriber-lifecycle niche is mostly distinct from generic state/streaming skills; minor overlap risk with a broader key/value or pub-sub skill keeps it just below 5.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: iii-hq/iii
Path: engine/src/workers/stream/skills/SKILL.md
Commit: 2c8976b

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.