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

Discovery

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.

The description is too vague and lacks both concrete actions and explicit trigger guidance. While it mentions the domain ('theme resources in Rill'), it fails to specify what actions are performed or when Claude should select this skill. It reads more like a section heading than a functional skill description.

Suggestions

Add a 'Use when...' clause specifying trigger conditions, e.g., 'Use when the user asks about creating or modifying themes, styling dashboards, or customizing visual appearance in Rill.'

List specific concrete actions such as 'Create theme YAML files, configure color palettes, define typography settings, and apply custom styles to Rill dashboards.'

Include natural trigger terms users might say, such as 'theme', 'styling', 'colors', 'dashboard appearance', 'custom look', or specific Rill file extensions.

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 are performed.	1 / 3
Completeness	The description weakly addresses 'what' (developing theme resources) but completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	It includes 'theme resources' and 'Rill' as relevant keywords, but misses common variations or natural terms a user might say, such as 'styling', 'theming', 'custom themes', 'CSS', or specific file types.	2 / 3
Distinctiveness Conflict Risk	'Rill' provides some specificity to a particular platform, and 'theme resources' narrows the domain somewhat, but the description is still vague enough that it could overlap with general theming or styling skills.	2 / 3
	Total	6 / 12 Passed

Implementation

42%

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

The skill provides highly actionable, concrete YAML examples and a complete schema reference for Rill themes, which is its main strength. However, it is extremely verbose—the full color palettes are listed twice (light/dark), the JSON schema is dumped inline, and the introduction explains concepts that are self-evident from the examples. The content would benefit enormously from being split into a concise overview with references to detailed palette and schema files.

Suggestions

Move the full 24-color qualitative, sequential, and diverging palette examples to a separate reference file (e.g., PALETTES.md) and keep only the minimal + a brief annotated example in the main skill.

Move the JSON schema to a separate SCHEMA.md or reference file and link to it from the main skill body.

Remove the introductory paragraphs explaining what themes are and how reconciliation works—Claude doesn't need this context to create a theme file.

Add an explicit numbered workflow: 1) Create themes/<name>.yaml, 2) Add type: theme + light/dark blocks, 3) Reference from rill.yaml or dashboard file, 4) Verify theme loads in rill start.

Dimension	Reasoning	Score
Conciseness	The content is extremely verbose. The introduction explains what themes are and how they work (concepts Claude can infer from examples). 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 when a minimal example plus a note about optional palette keys would suffice.	1 / 3
Actionability	The content provides fully concrete, copy-paste-ready YAML examples for both comprehensive and minimal themes, shows exactly how to reference themes from rill.yaml and per-dashboard files, specifies supported color formats, and includes a complete JSON schema reference. Claude can immediately create a theme file from this.	3 / 3
Workflow Clarity	The skill covers a simple resource type (no destructive operations), so multi-step validation is less critical. However, the workflow for creating and applying a theme is implicit rather than explicitly sequenced—there's no clear 'Step 1: create file, Step 2: reference it, Step 3: verify it loads' flow. The information is scattered across sections rather than presented as a clear process.	2 / 3
Progressive Disclosure	Everything is in a single monolithic file with no references to external files. The full JSON schema, all palette examples (light and dark with 24+ colors each), legacy format, and reference documentation are all inline. The recommended theme example alone could be a separate reference file, and the schema definitely should be. There's no bundle structure to support splitting, but the content badly needs it.	1 / 3
	Total	7 / 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: 65ccd1f

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.