rill-rillyaml

Detailed instructions and examples for developing the rill.yaml file

Quality

53%

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

Quality

Content

57%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 a well-organized, accurate reference for rill.yaml with strong executable examples, but it is monolithic: the full JSON schema is inlined rather than split into a reference file, and it offers no development workflow or validation step for the config it describes. Moderate quality overall.

Suggestions

Move the full JSON schema into a references/ file (e.g., references/rill-yaml-schema.json) and keep only the key properties inline, linking to it from a short 'Reference documentation' pointer.

Add a brief development workflow with a validation checkpoint, e.g., '1. Start from the minimal example, 2. Add sections as needed, 3. Run `rill start` to verify the config parses and the View as dropdown appears for mock users.'

Trim duplication between the core-concepts prose and the schema section (e.g., mock_users and ignore_paths are fully documented twice).

Dimension	Reasoning	Score
Conciseness	The prose core-concepts section is efficient and covers Rill-specific knowledge Claude would not know, but the 'Reference documentation' section inlines the entire ~290-line JSON schema, substantially duplicating what the prose already explains (mock_users, ignore_paths, env). This sits between anchor 3 and 4 but the duplication is noticeable, so 3.	3 / 5
Actionability	Provides copy-paste-ready executable examples — a minimal one-line YAML and a comprehensive complete example — plus concrete semantics (leading '/' for ignore_paths, {{ .env.<variable> }} templating syntax). Minor gaps (no command to apply or verify the file) keep it below the fully executable anchor 5.	4 / 5
Workflow Clarity	This is a reference-style skill with no ordered development workflow and no validation checkpoints (e.g., no 'run rill start to verify the config parses' step). The section structure substitutes for a sequence, but checkpoints are missing, matching anchor 3.	3 / 5
Progressive Disclosure	Section headers and the minimal/complete example split are well organized, but there are no reference files at all — the full JSON schema clearly belongs in a separate references/ file yet is inlined as ~290 lines, matching anchor 3 ('content that should be separate is inline' with some structure present).	3 / 5
	Total	13 / 20 Passed

Description

48%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 names a clear, niche target (the rill.yaml file) but is thin: it lists no concrete capabilities and provides no 'use when' trigger guidance. It functions as a label rather than an effective routing description.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g., 'Use when creating or editing rill.yaml, configuring Rill project settings, or setting up connectors, mock users, or environment variables.'

Replace 'Detailed instructions and examples' with the specific actions the skill enables, e.g., 'Configure project settings, default OLAP/AI connectors, env variables, mock users, and resource-type defaults in rill.yaml.'

Include natural trigger synonyms such as 'Rill project config', 'Rill configuration file', and 'project settings' so users' varied phrasing matches the skill.

Dimension	Reasoning	Score
Specificity	The description names the domain ('developing the rill.yaml file') but the only actions offered are generic — 'Detailed instructions and examples' — with no concrete capabilities listed, matching the 'Processes PDF files' anchor level.	2 / 5
Completeness	The 'what' is reasonably clear (instructions and examples for developing rill.yaml), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	'rill.yaml' is a natural keyword a user would say, but no synonyms or variations appear (e.g., 'Rill project config', 'project settings'), matching the 'Works with PDF files' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific file 'rill.yaml' carves a clear niche with only minor overlap risk against closely related Rill skills; it is not a 5 because the description offers only the filename as a discriminator, with no distinct trigger phrases.	4 / 5
	Total	12 / 20 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
relative_links	Relative link issues: 6 missing, 5 suspicious	Warning

	Total	15 / 16 Passed

Repository: rilldata/agent-skills
Path: skills/rill-rillyaml/SKILL.md
Commit: 1307e7f

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