tinybird

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

Quality

71%

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

72%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 body is admirably concise and well-organized as an overview-plus-index, with concrete distilled rules in the Quick Reference. Its main weaknesses are the absence of sequenced workflows with validation checkpoints and the fact that all 14 referenced rule files are missing, breaking progressive disclosure.

Suggestions

Provide the referenced rules/*.md files (e.g. rules/sql.md, rules/build-deploy.md) so the one-level-deep navigation actually resolves.

Add at least one short sequenced workflow with an explicit validation checkpoint for build/deploy, since the skill covers destructive/batch operations.

Include a few inline, copy-paste-ready command or SQL snippets (e.g. a minimal `tb deploy` or MergeTree example) so the body is actionable without depending solely on the external rule files.

Dimension	Reasoning	Score
Conciseness	The ~45-line body is lean and assumes Claude's competence: no concept explanations, no padding, and every section (triggers, rule index, distilled quick-reference) earns its place.	5 / 5
Actionability	Quick Reference gives concrete, actionable rules ('Build target comes from tinybird.config.json dev_mode', 'Use MergeTree by default; AggregatingMergeTree for materialized targets') and real commands, but the deeper executable detail is externalized to 14 rule files that are not present.	4 / 5
Workflow Clarity	The body is an overview/index with no sequenced multi-step workflow and no validation checkpoints, while the skill spans build/deploy and datasource-editing contexts where the rubric caps workflow clarity at 3 when validation is absent.	3 / 5
Progressive Disclosure	Structure and signaling of the one-level-deep rule references are clear, but the referenced rules/ directory and all 14 rule files do not exist, so the navigation path is broken rather than resolvable.	3 / 5
	Total	15 / 20 Passed

Description

70%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 specific and clearly niched to Tinybird, but it omits any explicit 'Use when...' trigger guidance, which caps completeness at 3. Trigger-term coverage is good but lacks natural user synonyms and file extensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when creating or editing Tinybird datafiles (.datasource, .pipe), writing SQL, or working with materialized views.'

Add natural synonyms and file extensions users would actually say ('Tinybird', '.datasource', '.pipe', 'tb') to broaden trigger-term coverage.

Lead with concrete action verbs ('Create, optimize, and deploy Tinybird...') rather than noun-only capability categories.

Dimension	Reasoning	Score
Specificity	Names the Tinybird domain and several concrete capability areas ('SQL rules, optimization patterns, and best practices for datasources, pipes, endpoints, and materialized views'), with only minor gaps in explicit action verbs.	4 / 5
Completeness	Provides a clear 'what' but lacks any explicit 'Use when...' trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	Includes accurate domain keywords ('Tinybird file formats', 'SQL rules', 'datasources, pipes, endpoints, materialized views') but leans technical and omits common natural synonyms/extensions like 'Tinybird' alone or '.datasource'.	4 / 5
Distinctiveness Conflict Risk	'Tinybird' is a clearly distinct niche and its listed objects (datasources, pipes, endpoints, materialized views) are product-specific, giving minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 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: 3cb9193

Reviewed: 1 day 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.