tinybird-typescript-sdk-guidelines

Define Tinybird datasources, pipes, and queries in TypeScript with full type inference.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Tinybird TypeScript SDK enables developers to define Tinybird resources with full type inference, allowing end-to-end type safety for datasources, pipes, and queries.

Core Features & Use Cases

  • Fully typed datasources and pipes with autocomplete and type-safe client generation
  • Supports mixed formats and migration from legacy .datasource/.pipe files
  • Provides clear guidance for installation, initialization, and project scaffolding to accelerate adoption
  • Use case: start a new Tinybird project with typed resource definitions and a typed client to ensure schema integrity

Quick Start

Install the Tinybird SDK in your TypeScript project and define your first typed datasource and endpoint.

Frequently Asked Questions about tinybird-typescript-sdk-guidelines

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

FAQPage Schema
How do I define Tinybird datasources and pipes with TypeScript type inference?

You can define Tinybird datasources and pipes with TypeScript type inference by using the Tinybird TypeScript SDK to create fully typed resource definitions, ensuring schema integrity and type-safe client generation for queries.

Can I migrate legacy Tinybird .datasource and .pipe files to TypeScript?

Yes, you can migrate legacy Tinybird .datasource and .pipe files to TypeScript by adopting the Tinybird TypeScript SDK, which supports mixed formats and structured migration paths to fully typed resource definitions.

What is the best way to generate a type-safe Tinybird client in a new TypeScript project?

The best way to generate a type-safe Tinybird client is installing the Tinybird SDK in your TypeScript project, defining typed datasources and endpoints, and leveraging full type inference for end-to-end workflow safety.

Does the Tinybird TypeScript SDK support mixed format resource definitions?

Yes, the Tinybird TypeScript SDK supports mixed format resource definitions, allowing developers to maintain existing legacy .datasource and .pipe files alongside new typed definitions during a gradual migration process.

Why define Tinybird queries with TypeScript instead of using untyped configuration files?

Defining Tinybird queries with TypeScript provides full type inference, autocomplete, and schema integrity, whereas untyped legacy .datasource and .pipe files lack end-to-end type safety and structured validation.