Tauri app file system — scoped access and safe file operations
Guidance for the Tauri v2 file-system plugin — minimal directory/file-pattern scopes, import/export file workflows, access-boundary validation, and safe read/write patterns
- What
- Guidance for the Tauri v2 file-system plugin — minimal directory/file-pattern scopes, import/export file workflows, access-boundary validation, and safe read/write patterns
- Cost
- Free
- Needs
- a Tauri v2 project needing local file access — 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-file-system skill: guidance for the Tauri v2 file-system plugin — defining the minimal directories and file patterns to access, configuring plugin scope and capabilities, implementing file selection, read, and write flows, and validating access boundaries and error handling, with links to the official v2.tauri.app file-system docs. It produces a file-access scope plan and an import/export flow checklist, with a declared boundary (file-system plugin usage only — scope restrictions for safe access). 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. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Tauri v2 project needing local file access — the skill is a workflow guide the agent follows, not software Install "Tauri app file system — scoped access and safe file operations" for me. It gives my agent @full-stack-skills' file-system guidance: define the minimal directories and file patterns to access, configure file-system plugin scope and capabilities, implement file selection, read, and write flows, and validate access boundaries and error handling — producing a file-access scope plan and an import/export flow checklist, with links to the official v2.tauri.app file-system docs. Apache-2.0 licensed. Repository: https://github.com/full-stack-skills/tauri-skills/blob/main/skills/tauri-app-file-system/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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-file-system". 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 file scope or import/export flows 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.