CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

freya

Freya Rust GUI framework best practices, patterns, and conventions. Use when writing Freya components, hooks, elements, or working on a Freya project.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/freya/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

An exceptionally actionable reference: nearly every section carries complete, executable Rust examples that cover the framework's common cases, and the structure is logically organized. The weaknesses are duplication that could be trimmed (the async spawn pattern and conditional-rendering helpers are each covered twice), the absence of an explicit post-change validation workflow despite a testing section being available, and the monolithic inlining of ~1000 lines of per-feature API detail that belongs in separate reference files.

Suggestions

De-duplicate the async sections: keep the use_hook + spawn snippet once and have 'Async functions in components' reference it, and merge the .maybe/.map/.maybe_child explanations from 'Element Builder Pattern' and 'Conditional and Dynamic Rendering' into one place.

Add an explicit validation checkpoint to the workflow, e.g. 'After changing components, verify behavior with freya-testing (TestingRunner) or render_to_file snapshots' rather than leaving testing as a standalone topic.

Move peripheral feature guides (camera, terminal, code editor, plotting, HTML, i18n) into files under references/ and keep one-line pointers plus the feature table in SKILL.md, turning the 1000-line body into a true overview.

DimensionReasoningScore

Conciseness

The body is dense with framework-specific API detail Claude would not know, but contains real duplication: the use_hook + spawn async pattern appears verbatim in 'Spawning tasks' and again in 'Async functions in components', .maybe/.map/.maybe_child are demonstrated in 'Element Builder Pattern' and then re-explained bullet-by-bullet in 'Conditional and Dynamic Rendering', and the HTML section shows two back-to-back redundant use_hook examples. Mostly efficient, but several sections could be tightened, matching anchor 3 rather than 4.

3 / 5

Actionability

Dozens of complete, copy-paste-ready Rust examples cover the common cases (struct/owned/function components, use_state and Radio state, events, focus/a11y, define_theme!/get_theme!, freya-query, TestingRunner), with specific catalogs (event names, crate features, ColorsSheet fields). Only peripheral features (terminal, use_editable) defer to examples/, which does not undermine coverage of common cases.

5 / 5

Workflow Clarity

An entry decision point exists ('Start by asking the user what they would like to do: Lint and improve existing code / Refactor / Add a new feature'), but the rest is organized topically rather than as a sequence, and the headless-testing section is never wired in as an explicit post-change validation checkpoint ('verify with freya-testing after edits'). Sequence present but checkpoints missing or implicit matches anchor 3; there is no clear multi-step flow to justify 4.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and roughly 1000 lines of per-feature API reference (i18n, code editor, camera, terminal, plotting, theming deep-dive) are inlined in SKILL.md where a split into reference files clearly belongs. Good section headers and a clearly signaled 'Further Reference' section (AGENTS.md, crates/freya/src/_docs/, examples/) keep it above anchor 2's 'no section headers' case, but content that should be separate is inline, matching anchor 3.

3 / 5

Total

14

/

20

Passed

Description

73%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 solid description with an explicit and well-triggered 'Use when' clause anchored to a distinctive framework name, so conflict risk is minimal. Its main weakness is the generic 'best practices, patterns, and conventions' phrasing for the 'what', which undersells the skill's concrete breadth (state, theming, routing, testing, i18n).

Suggestions

Replace the generic 'best practices, patterns, and conventions' with concrete capabilities, e.g. 'Write Freya components, manage state (use_state, Radio, context), theme apps, handle events, and test with freya-testing.'

Add a few task-oriented trigger phrases users would naturally say, such as 'state management', 'theming', or 'routing' in a Freya app.

DimensionReasoningScore

Specificity

The description names the domain concretely ('Freya Rust GUI framework') and enumerates real artifacts ('components, hooks, elements'), matching the '1-2 concrete actions' anchor, but 'best practices, patterns, and conventions' is generic phrasing and it omits much of the skill's actual breadth (state management, theming, routing, testing). It does not list several specific actions, so it stays below anchor 4, and it is above anchor 2 because more than minimal generic action is conveyed.

3 / 5

Completeness

Both halves are present: a 'what' ('best practices, patterns, and conventions') and an explicit 'when' with concrete triggers ('Use when writing Freya components, hooks, elements, or working on a Freya project'). The 'what' is abstract category nouns rather than concrete capabilities, so it falls short of anchor 5's requirement that both parts be concrete.

4 / 5

Trigger Term Quality

'Freya', 'Rust GUI framework', 'components, hooks, elements', and 'Freya project' give good coverage of the terms a user would naturally say, since 'Freya' is the dominant trigger. A few natural variations (e.g. task-oriented phrases like 'state management', 'theming', or 'GUI in Rust') are missing, keeping it below the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Freya' is a highly distinctive framework name repeated in both the what and when clauses, giving a clear niche with minimal risk of triggering for any other skill (other Rust GUI frameworks like egui or iced are not mentioned). This matches the anchor-5 example's structure of a distinct domain with explicit triggers.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1015 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

marc2332/freya

Path

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