iii-state-reactions
Registers state-type triggers that automatically fire functions when key-value state is created, updated, or deleted within a scope. Use when building reactive side effects, change watchers, audit logs, cache invalidation, notification dispatchers, or any observer pattern where data changes should trigger downstream processing.
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/iii-state-reactions/SKILL.mdQuality
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 articulates what the skill does (register state-type triggers for key-value state changes) and when to use it (with an explicit 'Use when' clause covering multiple concrete scenarios). The description includes rich, natural trigger terms spanning multiple use cases like observer patterns, cache invalidation, and audit logs, making it highly discoverable and distinct from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'registers state-type triggers', 'automatically fire functions when key-value state is created, updated, or deleted within a scope'. These are concrete, well-defined operations. | 3 / 3 |
Completeness | Clearly answers both 'what' (registers state-type triggers that fire functions on key-value state changes) and 'when' (explicit 'Use when' clause listing reactive side effects, change watchers, audit logs, cache invalidation, notification dispatchers, observer pattern scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'reactive side effects', 'change watchers', 'audit logs', 'cache invalidation', 'notification dispatchers', 'observer pattern', 'state triggers', 'key-value state'. Good coverage of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: state-type triggers on key-value state changes within a scope. The combination of 'state triggers', 'key-value state', and 'created/updated/deleted' events makes this clearly distinguishable from general event handling or other skill types. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-organized as a navigational overview with good progressive disclosure and reasonable conciseness, but critically lacks any inline executable code examples — all actionable content is deferred to external reference files. The workflow is described at a high level but lacks validation steps or error recovery guidance that would be important for correctly wiring up reactive state triggers.
Suggestions
Add at least one minimal, executable inline code example (e.g., a complete registerTrigger + registerFunction snippet) so the skill is actionable without navigating to external files.
Add a validation/verification step — e.g., how to confirm a trigger is registered and firing correctly, or how to debug when a reaction doesn't fire as expected.
Remove or consolidate the generic 'When to Use' and 'Boundaries' boilerplate sections, which add little beyond what 'Pattern Boundaries' already covers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy — the 'When to Use' and 'Boundaries' sections at the bottom are generic boilerplate that adds little value. The 'Common Patterns' section partially duplicates information from the primitives table. However, it generally avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | There is no executable code in the skill body itself — all concrete implementation is deferred to external reference files. The 'Common Patterns' section lists API calls but without executable examples or copy-paste ready snippets. The reader cannot act on this skill without navigating to separate files. | 1 / 3 |
Workflow Clarity | The Architecture section provides a clear event flow sequence, and the Common Patterns section lists relevant steps. However, there are no validation checkpoints, no error handling guidance, and no feedback loops for verifying that triggers are correctly registered and firing. | 2 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear one-level-deep references to implementation files in JS, Python, and Rust, plus a config reference. Navigation is clearly signaled with relative links, and the content is appropriately split between overview and detailed references. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
100%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
Table of Contents
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.