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

77%

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

The canonical home for this skill is freya in marc2332/freya

SKILL.md
Quality
Evals
Security

Quality

Content

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

Excellent, highly actionable reference material for the Freya framework with barely a wasted token within sections. The weaknesses are structural: the promised three-path workflow (lint/refactor/feature) has no follow-through sequence or validation checkpoints, and a monolithic 1000-line body keeps peripheral feature material in the main file instead of reference files.

Suggestions

Follow through on the opening triage: add a short sequenced workflow per choice (lint / refactor / add feature) ending in a validation checkpoint, e.g. 'after changes, run the headless TestingRunner or cargo check before reporting done'.

Move peripheral feature sections (camera, terminal, HTML, plot, i18n, borderless, material design, icons) into one-level-deep reference files (e.g. references/features.md), keeping only a one-line summary and feature table in SKILL.md.

Trim the 'Further Reference' section's repo paths to only those usable from any checkout, and consider consolidating the long theming section (define_theme!/ColorsSheet/Preference details) into a references/theming.md with a quick-use example left inline.

DimensionReasoningScore

Conciseness

Sections are dense and Freya-specific (event catalog, hook rules, define_theme! flow, radio channels) with essentially no explanation of concepts Claude already knows; only minor tightening is possible. Not a 5 because the sheer volume of the single file loads everything into context at once.

4 / 5

Actionability

Nearly every section carries copy-paste-ready Rust snippets (.maybe/.map builders, use_radio with derive_channel, WritableSetter::new, define_theme! with get_theme!), plus concrete catalogs (events, features, Focus variants) covering the common cases.

5 / 5

Workflow Clarity

The opening instructs asking the user to choose "Lint and improve existing code / Refactor existing code / Add a new feature", but the body never provides a sequenced workflow or validation checkpoint per path; it is a topic reference, not a process. Headless testing exists as a section yet is not wired in as a validate-after-change step, matching the anchor of steps listed but checkpoints missing or implicit.

3 / 5

Progressive Disclosure

No bundle files exist; ~1000 lines are inlined in SKILL.md, and peripheral topics (camera, terminal, HTML, plot, i18n, borderless, material design) clearly belong in separate reference files. Good section headers and a one-level-deep "Further Reference" section provide some structure, matching the anchor of structure present but content that should be separate is inline.

3 / 5

Total

15

/

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 niche-skill description with an explicit 'Use when...' clause and good natural trigger terms. Its main weakness is that the 'what' is stated generically (best practices, patterns, conventions) rather than as concrete actions.

DimensionReasoningScore

Specificity

The description names the domain ("Freya Rust GUI framework") and its deliverables ("best practices, patterns, and conventions") but lists no concrete actions comparable to "extract text, fill forms". It sits between the generic-actions anchor (2) and the 1-2-concrete-actions anchor (3), and is not noticeably below the midpoint.

3 / 5

Completeness

Both parts are present: the what ("best practices, patterns, and conventions" for Freya) and an explicit "Use when..." clause with concrete triggers. The 'what' is generic rather than action-level, matching the anchor where 'what' is present but could be more concrete rather than the fully explicit 5.

4 / 5

Trigger Term Quality

"Use when writing Freya components, hooks, elements, or working on a Freya project" covers the natural terms a user would say (Freya, components, hooks, GUI). A few natural variations (e.g. "Freya UI", "GUI app", "freyaui") are missing, so it falls short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Freya" names a specific niche framework with distinct triggers; only a general Rust development skill could plausibly overlap. Clear niche with minimal conflict risk.

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 (1008 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

marc2332/freya

Path

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