rill-theme

Detailed instructions and examples for developing theme resources in Rill

Quality

55%

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/rill-theme/SKILL.md

Quality

Content

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

The body is highly actionable with ready-to-use YAML examples and a clear theming workflow, but it is noticeably verbose and monolithic — the full palette listings and JSON schema would be better placed in separate reference files.

Suggestions

Move the full JSON schema and the complete 24/9/11-color palette listings into a references file (e.g., references/theme-schema.md) and link to it, keeping only a minimal example inline.

Trim the duplicated full palette YAML for both light and dark to representative entries plus a comment noting the remaining indices follow the same pattern.

Replace generic color-theory exposition (hex, HSL, WCAG basics) with terse pointers, since Claude already knows these concepts.

Dimension	Reasoning	Score
Conciseness	The full 24-color qualitative, 9-step sequential, and 11-step diverging palettes are spelled out for both light and dark modes (~130 lines of example values) and a ~100-line JSON schema is dumped inline, which are padded sections Claude does not need verbatim.	2 / 5
Actionability	Provides copy-paste-ready YAML (recommended structure, minimal example, legacy format) and concrete palette/color-format guidance; minor gaps remain because the brand-extraction steps are guidance rather than executable code.	4 / 5
Workflow Clarity	The on-brand theme workflow is a clearly sequenced three-step process (extract palette -> build light -> adapt dark) with embedded contrast/WCAG checkpoints; not a destructive or batch operation, so the validation cap does not apply.	4 / 5
Progressive Disclosure	Section headers give some structure, but no bundle files exist and the JSON schema reference plus the full palette listings are inlined monolithically rather than split into one-level-deep reference files.	3 / 5
	Total	13 / 20 Passed

Description

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

The description clearly identifies the domain and is reasonably distinct, but it lacks a trigger ('Use when...') clause and concrete action coverage, capping completeness and trigger quality at mid-range.

Suggestions

Add a 'Use when...' clause naming concrete triggers (e.g., 'Use when creating or customizing Rill dashboard themes, color palettes, or brand styling').

Expand the action list beyond 'developing' to specific verbs like 'define color palettes', 'configure light/dark modes', and 'apply brand colors to dashboards'.

Include natural synonyms such as 'color palette', 'brand colors', and 'dashboard styling' so the description matches how users phrase the request.

Dimension	Reasoning	Score
Specificity	Names the domain ('theme resources in Rill') and one concrete action ('developing'), but 'instructions and examples' describes the skill's contents rather than additional actions, so coverage is not comprehensive.	3 / 5
Completeness	Has a clear 'what' (instructions and examples for developing theme resources) but no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes relevant keywords ('theme', 'Rill') but omits natural variations users would say such as 'color palette', 'brand colors', or 'dashboard styling'.	3 / 5
Distinctiveness Conflict Risk	'Developing theme resources in Rill' carves a clear niche with minimal conflict risk; only minor overlap with adjacent Rill skills keeps it just below a 5.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rilldata/agent-skills
Path: skills/rill-theme/SKILL.md
Commit: 84f7d7c

Reviewed: about 7 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.