tauri-app-plugin-permissions
Author and audit Tauri v2 plugin permissions, generate capability files, and handle cross-platform permission differences. Use when writing plugin permission schemas, generating capabilities/default.json, or auditing permissions across Windows/macOS/Linux/mobile.
Best use case
tauri-app-plugin-permissions is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Author and audit Tauri v2 plugin permissions, generate capability files, and handle cross-platform permission differences. Use when writing plugin permission schemas, generating capabilities/default.json, or auditing permissions across Windows/macOS/Linux/mobile.
Author and audit Tauri v2 plugin permissions, generate capability files, and handle cross-platform permission differences. Use when writing plugin permission schemas, generating capabilities/default.json, or auditing permissions across Windows/macOS/Linux/mobile.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "tauri-app-plugin-permissions" skill to help with this workflow task. Context: Author and audit Tauri v2 plugin permissions, generate capability files, and handle cross-platform permission differences. Use when writing plugin permission schemas, generating capabilities/default.json, or auditing permissions across Windows/macOS/Linux/mobile.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tauri-app-plugin-permissions/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tauri-app-plugin-permissions Compares
| Feature / Agent | tauri-app-plugin-permissions | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Author and audit Tauri v2 plugin permissions, generate capability files, and handle cross-platform permission differences. Use when writing plugin permission schemas, generating capabilities/default.json, or auditing permissions across Windows/macOS/Linux/mobile.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## When to use this skill
**ALWAYS use this skill when the user mentions:**
- Writing or auditing plugin permissions
- Generating capability templates or permissions schemas
- Cross-platform permission differences
**Trigger phrases include:**
- "plugin permissions", "capability template", "permissions schema", "capabilities json"
## How to use this skill
1. **Map features to plugin permissions**:
```
Feature: "Read user files"
Plugin: fs
Permission: fs:allow-read-text-file
Scope: { "path": "$DOCUMENT/**" }
```
2. **Generate capabilities/default.json** with minimal scope:
```json
{
"identifier": "default",
"description": "Main app capabilities",
"windows": ["main"],
"permissions": [
"fs:allow-read-text-file",
"dialog:allow-open",
{ "identifier": "http:default", "allow": [{ "url": "https://api.example.com/**" }] }
]
}
```
3. **Separate plugin-defined permissions** (what a plugin exposes) from app-enabled capabilities (what your app allows)
4. **Handle platform differences**: Some permissions behave differently on Windows vs macOS (e.g., shell execution, file paths)
5. **Audit permissions** by reviewing each capability entry against the minimum required for each feature
6. **Run `cargo tauri build`** to validate that all required permissions are declared
## Outputs
- Feature-to-permission mapping table
- Minimal capabilities/default.json file
- Cross-platform permission audit checklist
## References
- https://v2.tauri.app/learn/using-plugin-permissions/
- https://v2.tauri.app/learn/security/writing-plugin-permissions/
## Keywords
tauri permissions, plugin permissions, capabilities, scope, capability templateRelated Skills
uniapp-plugin
Browses, installs, configures, and manages plugins from the uni-app plugin market (ext.dcloud.net.cn) including component plugins, API plugins, and template plugins with dependency handling. Use when the user needs to find and install uni-app plugins, configure plugin settings, manage plugin dependencies, or integrate third-party components.
uniapp-native-plugin
Develops native Android and iOS plugins for uni-app including module creation, JavaScript-to-native communication, and plugin packaging for distribution. Use when the user needs to build custom native modules, extend uni-app with native capabilities (camera, Bluetooth, sensors), or create publishable native plugins.
tauri
Primary index and router for all Tauri v2 framework skills covering Rust backend, frontend integration, and the full plugin ecosystem. Use when any Tauri-related request is made to route to the correct specialized sub-skill with local examples and templates.
tauri-window
Create and configure Tauri v2 windows including multi-window patterns, custom titlebars, and frameless window UI. Use when creating new windows, managing window lifecycle events, implementing custom titlebar drag regions, or building multi-window architectures.
tauri-setup
Install Tauri v2 prerequisites and configure the development environment across macOS, Windows, Linux, Android, and iOS. Use when setting up Rust toolchain, Node.js, platform build tools, or mobile development prerequisites (Xcode, Android Studio).
tauri-security
Configure Tauri v2 capabilities, scoped access rules, and ACL-based permission control for production apps. Use when generating capabilities/default.json, defining scoped access per plugin, or auditing permissions for minimum-privilege compliance.
tauri-scaffold
Scaffold a Tauri v2 project with create-tauri-app, configure project structure, and set up static export for frontend frameworks. Use when creating a new project, understanding the Tauri project structure, or configuring SSG/static export for Next.js or SvelteKit.
tauri-mobile
Set up Tauri v2 for Android and iOS development including build configuration, bundle identifiers, and mobile debugging. Use when adding mobile targets to a Tauri app, configuring Android/iOS bundle IDs, or debugging on mobile devices and emulators.
tauri-ipc
Implement frontend-to-Rust IPC using invoke calls, Tauri commands, and type-safe bindings in Tauri v2. Use when defining Rust commands callable from the frontend, setting up typed IPC contracts, or implementing bidirectional event-based communication.
tauri-framework-upgrade
Migrate Tauri apps from v1 to v2 or from v2 beta to v2 stable, handling breaking changes in config, plugins, and permissions. Use when upgrading Tauri versions, resolving migration errors, or updating config/capability formats for v2.
tauri-framework-security
Harden a Tauri v2 app with baseline security controls including CSP, HTTP headers, runtime authority, and capability matrices. Use when performing security audits, configuring CSP/headers per window, or building a minimum-privilege capability matrix for production.
tauri-config
Configure tauri.conf.json for Tauri v2 apps including app metadata, build settings, plugins, CSP, and platform-specific sections. Use when editing tauri.conf.json, migrating config from v1 to v2, or setting up CSP and platform-specific configuration.