mobile-tauri
Skill OPCIONAL do Mobile/Desktop Developer para criar apps nativos usando Tauri v2. Use quando precisar gerar APK Android, executável Windows/macOS/Linux, ou adaptar o frontend web para plataformas nativas. Trigger em: "mobile", "Tauri", "APK", "app nativo", "desktop app", "Windows app", "macOS app", "Android", "cross-platform", "build nativo", "executável", ".exe", ".dmg", ".deb", ".AppImage", "notificação nativa", "file system nativo".
86
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (Tauri v2 native app development), lists concrete actions (generating APKs, executables, adapting web frontends), and provides comprehensive trigger terms covering platforms, file types, and common user phrases. The explicit 'Use quando' and 'Trigger em' sections ensure Claude can reliably select this skill. The only minor note is the use of Portuguese, but the technical terms are universally recognizable.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'criar apps nativos usando Tauri v2', 'gerar APK Android', 'executável Windows/macOS/Linux', 'adaptar o frontend web para plataformas nativas'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (create native apps using Tauri v2, generate APK, executables, adapt frontend for native platforms) and 'when' (explicit 'Use quando' clause plus a detailed 'Trigger em' list with specific keywords). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including file extensions (.exe, .dmg, .deb, .AppImage), platform names (Android, Windows, macOS), common phrases ('mobile', 'APK', 'desktop app', 'cross-platform', 'app nativo'), and the specific technology ('Tauri'). These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Tauri v2 native app development. The combination of Tauri-specific terminology, native build artifacts (.exe, .dmg, .deb, .AppImage, APK), and cross-platform desktop/mobile focus makes it very unlikely to conflict with web-only or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides strong, actionable code examples for Tauri v2 development with good platform coverage (Android, desktop, notifications, file system). However, it suffers from excessive process/governance boilerplate that doesn't add value for Claude, and the workflow lacks explicit validation steps between build stages. The large inline configuration and code blocks would benefit from being split into referenced files to improve the overview-to-detail ratio.
Suggestions
Remove or drastically reduce meta-process sections (Governança Global, Entradas/Saídas Esperadas, Evidência de Conclusão, Regra de Código) that don't teach Tauri-specific knowledge — these waste tokens on things Claude already knows or that belong in global policies.
Add explicit validation steps after build commands (e.g., verify APK was generated, check file size, test installation on emulator) and include error recovery guidance for common build failures.
Move the large tauri.conf.json and the mobile navigation hook into referenced files (e.g., docs/skill-guides/tauri-config-example.md) and keep only a minimal config snippet inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes substantial boilerplate sections (Governança Global, Quando Usar/Não Usar, Entradas/Saídas Esperadas, Evidência de Conclusão, Handoff) that add process overhead without teaching Claude anything new. The code examples themselves are reasonably lean, but the overall document could be significantly tightened by removing meta-process sections and focusing on actionable content. | 2 / 3 |
Actionability | The skill provides fully executable code examples throughout: setup commands, complete TypeScript functions for platform detection, notifications, file system access, a full tauri.conf.json configuration, build commands, and Android environment setup. All code is copy-paste ready with real imports and proper typing. | 3 / 3 |
Workflow Clarity | While there's a pre-build checklist and the setup/build commands are listed, the overall workflow lacks explicit validation checkpoints and feedback loops. For example, after 'npx tauri android build --apk' there's no verification step, no error recovery guidance, and the checklist items are not sequenced into the build workflow. Build operations are somewhat destructive/complex and would benefit from validate-fix-retry loops. | 2 / 3 |
Progressive Disclosure | The skill references 'docs/skill-guides/mobile-tauri.md' for detailed setup and multiple policy files, which is good progressive disclosure. However, the main file itself is quite long (~250 lines) with large inline code blocks (the full tauri.conf.json, the mobile navigation hook) that could be split into referenced files. The balance between overview and detail is skewed toward too much inline content. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- felvieira/claude-skills-fv
- Commit
e9f6648
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.