rill-theme

Detailed instructions and examples for developing theme resources in Rill

Quality

32%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/rill-theme/SKILL.md

Quality

Content

42%

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

The skill is highly actionable with concrete, copy-paste-ready YAML examples and clear color format specifications. However, it is extremely verbose—the full color palettes listed twice (light/dark) and the inline JSON schema bloat the content significantly. The lack of any external file references or content splitting makes this a monolithic document that wastes token budget on repetitive color values.

Suggestions

Reduce the recommended theme example to show 3-4 qualitative colors with a comment like '# ... up to color-qualitative-24' instead of listing all 24 twice

Move the full JSON schema to a separate REFERENCE.md file and link to it from the main skill

Add a brief validation/verification section explaining how to confirm a theme is applied correctly (e.g., what to look for in Rill's UI or any error messages)

Consolidate the sequential and diverging palette examples into a pattern description rather than listing every single color value

Dimension	Reasoning	Score
Conciseness	The content is extremely verbose. The introduction explains what themes are (Claude knows this from context). The full 24-color qualitative palettes are listed twice (light and dark), the diverging and sequential palettes are listed twice, and the full JSON schema is dumped at the end. The recommended theme example alone is ~100 lines of color values that could be summarized with a pattern and a few examples. Much of this could be cut by 60%+ without losing actionability.	1 / 3
Actionability	The content provides fully executable YAML examples that are copy-paste ready, including a complete recommended structure, a minimal example, and a legacy format. Color formats are clearly specified with concrete examples, and referencing methods show exact YAML syntax for both project-wide and per-dashboard usage.	3 / 3
Workflow Clarity	The skill covers a simple resource type (theme YAML files) so multi-step workflows aren't critical, but the content lacks any validation steps or feedback loops. There's no guidance on how to verify a theme is working correctly, no mention of what errors look like, and no troubleshooting steps. For a non-destructive operation this is acceptable but not ideal.	2 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files. The full JSON schema, all 24 qualitative colors for both modes, all sequential and diverging palettes, and the legacy format are all inline. The schema reference alone could be a separate file. With no bundle files, the massive inline content makes this poorly organized for progressive disclosure.	1 / 3
	Total	7 / 12 Passed

Description

22%

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

This description is too vague and lacks both concrete actions and explicit trigger guidance. It fails to explain what specific tasks the skill enables (e.g., creating color palettes, customizing dashboards) and provides no 'Use when...' clause to help Claude select it appropriately. The mention of 'Rill' adds some distinctiveness but is insufficient on its own.

Suggestions

Add specific concrete actions the skill covers, e.g., 'Creates custom color schemes, typography settings, and layout configurations for Rill dashboards.'

Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user asks about Rill theming, custom themes, dashboard styling, or theme YAML configuration.'

Include natural keywords users might say, such as 'Rill theme', 'dashboard appearance', 'custom styling', 'theme YAML', or specific file types involved.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'detailed instructions and examples' without listing any concrete actions. It does not specify what 'theme resources' entails or what operations can be performed.	1 / 3
Completeness	The description weakly addresses 'what' (developing theme resources) but provides no 'when' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	It includes 'theme resources' and 'Rill' which are somewhat relevant keywords, but misses common variations or natural terms a user might say (e.g., 'styling', 'theming', 'CSS', 'colors', 'custom themes', 'Rill dashboard').	2 / 3
Distinctiveness Conflict Risk	'Rill' provides some specificity to a particular platform, but 'theme resources' is broad enough that it could overlap with other theming or styling skills. The lack of concrete actions makes it harder to distinguish.	2 / 3
	Total	6 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: rilldata/agent-skills
Commit: e7c833e

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.