roku

App dashboard with purple-themed aesthetic, top-bar navigation, card-based layouts, and developer-first workflows.

Quality

67%

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

Quality

Content

100%

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

The body is a tight, well-structured instruction-only skill that gives Claude everything needed to author Roku design-system guidelines: foundations, a sequenced workflow, required output structure, and quality gates. It assumes Claude's competence without padding and stays self-contained.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with no padding or explanation of concepts Claude already knows; every section (tokens, rules, quality gates, constraint language) earns its place.	3 / 3
Actionability	It gives concrete, executable guidance for an instruction-only skill: a numbered authoring workflow, an explicit required output structure, a concrete required-states list ("default, hover, focus-visible, active, disabled, loading, error"), and "must"/"should" constraint language.	3 / 3
Workflow Clarity	The Guideline Authoring Workflow is a clearly sequenced 6-step process backed by Quality Gates; since this involves no destructive or batch operation, no validation feedback loop is required.	3 / 3
Progressive Disclosure	The skill is self-contained and organized into clear, navigable sections with no need for external reference files, which the rubric rewards with a 3 for well-organized single-file instruction skills.	3 / 3
	Total	12 / 12 Passed

Description

35%

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

The description reads as a product feature blurb rather than a skill capability statement: it describes what the dashboard looks like but not what the skill does or when to use it. It has no trigger terms and no "Use when" guidance.

Suggestions

Reframe the description around the skill's actions in third person, e.g. 'Authors implementation-ready Roku design-system guidelines: tokens, component rules, and accessibility criteria.'

Add an explicit trigger clause, e.g. 'Use when creating or updating Roku app-dashboard design guidelines, component rules, or design tokens.'

Surface natural trigger terms users would actually say ('design system', 'component guidelines', 'design tokens') rather than describing the dashboard aesthetic.

Dimension	Reasoning	Score
Specificity	It names the domain ("App dashboard") and concrete attributes ("purple-themed aesthetic", "top-bar navigation", "card-based layouts") but lists no actions the skill performs, so it sits above the vague score-1 examples yet below a comprehensive score-3 listing of specific actions.	2 / 3
Completeness	It conveys a recognizable "what" (a Roku app-dashboard design-system skill) but the "when" is entirely missing with no "Use when..." trigger clause, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	Phrases like "purple-themed aesthetic", "top-bar navigation", and "developer-first workflows" describe the artifact rather than the natural terms a user would say to invoke this skill, and there are no common keyword variations.	1 / 3
Distinctiveness Conflict Risk	The aesthetic-and-navigation combo is somewhat specific, but the generic design-system framing could still overlap with other UI/dashboard design skills, so it is not a clearly distinct niche.	2 / 3
	Total	7 / 12 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: bergside/awesome-design-skills
Path: skills/roku/SKILL.md
Commit: f631a09

Reviewed: 1 day 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.