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".
85
Quality
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 well-structured skill description with excellent trigger term coverage and clear 'what/when' guidance. The explicit 'Trigger em:' list is particularly effective for skill selection. The main weakness is that the specific capabilities could be more detailed - it mentions generating builds but doesn't elaborate on other Tauri-specific features it handles.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Tauri v2, native apps) and some actions ('criar apps nativos', 'gerar APK Android', 'executável Windows/macOS/Linux', 'adaptar o frontend web'), but lacks comprehensive detail on specific capabilities like what Tauri features it handles. | 2 / 3 |
Completeness | Clearly answers both what ('criar apps nativos usando Tauri v2', 'gerar APK Android', 'executável', 'adaptar o frontend web') and when ('Use quando precisar...') with an explicit 'Trigger em:' clause listing specific activation keywords. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including platform names ('Android', 'Windows', 'macOS'), file extensions ('.exe', '.dmg', '.deb', '.AppImage', 'APK'), and user-friendly terms ('mobile', 'desktop app', 'app nativo', 'cross-platform'). Users would naturally use these terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche focused specifically on Tauri v2 native app development. The combination of 'Tauri', specific file extensions, and platform-specific terms creates a clear, non-conflicting identity that wouldn't overlap with general web development or other mobile frameworks. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid skill with excellent actionability - the code examples are complete, typed, and immediately usable. The structure is well-organized with appropriate progressive disclosure. Main weaknesses are some verbosity in governance/meta sections and missing validation checkpoints in the build workflow, which is important for native builds that can fail in non-obvious ways.
Suggestions
Add explicit validation steps to the build workflow (e.g., 'Verify APK signature: apksigner verify --print-certs app.apk' after build)
Remove or condense the 'Regra de Codigo' section - this is general knowledge Claude already has
Add error recovery guidance for common build failures (missing SDK, signing issues, permission errors)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary sections like 'Regra de Codigo' at the end which restates general coding principles Claude already knows, and the governance references at the top add overhead without actionable content. | 2 / 3 |
Actionability | Provides fully executable code examples throughout - complete TypeScript hooks, CSS with safe areas, bash commands, and JSON configuration. All examples are copy-paste ready with proper imports and type annotations. | 3 / 3 |
Workflow Clarity | Has a pre-build checklist and clear handoff sections, but lacks explicit validation checkpoints in the build workflow. The 'Comandos de Build' section lists commands without verification steps between them, and there's no error recovery guidance for failed builds. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from setup to advanced features. References external docs appropriately ('docs/skill-guides/mobile-tauri.md apenas quando necessario') and keeps the main content focused on actionable guidance. | 3 / 3 |
Total | 10 / 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
524725e
- 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.