Overview of how to develop a Rill project
54
28%
Does it follow best practices?
Impact
100%
1.04xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/rill-development/SKILL.mdFull pipeline from S3 to dashboard
rill.yaml exists
100%
100%
olap_connector in rill.yaml
100%
100%
Managed OLAP connector
100%
100%
S3 connector file
100%
100%
Model is YAML not SQL
100%
100%
Model is materialized
100%
100%
Dev partition present
87%
100%
Secrets in .env
100%
100%
Metrics view timeseries
100%
100%
Explore dashboard exists
100%
100%
No ETL duplication
100%
100%
.env variable naming
100%
100%
Fix broken Rill project structure
Models converted to YAML
50%
100%
Model is materialized
40%
100%
No ETL duplication
100%
100%
OLAP connector added
100%
100%
olap_connector in rill.yaml
100%
100%
Metrics view timeseries
100%
100%
Explore dashboard created
100%
100%
Secrets not hardcoded
100%
100%
changes.md produced
100%
100%
Connector file naming
100%
100%
No undocumented properties
100%
100%
Custom API endpoints for metrics view
Uses metrics_sql resolver
100%
100%
Both APIs use metrics_sql
100%
100%
API files in apis/ directory
100%
100%
Lowercase snake_case names
100%
100%
type: api declared
100%
100%
Query parameter templating
100%
100%
No undocumented properties
100%
100%
References existing metrics view
100%
100%
api_docs.md produced
100%
100%
Two distinct endpoints
100%
100%
65ccd1f
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.