multiAI Summary Pending
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.
223 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/tauri-app-plugin-permissions/SKILL.md --create-dirs "https://raw.githubusercontent.com/partme-ai/full-stack-skills/main/skills/tauri-skills/tauri-app-plugin-permissions/SKILL.md"
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 | multi | 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.
Which AI agents support this skill?
This skill is compatible with multi.
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 template