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' clause and 'Trigger em' list make it highly actionable for skill selection. The only minor note is it's written in Portuguese, but the trigger terms include many universal technical terms.
| 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 native context makes it very unlikely to conflict with generic web development or other 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 excels in actionability with concrete, executable code examples covering setup, configuration, platform detection, native features, and build commands. However, it suffers from verbosity due to numerous meta-process sections (governance, inputs/outputs, handoff templates) that don't add actionable value for Claude, and the large inline configuration blocks could benefit from being referenced externally. The workflow would be stronger with explicit step-by-step sequencing and validation checkpoints between build stages.
Suggestions
Remove or drastically condense meta-process sections (Governança Global, Entradas/Saídas Esperadas, Evidência de Conclusão, Regra de Código) that don't provide actionable Tauri-specific guidance.
Add an explicit numbered workflow with validation steps, e.g.: 1. Init → 2. Verify config → 3. Dev test → 4. Validate on device → 5. Build release, with specific verification commands at each stage.
Move the large tauri.conf.json example and detailed Android setup to a referenced file (e.g., docs/skill-guides/mobile-tauri.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, Regra de Código) that add little value for Claude. The code examples themselves are reasonably lean, but the overall document could be significantly tightened by removing meta-process sections and obvious guidance. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout: setup commands, tauri.conf.json configuration, TypeScript hooks for platform detection and navigation, CSS safe areas, notification and file system APIs, and build commands with specific output paths. All code is concrete and complete. | 3 / 3 |
Workflow Clarity | While there's a pre-build checklist and handoff sections, the overall workflow lacks explicit sequencing with validation checkpoints. The build process (init → configure → adapt → build) is implied but not presented as a clear numbered sequence with verification steps between stages. For a multi-step process involving native builds, missing validation/feedback loops (e.g., verify Android SDK setup before building, validate config before packaging) caps this at 2. | 2 / 3 |
Progressive Disclosure | The skill references `docs/skill-guides/mobile-tauri.md` for detailed setup and several policy files, which is good progressive disclosure. However, the main file itself is quite long (~250 lines) with full configuration JSON and multiple code blocks that could be split into referenced files. The tauri.conf.json example alone is ~50 lines that could live in a separate reference. | 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
d87ad31
- 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.