managing-tauri-plugin-permissions

What problem does it solve? Tauri applications deny all plugin commands by default, so developers must correctly wire capabilities, permission identifiers, and scopes or their app fails with permission errors or ships with overly broad access. ## Core Features & Use Cases - Capability Configuration: Create JSON capability files targeting specific windows and platforms (linux, windows, macos, android, ios) with least-privilege permission sets. - Scoped Permissions: Restrict filesystem and other plugin access using scope variables like $HOME, $APP, and $DOCUMENT instead of blanket allow rules. - Custom Plugin Permissions: Auto-generate allow/deny permissions from plugin commands and define tiered permission sets (default, read-write, full-access) in TOML. - Use Case: You are building a cross-platform Tauri app where the main window needs read access to ~/Documents but the settings window should only touch app data. This Skill walks you through writing separate capability files with scoped fs permissions for each window. ## Quick Start Ask the assistant to create a Tauri capability file that grants the main window scoped read access to the Documents folder and write access to the app data directory.