CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rill-analysis

Overview of how to analyze data in a Rill project

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/rill-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is a well-structured, actionable agent playbook with a clear phased workflow, named tools, concrete constraints, and an explicit output format. It scores consistently just below excellent due to mild redundancy between sections, no example query payload, and no explicit validation step.

Suggestions

Merge the 'Reflection between queries' section into the Phase 2 OODA loop to remove the duplicated guidance and save tokens.

Add one concrete example of a 'query_metrics_view' call (dimensions, measures, time_range) so the first analytical query is fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is largely efficient, prescriptive, and free of concepts Claude already knows (e.g. 'Execute a MINIMUM of 4-6 distinct analytical queries', 'should be below 10000 rows'), but the 'Reflection between queries' section largely restates the Phase 2 OODA loop and 'Analysis guidelines' repeats phase instructions. Matches 'Efficient; minor instances of over-explanation that could be trimmed', not a 5 due to this redundancy.

4 / 5

Actionability

It names exact tools ('list_metrics_view', 'query_metrics_view', 'create_chart'), concrete chart-type-to-data mappings, specific features (delta_abs, delta_rel), and a concrete output template. As an instruction-only skill the guidance is actionable; the minor gap is the absence of an example query payload, matching 'Mostly executable guidance; concrete code or commands with minor gaps'.

4 / 5

Workflow Clarity

A clear three-phase sequence with ordered discovery steps, an explicit OODA feedback loop, 'If any step fails, investigate and adapt', and per-query reflection checkpoints. Not a 5 because there is no explicit validation step for the correctness of results, matching 'Clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-sectioned with clear headers and a clearly signaled external 'rill-charts' skill reference. Minor gaps: the skill exceeds 50 lines and the chart-type selection list could be split into a reference file, matching 'Good structure; most content is appropriately placed; minor organization gaps'.

4 / 5

Total

16

/

20

Passed

Description

40%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 is too vague to serve its purpose: it names the Rill domain but lists no concrete capabilities and provides no 'Use when' trigger guidance. Its only strength is the distinct 'Rill project' niche, which keeps conflict risk low.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks to analyze data, explore metrics, or find insights in a Rill project or dashboard'.

Replace 'Overview of how to analyze data' with the concrete actions the skill performs, e.g. 'Run iterative metric queries, compare time periods, and generate charts to surface insights'.

Include natural trigger terms and synonyms users would say, such as 'Rill dashboard', 'metrics', 'dimensions', 'measures', and 'data insights'.

DimensionReasoningScore

Specificity

The description 'Overview of how to analyze data in a Rill project' names the domain but offers no concrete actions (no querying, charting, or comparing metrics); this matches the anchor 'Names the domain but actions are minimal or generic'. It is not a 3 because that anchor requires 1-2 concrete actions to be stated.

2 / 5

Completeness

'Overview of how to analyze data' is a vague 'what' and there is no 'when'/'Use when' clause at all, matching 'Has a vague what and no when'. Not a 3 because the 'what' is not clear and concrete, and the missing trigger guidance caps it regardless.

2 / 5

Trigger Term Quality

'analyze data' and 'Rill project' are relevant, natural keywords, but common variations users would say (metrics, dashboards, insights, explore) are missing, matching 'Some relevant keywords but missing common variations or synonyms'. Not a 2 because 'Rill' is a specific natural term rather than generic filler.

3 / 5

Distinctiveness Conflict Risk

'Rill project' carves a clear niche with minimal conflict risk against other skills, but the generic 'analyze data' phrasing leaves minor overlap risk with general data-analysis skills, matching 'Mostly distinct; minor overlap risk'. Not a 5 because the trigger phrasing itself is not distinct.

4 / 5

Total

11

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rilldata/agent-skills

Path

skills/rill-analysis/SKILL.md

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.