iii-reactive-backend

Builds reactive real-time backends on the iii engine. Use when building event-driven apps where state changes automatically trigger side effects, clients receive live updates via streams or websockets, or you need a real-time database layer with pub/sub and CRUD endpoints.

Quality

78%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/iii-reactive-backend/SKILL.md

Quality

Discovery

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.

This is a strong skill description that clearly identifies the specific platform (iii engine), lists concrete capabilities (reactive backends, event-driven side effects, live updates, pub/sub, CRUD), and provides explicit trigger guidance with a 'Use when...' clause. The natural trigger terms cover the domain well and the specificity to the iii engine makes it highly distinctive.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and architectural patterns: event-driven apps, state changes triggering side effects, live updates via streams/websockets, real-time database layer with pub/sub and CRUD endpoints.	3 / 3
Completeness	Clearly answers both what ('Builds reactive real-time backends on the iii engine') and when ('Use when building event-driven apps where state changes automatically trigger side effects, clients receive live updates via streams or websockets, or you need a real-time database layer with pub/sub and CRUD endpoints').	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'real-time', 'event-driven', 'websockets', 'streams', 'pub/sub', 'CRUD endpoints', 'live updates', 'reactive', 'side effects', 'real-time database'. Good coverage of terms a developer would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific 'iii engine' platform reference and the combination of reactive/real-time/event-driven backend patterns. Unlikely to conflict with generic backend or database skills.	3 / 3
	Total	12 / 12 Passed

Implementation

57%

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

This skill provides a solid architectural overview of the reactive backend pattern with good organization and progressive disclosure. However, it leans too heavily on the external reference file for actual executable code, leaving the skill itself more descriptive than actionable. The boilerplate boundary/usage sections at the bottom add little value and could be trimmed.

Suggestions

Add at least one minimal but complete inline code example showing worker registration with a state trigger and stream push — don't rely solely on the external reference file for all executable guidance.

Include a brief step-by-step workflow for bootstrapping a reactive backend (e.g., 1. Register worker, 2. Register state functions, 3. Wire triggers, 4. Verify stream output) with a validation checkpoint.

Remove or consolidate the 'When to Use' and 'Boundaries' boilerplate sections — they repeat generic guidance that doesn't add skill-specific value.

Dimension	Reasoning	Score
Conciseness	Generally efficient but has some redundancy — the 'When to Use' and 'Boundaries' sections at the bottom are boilerplate that add little value, and the 'Pattern Boundaries' section partially overlaps. The architecture diagram and table are well-structured and earn their tokens.	2 / 3
Actionability	Provides useful API patterns and primitive names but lacks executable code examples inline — it defers to an external reference file. The 'Common Patterns' section shows API calls but as bullet-point fragments rather than copy-paste-ready code blocks. The architecture diagram helps but isn't a substitute for runnable examples.	2 / 3
Workflow Clarity	The architecture diagram provides a clear data flow sequence, and the primitives table helps understand the building blocks. However, there are no explicit validation checkpoints or error recovery steps for setting up a reactive backend, and the actual step-by-step process of building one is delegated entirely to the reference file.	2 / 3
Progressive Disclosure	Good structure with a clear overview, well-organized sections, and a single-level reference to the full implementation file. The skill appropriately keeps the overview concise and points to the reference implementation for the complete working example.	3 / 3
	Total	9 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: iii-hq/iii
Commit: 8921efa

Reviewed: 1 day 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.