tinybird

Apply Tinybird project patterns and SQL rules to datasources, pipes, endpoints, and materialized views.

1.6k|107|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/Makisuo/maple --skill tinybird-makisuo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tinybird
Source: https://github.com/Makisuo/maple/tree/main/.agents/skills/tinybird
Command: npx skills add https://github.com/Makisuo/maple --skill tinybird-makisuo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and codifies Tinybird project conventions to prevent drift in datasources, pipes, endpoints, and materialized views.

Core Features & Use Cases

  • Comprehensive rules and templates for project structure (datasources, pipes, endpoints, materialized views).
  • Guidance for SQL, data modeling, and optimization to improve reliability and performance.
  • Use Case: teams adopting Tinybird across multiple projects can apply uniform patterns to accelerate development and audits.

Quick Start

Initialize Tinybird project files using the provided rules and templates to ensure consistent structure across datasources, pipes, endpoints, and materialized views.

Frequently Asked Questions about tinybird

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Tinybird project file patterns across multiple data pipelines?

To standardize Tinybird project file patterns, apply codified SQL rules and templates for datasources, pipes, endpoints, and materialized views. This prevents project drift and ensures consistent engineering patterns across multiple teams and deployments.

When should I use MergeTree vs AggregatingMergeTree in Tinybird datasources?

Choosing MergeTree vs AggregatingMergeTree in Tinybird datasources depends on your optimization needs. Apply consistent engineering patterns through structured SQL rules to select the correct engine, ensuring reliable performance and safe repeatable deployments.

What are the best practices for structuring Tinybird materialized views and endpoints?

Best practices for structuring Tinybird materialized views and endpoints involve applying templated SQL guidance and project structure conventions. This centralizes data modeling rules to improve reliability and streamline data-work pipeline audits.

Can I use SQL rules to validate Tinybird pipe structures before deployment?

Yes, you can use SQL rules to validate Tinybird pipe structures before deployment. The framework provides rule validation and structure conventions for datasources and pipes, ensuring safe, repeatable deployments across your data pipelines.

Does applying uniform patterns to Tinybird projects accelerate data pipeline development?

Applying uniform patterns to Tinybird projects accelerates data pipeline development by providing comprehensive rules and templates. Teams adopting Tinybird can prevent drift and streamline audits for datasources, pipes, endpoints, and materialized views.

Why does my Tinybird data model drift between different pipe and datasource configurations?

Tinybird data models drift between configurations without centralized conventions. Applying standardized project file patterns, SQL rules, and optimization guidelines codifies datasource and pipe structures to prevent inconsistencies.