Tauri framework for building cross-platform desktop and mobile apps.
SkillScore73Maintained
Automatic
◆Coding pack
Last verified 8/21/2026
What it changes
Passed 16 of 22 test cases with the skill, and 12 of 22 without it.
Without skill55%
With skill73%
Checks it passed that the model alone missed
Includes ./src-tauri in the watch ignore array.
Sets ws_protocol to ws under the serve configuration.
Uses app.state::<AppData>() to access the managed state.
and 2 more in the full report
4 fixed12 passed either way6 still failing0 broke
Pass-rate lift
+18 pp
Tokens
+165%
Agent turns
0%
Response time
-22%
Model gemini-3.6-flashMeasured 8/21/2026v116 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
Write a `relic.conf` TOML snippet configuring Azure Key Vault integration for certificate signing. Provide the server URL endpoint targeting a key vault named `my-vault` and certificate `my-cert`.
What was checked, without and with the skill
Checked
Without skill
With skill
Formats the Key Vault URL using the /certificates/ path segment.
Missed
Passed
Uses the domain suffix .vault.azure.net in the URL.
Passed
Passed
case-06 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md414 linessingle file
Tauri Skill
Comprehensive assistance with Tauri development, generated from official documentation.
When to Use This Skill
This skill should be triggered when:
Building cross-platform desktop applications with Rust + WebView
Implementing native system integrations (file system, notifications, system tray)
Setting up Tauri project structure and configuration
Debugging Tauri applications in VS Code or Neovim
Configuring Windows/macOS/Linux code signing for distribution
Developing mobile apps with Tauri (Android/iOS)
Creating Tauri plugins for custom native functionality
Implementing IPC (Inter-Process Communication) between frontend and backend
Optimizing Tauri app security and permissions
Setting up CI/CD pipelines for Tauri app releases
Key Concepts
Multi-Process Architecture
Tauri uses a Core Process (Rust) and WebView Process (HTML/CSS/JS) architecture:
Core Process: Manages windows, system tray, IPC routing, and has full OS access
WebView Process: Renders UI using system WebViews (no bundled browser!)
Principle of Least Privilege: Each process has minimal required permissions