tinybird

Tinybird file formats, SQL rules, optimization patterns, and best practices for datasources, pipes, endpoints, and materialized views.

Quality

76%

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 ./.agents/skills/tinybird/SKILL.md

Quality

Content

80%

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 token-efficient, actionable index with a strong Quick Reference, but it lacks an explicit task-to-rule-file mapping and—critically—every referenced rule file is missing from the bundle, breaking progressive disclosure.

Suggestions

Ship the referenced rules/*.md files (or remove the dead references), since the entire skill's detail content is unreachable without them.

Cross-reference 'When to Apply' scenarios to specific rule files (e.g. 'Designing endpoints → rules/endpoint-files.md, rules/endpoint-optimization.md') so the routing is explicit.

Add a short build/deploy workflow with a validation checkpoint (e.g. run tb tests / tb deploy only after local validation passes) to cover the destructive batch operations involved.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet-pointed content with no preamble or explanation of concepts Claude already knows (e.g. what MergeTree or SQL is); every line carries a concrete fact or directive.	3 / 3
Actionability	The Quick Reference gives concrete, usable directives and commands — 'tb deploy targets Tinybird Cloud production', 'Use MergeTree by default; AggregatingMergeTree for materialized targets', 'Filter early, select only needed columns' — while appropriately delegating deep detail to the rule files.	3 / 3
Workflow Clarity	The 'When to Apply' scenarios and 'Rule Files' list are present but not cross-referenced, so there is no explicit mapping from a task to the rule file that handles it, and no sequencing or validation checkpoints for multi-step operations like build/deploy.	2 / 3
Progressive Disclosure	The structure is well-designed as a lean overview pointing one level deep to 14 rule files, but none of the referenced rules/*.md files exist in the bundle, so the references are non-functional dead links and actual navigation fails.	2 / 3
	Total	10 / 12 Passed

Description

72%

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 scopes the skill to Tinybird's domain with strong, distinctive trigger terms, but it lists categories rather than concrete actions and omits an explicit 'Use when…' trigger clause.

Suggestions

Lead with concrete action verbs, e.g. 'Create and optimize Tinybird datasources, pipes, endpoints, and materialized views' instead of listing abstract categories like 'SQL rules' and 'optimization patterns'.

Add an explicit 'Use when…' clause naming the file extensions and situations, e.g. 'Use when creating or editing .datasource, .pipe, or .connection files or running tb deploy/SQL workflows'.

Consider including the natural tool/file variations ('.datasource', '.pipe', 'tb deploy', 'Tinybird Cloud') that users mention.

Dimension	Reasoning	Score
Specificity	Names the Tinybird domain and its concrete resource types (datasources, pipes, endpoints, materialized views) but uses categories/nouns rather than concrete action verbs like 'create', 'deploy', or 'optimize'; not vague enough for a 1, but lacks the explicit action list required for a 3.	2 / 3
Completeness	Clearly states what the skill covers but has no 'Use when…' clause or equivalent explicit trigger guidance; per the rubric a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Covers the natural Tinybird vocabulary users actually say — 'datasources', 'pipes', 'endpoints', 'materialized views', 'SQL', 'file formats' — which are precisely the product's domain terms.	3 / 3
Distinctiveness Conflict Risk	Tied to the specific Tinybird product and its named resource types, giving it a clear niche that is unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: MapleTechLabs/maple
Path: .agents/skills/tinybird/SKILL.md
Commit: 8d347f8

Reviewed: about 12 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.