freya

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

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/freya/skills/freya/SKILL.md

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 thorough, highly actionable Freya reference with excellent code examples, but it is long and largely monolithic, working against token efficiency and progressive disclosure. Splitting major topics into referenced files would materially improve both.

Suggestions

Move the detailed theming (define_theme!/ColorsSheet/Preference) and event-handler catalog into separate referenced files, keeping only the essential pattern inline in SKILL.md.

Tighten prose sections like Readable/Writable and Context API to assume Claude's competence and let the code carry the explanation.

Add inline one-level-deep links (e.g. 'See theming/THEMING.md') next to each major section so navigation is signposted where the topic appears, not just in a trailing Further Reference list.

Dimension	Reasoning	Score
Conciseness	Largely lean reference prose with executable snippets, but at ~980 lines several sections (full theming macro walkthrough, the event catalog, Readable/Writable prose) over-explain concepts Claude could derive from the code.	3 / 5
Actionability	Pervasive copy-paste-ready Rust examples covering the common cases, with concrete builder calls, hook usage, and feature-gated snippets.	5 / 5
Workflow Clarity	Opens with a clear three-option workflow (lint/refactor/feature) and most topics are well sequenced; it is reference rather than a destructive/batch process, so explicit validation checkpoints are not required, but none are present where they'd help.	4 / 5
Progressive Disclosure	Good section headings, but the bulk of the reference (theming, events, state, async) is inlined monolithically rather than split out; the pointers to AGENTS.md, _docs/, and examples/ appear only at the end and are not signposted inline per topic.	3 / 5
	Total	15 / 20 Passed

Description

87%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 concise, well-formed description that clearly states both capability and trigger conditions for a distinct niche. Minor gains possible from broader synonym coverage, but it is strong overall.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete deliverables ('best practices, patterns, and conventions') plus concrete artifacts ('components, hooks, elements'), with only minor coverage gaps.	4 / 5
Completeness	Explicitly states what it does ('Freya Rust GUI framework best practices, patterns, and conventions') and when to use it with concrete trigger phrases.	5 / 5
Trigger Term Quality	'Use when writing Freya components, hooks, elements, or working on a Freya project' gives good natural-term coverage, though it relies on a single product name and lacks synonym/extension variations.	4 / 5
Distinctiveness Conflict Risk	Targets a clearly defined niche (the Freya framework) with distinct triggers and minimal risk of firing for unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (986 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: marc2332/freya
Path: plugins/freya/skills/freya/SKILL.md
Commit: 0cc52c6

Reviewed: ~21 hours ago

Table of Contents

Discovery Implementation Validation

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.