CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tauri

Tauri commands, permissions, capabilities, security config, path handling, cross-platform file ops, and native filesystem APIs. Use when mentioning Tauri, desktop apps, Rust commands, invoke, capabilities, permissions, ResourceId, file paths, or platform differences.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable, well-sectioned reference skill whose project-specific security and IPC guidance is excellent, but it is a ~240-line monolith with no bundle files. Redundant async notes and inlined API-reference tables hurt both token efficiency and progressive disclosure.

Suggestions

Move the path manipulation, platform constants, and base directory function tables into a references/path-api.md file and keep only the context-detection rule, the async caveat, and one canonical example inline in SKILL.md.

Remove the duplicate async explanation: the 'Note on Async' section repeats the sync/async distinction already stated under Platform Constants — keep it in one place.

Trim the 'Import Pattern' section (it restates imports shown in the code examples) and condense the four anti-pattern subsections into a single BAD/GOOD table.

DimensionReasoningScore

Conciseness

The body contains high-value, project-specific guidance (CSP configuration, ownership boundaries, generated-bindings rules), but the path API tables explaining 'Get parent directory', 'Get filename', and the base-directory listing restate API behavior Claude already knows, and the async note duplicates the same point made under Platform Constants. This matches the 'mostly efficient but includes some unnecessary explanation' anchor rather than the 4 anchor, where only minor trimming would be needed.

3 / 5

Actionability

Guidance is fully executable throughout: copy-paste-ready CSP JSONC, TypeScript path/filesystem snippets, a concrete 'cargo check --manifest-path ...' verification command, a context-detection table with file globs, and explicit BAD/GOOD anti-pattern pairs. Specific examples cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

Key flows carry explicit validation checkpoints: 'smoke-test a real tauri dev AND a release build, watching the webview console for CSP violations', 'cargo check' for IPC changes, and 'inspect the diff before committing' regenerated bindings. It falls short of 5 because these are scattered rules rather than a clearly sequenced multi-step workflow with error-recovery feedback loops, and above 3 because checkpoints are explicit, not missing.

4 / 5

Progressive Disclosure

The body has clear section headers, but with no references/ or scripts/ files, everything is inlined — including ~80 lines of path-function and base-directory API tables that are classic separate-file reference material. This fits 'some structure but content that should be separate is inline'; it is above 2 because the section organization is genuinely good, and below 4 because the bulk reference content belongs in a one-level-deep bundle file.

3 / 5

Total

15

/

20

Passed

Description

83%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 that explicitly states the skill's scope and provides an explicit, trigger-rich 'Use when' clause. Its main weaknesses are keyword-style topic listing instead of action verbs and a few missing natural synonyms in the trigger list.

DimensionReasoningScore

Specificity

The description enumerates several concrete capability areas — 'commands, permissions, capabilities, security config, path handling, cross-platform file ops, and native filesystem APIs' — giving specific, comprehensive coverage of the Tauri domain. It falls short of a 5 because these are topic nouns rather than concrete actions (no verbs like 'extract' or 'configure'), and below 4 would understate the breadth and specificity of the enumerated areas.

4 / 5

Completeness

It explicitly answers both 'what' (the enumerated capability areas) and 'when' with a concrete 'Use when mentioning...' clause listing specific trigger phrases. This matches the 5 anchor's requirement of clearly and explicitly answering both with concrete triggers; the 4 anchor would apply only if the 'when' were less explicit.

5 / 5

Trigger Term Quality

The 'Use when mentioning Tauri, desktop apps, Rust commands, invoke, capabilities, permissions, ResourceId, file paths, or platform differences' clause covers many natural terms a user would say, including the distinctive 'invoke' and 'ResourceId'. A few natural terms are missing (e.g., 'CSP', 'webview', 'IPC', 'tauri.conf.json'), keeping it below the comprehensive synonym-level 5 anchor.

4 / 5

Distinctiveness Conflict Risk

'Tauri', 'Rust commands', 'invoke', and 'ResourceId' carve out a clear, framework-specific niche with distinct triggers. Generic terms like 'permissions', 'file paths', and 'platform differences' create minor overlap risk with general Rust or filesystem skills, so it sits just below the minimal-conflict 5 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

EpicenterHQ/epicenter

Path

.agents/skills/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.