rill-rillyaml

Detailed instructions and examples for developing the rill.yaml file

Quality

47%

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

46%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 skill is actionable with strong worked YAML examples but is weighed down by an inlined ~270-line JSON schema and lacks a sequenced workflow with validation. Moving the schema to a reference file and adding a develop/validate sequence would markedly improve it.

Suggestions

Extract the full JSON schema block into a references/ file (e.g. rill-yaml.schema.md) and link to it from the body, keeping only key examples inline.

Add a short 'Developing rill.yaml' workflow: write minimal config -> add properties -> validate with `rill start` / parser -> iterate, with an explicit validation checkpoint.

Trim concept-level padding (e.g. the package.json/dbt analogy and admonition callouts) that Claude can infer, retaining only property-specific guidance.

Dimension	Reasoning	Score
Conciseness	The body inlines a ~270-line raw JSON schema with descriptions, examples, and admonitions that is reference padding, and repeats concept explanations Claude could largely infer, making it noticeably verbose.	2 / 5
Actionability	Provides concrete, copy-paste-ready minimal and complete YAML examples plus schema examples covering common configurations, with only minor gaps where properties are documented but not exemplified.	4 / 5
Workflow Clarity	Content is organized by topic with worked examples but offers no sequenced develop/edit/validate workflow or validation checkpoints, so the process sequence is implicit rather than explicit.	3 / 5
Progressive Disclosure	No bundle files exist and the large JSON schema that clearly belongs in a separate reference file is inlined monolithically, with minimal file-level separation despite topical section headers.	2 / 5
	Total	11 / 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 clearly identifies its domain (rill.yaml) and niche but is light on concrete actions and entirely missing a 'when to use' trigger clause. It is adequate but would benefit from explicit trigger phrases and more specific verbs.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when configuring or troubleshooting a Rill project's rill.yaml, setting OLAP/AI connectors, or defining project-wide defaults.'

Replace the generic verb 'developing' with specific actions like 'configure, validate, and document rill.yaml properties'.

Include natural synonyms and the file extension (e.g. 'rill.yaml, rill yaml, project config') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('rill.yaml file') but the only action ('developing') is generic, and 'instructions and examples' are content types rather than concrete actions, leaving coverage minimal.	2 / 5
Completeness	States a clear 'what' (instructions and examples for developing rill.yaml) but provides no 'Use when...' clause, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes the natural term 'rill.yaml' but omits common variations and synonyms such as 'rill yaml', 'project config', or 'configure rill', so keyword coverage is partial.	3 / 5
Distinctiveness Conflict Risk	Targeting the rill.yaml project config is a clear niche unlikely to fire for unrelated skills, with only minor overlap risk against other Rill-specific skills.	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: 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.