rill-rillyaml
Detailed instructions and examples for developing the rill.yaml file
32
24%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/rill-rillyaml/SKILL.mdQuality
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 'rill.yaml' provides a specific keyword, the description fails to explain what developing a rill.yaml file involves or when this skill should be selected. It reads more like a section heading than a functional skill description.
Suggestions
List specific concrete actions the skill covers, e.g., 'Configures data sources, defines metrics, sets up dashboard models in rill.yaml files'.
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Rill project configuration, rill.yaml setup, data source definitions, or Rill Developer project files'.
Clarify the domain context (e.g., Rill Developer / Rill Cloud) to improve distinctiveness and help Claude differentiate this skill from other YAML or configuration-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'detailed instructions and examples for developing the rill.yaml file' but does not list any concrete actions like 'configure data sources', 'define metrics', or 'set up dashboards'. It vaguely references instructions and examples without specifying what those entail. | 1 / 3 |
Completeness | The description partially addresses 'what' (instructions for developing rill.yaml) but provides no explicit 'when' clause or trigger guidance. The lack of a 'Use when...' clause caps this at 2 per the rubric, and the 'what' itself is also weak, so it scores a 1. | 1 / 3 |
Trigger Term Quality | It includes 'rill.yaml' which is a specific and relevant keyword a user might mention. However, it lacks broader natural trigger terms like 'Rill configuration', 'Rill project setup', 'YAML config', or related variations that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'rill.yaml' provides some specificity that distinguishes it from generic YAML or configuration skills. However, without more detail about what rill.yaml configures or its domain, it could overlap with other Rill-related or YAML configuration skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides useful examples for rill.yaml configuration but is severely bloated by an inlined JSON schema that duplicates the prose explanations and includes raw documentation markup. The content would benefit greatly from separating the schema into a reference file, trimming redundant explanations, and adding a clear workflow for creating and validating the configuration file.
Suggestions
Move the full JSON schema to a separate REFERENCE.md file and link to it from the main skill, keeping only the most essential properties inline.
Remove the raw documentation markup (:::info, :::tip blocks) from the schema section — these are not rendered in markdown and add noise.
Trim the 'Core Concepts' prose that duplicates information already shown in the complete YAML example — let the example speak for itself with brief inline comments.
Add a brief workflow section: 1) Create rill.yaml at project root, 2) Add required configuration, 3) Validate by running `rill start` and checking for errors.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose. It includes a full JSON schema dump (~100+ lines) as 'reference documentation' that adds massive token cost. The 'Core Concepts' section explains basic concepts Claude can infer. The introductory comparison to package.json/dbt_project.yml is unnecessary padding. Much of the schema content duplicates what was already explained in the prose sections above it. | 1 / 3 |
Actionability | The skill provides two concrete YAML examples (minimal and complete) that are copy-paste ready, which is good. However, the JSON schema section contains raw documentation markup (:::info, :::tip) that isn't actionable and appears to be copy-pasted from docs rather than curated for Claude. There are no specific commands or workflows for creating/validating the file. | 2 / 3 |
Workflow Clarity | For a configuration file skill, the workflow is relatively simple (create/edit rill.yaml), and the examples provide decent guidance. However, there's no explicit workflow for creating a new rill.yaml, no validation steps to verify the configuration is correct, and no guidance on common errors or how to troubleshoot them. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic wall of text with no references to external files. The full JSON schema is inlined (~150 lines) when it could be in a separate reference file. The schema contains embedded documentation links (e.g., '/developers/build/connectors/olap') and tip/info blocks that are clearly from external docs pasted inline, creating noise rather than structure. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%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
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.