CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mobile-tauri

Implementa e empacota aplicacoes mobile e desktop com Tauri. 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".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concrete, executable Tauri v2 guide with strong workflow validation and a genuine feedback loop, weakened by inline reference material and some process boilerplate. Closing the plugin-os dependency gap and splitting bulk config/code into reference files would lift it further.

Suggestions

Move the full tauri.conf.json sample, safe-area CSS, and native-feature code into reference files (e.g. references/tauri-conf.md, references/mobile-adaptations.md), keeping SKILL.md as an overview with clearly signaled one-level-deep pointers.

Add '@tauri-apps/plugin-os' to the install list (the platform-detection code imports it) and include an icon-generation command such as 'npx tauri icon' since the pre-build checklist requires icons for all platforms.

Remove the duplicated 'npx tauri android build --apk' between 'Comandos de Build' and 'Setup Android', and trim the governance/process boilerplate sections that add no executable guidance.

DimensionReasoningScore

Conciseness

Core setup, config, and code sections are efficient, but process-boilerplate sections ('Entradas Esperadas', 'Saidas Esperadas', 'Evidencia de Conclusao', 'Regra de Codigo'), a duplicated 'npx tauri android build --apk' (in both 'Comandos de Build' and 'Setup Android'), and a ~60-line inline tauri.conf.json could be trimmed or moved out.

3 / 5

Actionability

Commands, full tauri.conf.json, and TypeScript/CSS code are mostly copy-paste ready, but the platform-detection code imports '@tauri-apps/plugin-os' which is absent from the install list, and no icon-generation command (e.g. 'npx tauri icon') is given despite the checklist requiring icons for all platforms.

4 / 5

Workflow Clarity

A numbered sequence (Responsabilidades 1-6), an explicit validation checkpoint ('rodar o build de release... instalar no dispositivo real... modo avião'), a feedback loop ('corrigir a config e repetir o build completo — não patchear no dispositivo'), and a pre-build checklist together cover sequence, validation, recovery, and checklist.

5 / 5

Progressive Disclosure

The ~360-line body inlines reference-grade material (full config JSON, safe-area CSS, native-feature code) that belongs in separate reference files, and offers only one external pointer ('consultar docs/skill-guides/mobile-tauri.md apenas quando necessario') with no bundle files present.

3 / 5

Total

15

/

20

Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit, comprehensive trigger list and a clear what/when structure in third-person voice. Its only weaknesses are a thin enumeration of capabilities in the 'what' clause and a few overly broad trigger terms.

DimensionReasoningScore

Specificity

'Implementa e empacota aplicacoes mobile e desktop com Tauri' names the domain with exactly two actions; it never enumerates the concrete capabilities the body covers (permissions, notifications, file system, per-platform build targets), matching the 1-2-concrete-actions anchor rather than the several-actions anchor.

3 / 5

Completeness

It explicitly answers both 'what' ('Implementa e empacota aplicacoes mobile e desktop com Tauri') and 'when' via an explicit 'Trigger em:' clause with concrete trigger phrases, matching the top anchor rather than the 'when could be more explicit' anchor below it.

5 / 5

Trigger Term Quality

Seventeen natural triggers include file extensions (.exe, .dmg, .deb, .AppImage), platform names (Android, Windows, macOS), and synonyms ('app nativo', 'build nativo', 'cross-platform'), matching the comprehensive-coverage-with-extensions anchor.

5 / 5

Distinctiveness Conflict Risk

Niche-anchored terms (Tauri, APK, .dmg, .AppImage, 'build nativo') keep it mostly distinct, but broad terms like 'mobile', 'Android', and 'cross-platform' carry minor overlap risk with other mobile-development skills, so it sits below the minimal-conflict anchor.

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

felvieira/claude-skills-fv

Path

skills/15-mobile-tauri/SKILL.md

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.