iii-reactive-backend

Builds reactive real-time backends where functions react automatically to state changes and stream events. Use when requirements say "after create/update do this", "keep views/metrics/cache in sync", "notify clients when data changes", "push live updates", or "avoid polling"; combine state triggers, stream updates, pub/sub, and queued work instead of imperative follow-up calls.

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 defines a specific architectural pattern (reactive real-time backends) with concrete actions and excellent trigger coverage. The 'Use when...' clause provides multiple natural-language phrases that users would realistically use when they need this skill. The description is concise yet comprehensive, and the domain is distinct enough to avoid conflicts with general backend development skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: state triggers, stream updates, pub/sub, queued work, keeping views/metrics/cache in sync, notifying clients, and pushing live updates. These are concrete architectural patterns and actions, not vague language.	3 / 3
Completeness	Clearly answers both what ('Builds reactive real-time backends where functions react automatically to state changes and stream events') and when (explicit 'Use when...' clause with multiple specific trigger scenarios). The when clause is detailed and actionable.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger phrases users would say: 'after create/update do this', 'keep views/metrics/cache in sync', 'notify clients when data changes', 'push live updates', 'avoid polling'. These are realistic phrases from requirements discussions and user requests.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche around reactive/event-driven real-time backends with specific patterns (state triggers, pub/sub, streams). The trigger terms are distinct enough ('avoid polling', 'push live updates', 'react automatically to state changes') to avoid conflicting with general backend or API 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.

The skill provides a solid conceptual framework for reactive backends with good use of an architecture diagram and primitives table, but falls short on actionability by lacking inline executable code examples and relying on an unverifiable external reference file. The workflow could be strengthened with explicit step-by-step build instructions and validation checkpoints, and some sections contain redundant guidance that could be tightened.

Suggestions

Add at least one complete, executable inline code example showing a minimal reactive backend (e.g., a single state trigger that pushes to a stream) rather than relying solely on the external reference file.

Add a step-by-step 'Quick Start' workflow with numbered steps and validation checkpoints (e.g., verify worker registration, test state trigger fires, confirm stream receives updates).

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

Include the bundle reference file (reactive-backend.js) or ensure it exists so the progressive disclosure actually works as intended.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some redundancy — the 'When to Use' and 'Boundaries' sections repeat information that could be consolidated, and phrases like 'Use the concepts below when they fit the task' and 'Use the adaptations below when they apply to the task' are unnecessary filler. The architecture diagram and primitives table are well-structured, though.	2 / 3
Actionability	The skill provides common patterns and API signatures but lacks executable, copy-paste-ready code examples inline. It relies heavily on a reference file (reactive-backend.js) for the actual implementation. The patterns section lists function signatures but doesn't show complete working snippets that Claude could directly use.	2 / 3
Workflow Clarity	The architecture diagram provides a clear conceptual flow of how state changes propagate through triggers and streams. However, there are no explicit step-by-step instructions for building a reactive backend, no validation checkpoints, and no error recovery guidance for when triggers fail or streams disconnect.	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 content itself is reasonably organized with clear sections, but the inline content could benefit from a clearer quick-start section separated from the detailed patterns.	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: a7ebbbb

Reviewed: 5 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.