AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Effector Storage

skill-aiko-atami-effectorjs-skills-effector-storage · by aiko-atami

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 serializat…

↗ Website ↗ Repository
— No reviews yet
0 installs
32 views
0.0% view→install

Install

$ agentstack add skill-aiko-atami-effectorjs-skills-effector-storage

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-aiko-atami-effectorjs-skills-effector-storage)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
○ 7mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Effector Storage? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Effector Storage Skill

Use this skill to design, implement, and debug effector-storage integrations with predictable runtime behavior.

Workflow

  1. Classify the request:
  • adapter-choice: pick the right adapter for environment and data behavior.
  • integration: wire persist/createPersist into existing model flow.
  • contracts-errors: validate storage payloads and route failures.
  • sync-debug: investigate cross-tab/query/broadcast synchronization issues.
  • ssr-fallback: make persistence safe across browser/server runtimes.
  1. Load references progressively:
  • Start with references/core-patterns.md.
  • Add references/adapter-matrix.md when adapter selection/configuration is needed.
  • Add references/tools-and-composition.md for async, either, farcached, or composition recipes.
  • Add references/contracts-and-errors.md for contracts and error channels.
  • End with references/pitfalls-and-checklist.md before finalizing.
  1. Build answer contract:
  • Start with a concrete adapter decision and why.
  • Provide a minimal working snippet with explicit key strategy.
  • List behavior caveats (init timing, sync limits, validation behavior).
  • Add verification steps/tests for the chosen flow.

Defaults

  • Target effector-storage v7.x behavior.
  • Prefer explicit key over implicit store names for portability.
  • Prefer declarative Effector wiring around persist (sample/clock/context units).
  • Keep payloads plain and serialization stable (deserialize(serialize(x))).

Guardrails

  • Do not omit both key and store name.
  • Do not use source === target for non-store units.
  • Do not assume pickup still performs automatic initial restore (it disables it).
  • Do not assume contract validation prevents writes; invalid values can be persisted and then reported via fail.
  • Do not treat broadcast as durable storage; it is sync-only messaging.

Practical Extras Boundary

For adapters from effector-storage-extras, reuse the same adapter contract and decision flow from this skill, but verify exact API/options in that repository before coding.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills