CtrlK
BlogDocsLog inGet started
Tessl Logo

native-feel-cross-platform-desktop

Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include "cross-platform desktop", "Electron alternative", "Tauri vs native", "WebView wrapper", "near-native performance", "Raycast architecture", "WebKit/WebView2 quirks", "WKWebView", "system tray app", "global hotkey app", "launcher app". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.

77

Quality

96%

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

92%Weight 40%Scale 1-3

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

A tightly written, highly actionable advisory skill with a clear sequenced workflow and excellent references/ routing. The one real defect is that two workflow-critical checklist files (decision-tree.md, ship-readiness.md) are referenced but absent from the bundle, which breaks progressive disclosure for the skill's own gating steps.

Suggestions

Add the missing checklists/decision-tree.md and checklists/ship-readiness.md files (or remove the references and inline the gating criteria), since both the workflow and the output-style section depend on them existing.

If the checklists are intentionally deferred, replace the bare file references with a brief inline description of what each gate checks so the skill remains usable when the files are absent.

Double-check every path mentioned in the body (e.g., references/03-webview-survival.md § "Hidden window throttling") resolves to a real file and section, to keep navigation one-level-deep and intact.

DimensionReasoningScore

Conciseness

The ~41-line body is dense and high-signal with no padding of concepts Claude already knows — it jumps straight into tenets, routing, anti-patterns, and trade-offs. It is not level 2 because there is no unnecessary explanation; even the long "one-paragraph version" is a deliberate compression that earns its place as orientation.

3 / 3

Actionability

For an advisory skill it gives concrete, specific guidance: a question→reference routing table, per-anti-pattern recommendations pointing at exact files ("Recommend references/02-architecture.md instead"), and concrete architectural specifics (Swift/AppKit, C#/WPF, Rust+UniFFI, ~400MB). It is not level 2 because the guidance is complete and specific rather than abstract or pseudocode-like, and the scoring note explicitly does not penalize absence of code in instruction-only skills.

3 / 3

Workflow Clarity

"How to use this skill" is a clearly numbered 4-step sequence with explicit gating checkpoints ("Before recommending... run the decision tree", "Before the user claims... run ship-readiness"). It is not level 2 because validation checkpoints are explicit and named, not implicit. This is an advisory (not destructive/batch) skill, so the missing-feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

The references/ layer is excellent — all 7 referenced files exist, one level deep, with a clear routing guide. However the workflow's two gating checkpoints point to checklists/decision-tree.md and checklists/ship-readiness.md, and no checklists/ directory exists in the bundle, so those references are broken. Scored against the actual bundle structure (per guideline), this navigation defect keeps it below 3; it is not level 1 because the references that do exist are well-organized and clearly signaled rather than monolithic.

2 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

An excellent description: concrete capabilities, broad and natural trigger terms, explicit use/negative-trigger guidance, and a clearly distinct niche with conflict-reducing exclusions. It uses third-person "the user" framing and avoids fluff.

DimensionReasoningScore

Specificity

Names multiple concrete actions and qualities — "designing, prototyping, or rewriting a desktop app" plus "fast launch, native windowing, native input handling, native materials" — rather than vague language. It is not the level below (2) because it goes well beyond naming a single domain to enumerating several specific capabilities.

3 / 3

Completeness

Opens with an explicit "Use when the user is designing, prototyping, or rewriting..." clause and adds a "Do NOT trigger this skill for..." negative-trigger clause, clearly answering both what and when. It is not level 2 because the trigger guidance is explicit, not merely implied.

3 / 3

Trigger Term Quality

Explicitly enumerates natural trigger terms a user would actually say ("cross-platform desktop", "Electron alternative", "Tauri vs native", "WKWebView", "system tray app", "global hotkey app", "launcher app"). Coverage is broad, matching the level-3 anchor; it is not level 2 because it is not missing common variations.

3 / 3

Distinctiveness Conflict Risk

A tightly scoped niche (native-feel multi-OS desktop) with explicit negative exclusions (not pure web, not pure mobile, not greenfield-without-native-feel) makes it unlikely to fire for the wrong skill. It is not level 2 because the explicit exclusions remove the realistic overlap cases.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
yetone/native-feel-skill
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.