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".
64
75%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/15-mobile-tauri/SKILL.mdQuality
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 frontend for native platforms), and provides comprehensive trigger terms covering file extensions, platform names, and common user phrases. The explicit 'Use quando' and 'Trigger em' sections ensure Claude can reliably select this skill when appropriate.
| 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' (criar apps nativos usando Tauri v2, gerar APK, executáveis, adaptar frontend web) and 'when' (explicit 'Use quando' clause plus a detailed 'Trigger em' list with specific keywords). Both dimensions are thoroughly addressed. | 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
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable code examples and concrete configuration for Tauri v2 development, which is its main strength. However, it is significantly over-verbose, inlining large blocks of boilerplate configuration and standard patterns that Claude could generate independently. The workflow lacks explicit validation checkpoints for complex native build operations, and the content organization would benefit from moving detailed code examples to referenced files.
Suggestions
Drastically reduce inline content by moving the full tauri.conf.json, CSS safe areas, and TypeScript hooks to the referenced `docs/skill-guides/mobile-tauri.md`, keeping only key patterns and commands in the main skill file.
Remove sections that describe what Claude already knows: 'Entradas Esperadas', 'Saidas Esperadas', 'Responsabilidades', and 'Regra de Codigo' add minimal actionable value.
Add explicit validation steps to the build workflow: e.g., verify APK signature, test on emulator before release, validate permissions after build, with error recovery guidance.
Convert the flat 'Checklist Pre-Build' into a sequenced workflow with verification gates between stages (e.g., 'only proceed to APK signing after device testing passes').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines. It includes large boilerplate JSON configs, full React hooks with state management, CSS blocks, and extensive handoff/checklist sections that Claude could generate on its own. The 'Quando Usar/Nao Usar', 'Entradas Esperadas/Saidas Esperadas', 'Responsabilidades', and 'Regra de Codigo' sections add little actionable value. Much of this content explains things Claude already knows (safe area CSS, basic TypeScript patterns, platform detection). | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples: complete TypeScript functions for notifications and file system, working JSON configuration, bash commands for setup and build, and concrete CSS. Commands are specific with exact package names and versions. | 3 / 3 |
Workflow Clarity | The build steps are listed but lack explicit validation checkpoints and error recovery. There's no 'validate -> fix -> retry' loop for the build process, which involves destructive/complex operations (APK signing, native builds). The checklist is a flat list without sequencing or verification steps between stages. | 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 monolithic with large inline code blocks (full JSON config, multiple TypeScript examples, CSS) that could be split into referenced files. The content that should be in the guide file is largely duplicated inline. | 2 / 3 |
Total | 8 / 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
7577622
- 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.