Tauri app store — key-value persistence with Store vs LazyStore
Guidance for the Tauri v2 store plugin — lightweight key-value persistence, Store vs LazyStore decision by load timing, storage schema, capability scoping, and persistence lifecycle
- What
- Guidance for the Tauri v2 store plugin — lightweight key-value persistence, Store vs LazyStore decision by load timing, storage schema, capability scoping, and persistence lifecycle
- Cost
- Free
- Needs
- a Tauri v2 project needing lightweight persistent storage — the skill is a workflow guide the agent follows, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @full-stack-skills' tauri-app-store skill: guidance for the Tauri v2 store plugin — lightweight persistent storage for app settings, the Store vs LazyStore decision based on load timing, storage file location and schema definition, capability/scope restriction, and persistence lifecycle and error handling, with links to the official v2.tauri.app store docs. It produces store-selection guidance and a settings persistence plan, with a declared boundary (store plugin usage only — Store vs LazyStore differences). Honest caveats: guidance sections are bilingual English/Chinese and distinct per skill; the gotchas/workflow tail is a shared template across the tauri-app-* series. (Unrelated to Apple's App Store or App Store Connect tooling also present on the site — this is Tauri's local key-value store plugin.) Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Tauri app store is a free Muse skill guiding the Tauri v2 store plugin: lightweight key-value storage for app settings, the Store versus LazyStore choice by load timing, storage location and schema, capability and scope restriction, and persistence lifecycle and error handling. It produces store-selection guidance and a settings persistence plan, with links to the official Tauri docs.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 77b57c4Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Tauri v2 project needing lightweight persistent storage — the skill is a workflow guide the agent follows, not software Install "Tauri app store — key-value persistence with Store vs LazyStore" for me. It gives my agent @full-stack-skills' store guidance: decide between Store and LazyStore based on load timing, define the storage file location and schema, restrict access via capabilities and scope, and validate the persistence lifecycle and error handling — producing store-selection guidance and a settings persistence plan, with links to the official v2.tauri.app store docs. Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/full-stack-skills/tauri-skills/77b57c4913873a0f8cab7db45116038dc18a27f0/skills/tauri-app-store/SKILL.md Pinned version: install the code at commit 77b57c4913873a0f8cab7db45116038dc18a27f0 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "tauri-app-store". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it's a methodology; ask the agent about Store vs LazyStore or settings persistence for my Tauri project). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 77b57c4 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.