tinybird

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

Quality

56%

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

53%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 a compact, well-organized index with a genuinely useful quick-reference section, but it functions as a pointer document whose targets are missing: all 14 referenced rule files are absent from the bundle, leaving the skill with little standalone actionable content and no workflow guidance. Inlining the key rules or shipping the rule files with descriptive labels would resolve most weaknesses.

Suggestions

Ship the 14 rule files referenced under 'Rule Files' — or inline the most important rules into the body — since every referenced path is currently dangling.

Annotate each rule-file entry with what it covers (e.g., 'rules/endpoint-optimization.md — query tuning for API endpoints') and map the 'When to Apply' bullets to the relevant file so readers know which file to open for which task.

Add a minimal workflow with a validation checkpoint (e.g., edit datafile -> run tb build/tests locally -> tb deploy) and one or two executable tb command examples to raise actionability and workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations Claude already knows — sections are 'When to Apply', a rule-file index, and a dense 'Quick Reference' of genuinely non-obvious facts ('Build target comes from tinybird.config.json dev_mode', 'Use MergeTree by default; AggregatingMergeTree for materialized targets'). It falls short of 5 only because the intro line ('Guidance for Tinybird file formats, SQL rules, optimization patterns, and data modeling...') duplicates the frontmatter description and overlaps the 'When to Apply' list.	4 / 5
Actionability	The Quick Reference contains some concrete, specific guidance (named commands like 'tb sql and tb logs default to local unless --cloud or --branch=<branch-name>', config keys, engine choices), but the actual executable detail is deferred to the 14 rule files and no usage examples or command invocations appear inline — matching 'Some concrete guidance but incomplete... missing key details' rather than score 4's 'concrete code or commands with minor gaps'.	3 / 5
Workflow Clarity	There is no multi-step sequence anywhere: 'When to Apply' is a list of situations, not ordered steps, and no validation/checkpoint guidance exists (deploy and batch operations are in scope yet unvalidated). It also doesn't qualify for the simple-skill exception because it is an index into rule files with no mapping of which task reads which file, so the reader cannot form a clear procedure — matching 'Steps listed but validation gaps; sequence present but checkpoints missing' at best.	3 / 5
Progressive Disclosure	The body is structured as a one-level index of 14 rule files ('rules/datasource-files.md', 'rules/pipe-files.md', ...), but none of those files exist in the bundle — no rules/, references/, scripts/, or assets/ directories are present, so every reference is dangling and navigation dead-ends. The list entries are also bare paths with no per-file description of what each covers, fitting 'Minimal structure... references are buried [or broken]' rather than score 3's 'references present but not clearly signaled'.	2 / 5
	Total	12 / 20 Passed

Description

60%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 well-scoped to a distinct niche with strong natural trigger vocabulary, but it is a topic list rather than a capability statement: no concrete actions and no explicit 'use when' trigger clause. Adding verbs and a trigger sentence would lift both specificity and completeness.

Suggestions

Rewrite as an action-led sentence, e.g., 'Create, optimize, and review Tinybird datafiles — datasources, pipes, endpoints, and materialized views — following Tinybird SQL and file-format best practices.'

Add an explicit trigger clause: 'Use when creating or editing Tinybird files (.datasource, .pipe, .connection), writing or optimizing Tinybird SQL, or deploying with the tb CLI.'

Include the file extensions (.datasource, .pipe) and the tb CLI as trigger terms users naturally mention.

Dimension	Reasoning	Score
Specificity	The description is a noun-phrase topic list — "file formats, SQL rules, optimization patterns, and best practices for datasources, pipes, endpoints, and materialized views" — with no concrete verbs or actions at all. It names the Tinybird domain in detail but never states what the skill does (create, optimize, review, etc.), matching the anchor 'Names the domain but actions are minimal or generic' rather than score 3, which requires 1-2 concrete actions like 'Processes PDF files and extracts content'.	2 / 5
Completeness	The 'what' is reasonably clear (Tinybird formats/rules/best practices across named resource types), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It does not reach score 4 because 'when' is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	Strong natural vocabulary for the niche: "Tinybird", "SQL", "datasources", "pipes", "endpoints", "materialized views" are exactly what a user would say when needing this skill. A few common variations are missing (e.g., ".datasource"/".pipe" file extensions, "tb" CLI, "deploy"), which fits 'Good keyword coverage; a few natural terms missing' rather than the comprehensive-synonym coverage of score 5.	4 / 5
Distinctiveness Conflict Risk	"Tinybird" plus its resource types (pipes, materialized views, endpoints) is a clear niche with distinct triggers and virtually no overlap risk with other skills, matching the score 5 anchor. It is not score 4 because there is no 'minor overlap risk with closely related skills' — the vendor-specific terminology is unambiguous.	5 / 5
	Total	14 / 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: 1a03fa7

Reviewed: 11 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.