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

75%

Does it follow best practices?

Impact

—

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 its domain (reactive real-time backends on the iii engine), lists concrete capabilities, and provides explicit trigger conditions via a well-structured 'Use when...' clause. The description uses proper third-person voice and includes a rich set of natural trigger terms that developers would use. The specificity of the platform ('iii engine') and the architectural patterns make it highly distinguishable from other skills.

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' with an explicit 'Use when...' clause covering three distinct trigger scenarios: event-driven apps with automatic side effects, clients needing live updates, and real-time database needs.	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. The niche is clear and unlikely to conflict with general backend or database skills.	3 / 3
	Total	12 / 12 Passed

Implementation

50%

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 conceptual framework for building reactive backends with clear architecture visualization and useful primitive mappings. Its main weaknesses are the lack of inline executable code examples (relying entirely on an external reference file) and missing validation/error-handling guidance for a multi-step reactive system. The bottom sections contain generic boilerplate that could be trimmed.

Suggestions

Add at least one inline, executable code snippet showing a minimal reactive backend setup (e.g., registering a worker, setting state, and wiring a state trigger) rather than relying solely on the external reference file.

Add validation/error-handling guidance: what happens when a state trigger fails, how to verify stream connections, and how to debug reactive chains.

Consolidate the 'Pattern Boundaries', 'When to Use', and 'Boundaries' sections into a single concise section to reduce redundancy and save tokens.

Convert the 'Common Patterns' bullet list into a short but complete executable example that demonstrates the reactive flow end-to-end.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some redundant sections. The 'When to Use' and 'Boundaries' sections at the bottom repeat generic boilerplate that doesn't add value. Phrases like 'Use the concepts below when they fit the task' and 'Use the adaptations below when they apply to the task' are unnecessary hedging. The architecture diagram and primitives table are well-structured and earn their tokens.	2 / 3
Actionability	The skill provides concrete API patterns and a useful architecture diagram, but lacks executable code examples inline. It relies on a reference file (reactive-backend.js) for the actual implementation, and the 'Common Patterns' section shows API signatures but not complete, copy-paste-ready code blocks. The patterns are specific enough to guide implementation but fall short of fully executable guidance.	2 / 3
Workflow Clarity	The architecture diagram provides a clear data flow sequence (HTTP → state → triggers → stream), which is helpful. However, there are no explicit validation checkpoints, no error handling guidance, and no feedback loops for when things go wrong. For a reactive system with state triggers and streams, missing validation steps (e.g., verifying stream connections, confirming state writes) is a notable gap.	2 / 3
Progressive Disclosure	The skill references a detailed implementation file (../references/reactive-backend.js) which is good progressive disclosure, but no bundle files were provided to verify this reference exists. The main content is reasonably structured with clear sections, but the 'Common Patterns' section contains detail that might be better served inline as a short executable example rather than a bullet list of API signatures. The boundary/disambiguation sections ('Pattern Boundaries', 'When to Use', 'Boundaries') could be consolidated.	2 / 3
	Total	8 / 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: d51a06d

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.