effector-storage

Choose and implement effector-storage persistence patterns for Effector apps. Use when tasks involve persist/createPersist usage, selecting adapters (local/session/query/broadcast/storage/asyncStorage/memory/nil/log), configuring clock/pickup/context/keyPrefix, validating data with contracts, handling done/fail/finally flows, SSR-safe adapter fallback with either, or debugging sync and serialization issues.

Quality

75%

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 ./skills/effector-storage/SKILL.md

Quality

Content

50%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 skill is well-structured as a meta-workflow for answering effector-storage questions, with good guardrails and sensible defaults. Its main weakness is the complete absence of concrete code examples or executable snippets, which significantly limits actionability. The referenced bundle files are missing, undermining the progressive disclosure strategy that the skill relies on.

Suggestions

Add at least 2-3 minimal executable code snippets showing common `persist`/`createPersist` patterns with explicit key strategies and adapter selection.

Include a concrete example of contract validation with done/fail routing to make the 'contracts-errors' classification actionable.

Provide the referenced bundle files (core-patterns.md, adapter-matrix.md, etc.) or inline the most critical reference content if the bundle cannot be supplied.

Add a verification/validation step in the workflow, such as a checklist or test pattern to confirm the persistence integration works correctly before finalizing.

Dimension	Reasoning	Score
Conciseness	The content is efficient and avoids explaining what Effector or storage adapters are. Minor verbosity in the workflow classification section and 'Build answer contract' could be tightened slightly, but overall it respects Claude's intelligence well.	4 / 5
Actionability	The skill provides structured guidance on decision-making and workflow but lacks any concrete code examples, executable snippets, or specific API usage patterns. It tells Claude what to do at a high level (e.g., 'provide a minimal working snippet') but never demonstrates one itself.	2 / 5
Workflow Clarity	The three-step workflow (classify, load references, build answer) is clearly sequenced and logical. However, there are no explicit validation checkpoints or feedback loops for error recovery, and the steps are meta-instructions about how to answer rather than steps for performing the actual task.	3 / 5
Progressive Disclosure	The skill references five specific files in `references/` with clear loading order and conditions, which is good structure. However, no bundle files are provided, so these references are unverifiable and potentially broken. The skill itself is appropriately concise as an overview, but the missing bundle undermines the progressive disclosure pattern.	3 / 5
	Total	12 / 20 Passed

Description

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

This is an excellent skill description that comprehensively covers the effector-storage library's capabilities with highly specific trigger terms. It clearly states both what the skill does and when to use it, with an explicit 'Use when' clause containing concrete scenarios. The description is highly distinctive due to its niche domain and library-specific terminology.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions and concepts: implementing persistence patterns, using persist/createPersist, selecting from a comprehensive list of adapters, configuring specific options (clock/pickup/context/keyPrefix), validating with contracts, handling done/fail/finally flows, SSR-safe fallback with 'either', and debugging sync/serialization issues.	5 / 5
Completeness	Clearly answers both 'what' (choose and implement effector-storage persistence patterns) and 'when' (explicit 'Use when' clause listing specific trigger scenarios like persist/createPersist usage, adapter selection, configuration, validation, SSR fallback, and debugging).	5 / 5
Trigger Term Quality	Includes highly specific and natural trigger terms a developer would use: 'persist', 'createPersist', adapter names (localStorage, sessionStorage, asyncStorage, etc.), 'SSR', 'contracts', 'keyPrefix', 'effector-storage', 'serialization'. These are the exact terms a user working with this library would mention.	5 / 5
Distinctiveness Conflict Risk	Extremely niche and distinct — targets the specific 'effector-storage' library within the Effector ecosystem. The combination of library-specific API names (persist, createPersist, adapter types, 'either') makes it virtually impossible to conflict with other skills.	5 / 5
	Total	20 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: aiko-atami/effectorjs-skills
Path: skills/effector-storage/SKILL.md
Commit: 9a7e508

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