Overview of how to develop a Rill project
59
52%
Does it follow best practices?
Impact
84%
1.55xAverage score across 2 eval scenarios
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/rill-development/SKILL.mdRill pipeline file format and structure conventions
Models as .yaml
0%
100%
Source model materialized
0%
100%
Connector resource file
0%
0%
olap_connector in rill.yaml
0%
0%
timeseries set
100%
100%
Dimension count
100%
100%
Measure count
100%
100%
Single ingest model
100%
100%
snake_case resource names
100%
100%
snake_case env var names
100%
100%
No undocumented YAML properties
100%
100%
Managed DuckDB connector with partitioned source model
OLAP connector in rill.yaml
40%
100%
Connector named after driver
0%
100%
Managed DuckDB connector
0%
0%
No mode: read on managed connector
50%
100%
Source model as YAML file
100%
100%
Source model materialized
0%
100%
Dev partition configured
25%
100%
Ingest-once pattern
100%
100%
No invented env vars
100%
100%
No hardcoded secrets
100%
100%
3ad909d
Table of Contents
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.