brasa-template-writer

Generate and migrate brasa YAML templates to the modern pipeline format.

51|8|Updated Feb 18, 2023

Search Tags:#template #migration #yaml #pipeline #etl #data-pipelines #brasa

Ready to run

npx skills add https://github.com/wilsonfreitas/brasa --skill brasa-template-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brasa-template-writer
Source: https://github.com/wilsonfreitas/brasa/tree/main/.claude/skills/brasa-template-writer
Command: npx skills add https://github.com/wilsonfreitas/brasa --skill brasa-template-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write new brasa YAML templates from scratch or migrate legacy templates (with reader.function and handler-based fields) to the modern pipeline-based format, simplifying template management.

Core Features & Use Cases

Mode Detection: automatically identify when to write new templates versus migrate legacy ones.
Workflow: guided steps for writing or migrating templates, including analyzing legacy readers and applying transformations.
Examples: canonical examples and migration rules illustrating expected outputs.

Quick Start

Create a new brasa YAML template for a given data source or migrate a legacy template to the modern pipeline format.

Frequently Asked Questions about brasa-template-writer

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

FAQPage Schema

How do I migrate legacy brasa YAML templates to the modern pipeline format?▼

To migrate legacy brasa YAML templates, the Skill analyzes old reader.function and handler-based fields, applies transformation rules, and aligns the output with the official pipeline schema for production-ready data pipelines.

What is a brasa YAML template and when do I need to create one?▼

A brasa YAML template defines data pipelines for ETL processing. You need to create one when configuring new data sources or modernizing legacy ETL configurations to ensure frontmatter requirements like name and description are met.

How do I convert old brasa ETL configurations that use reader functions and handlers?▼

Converting old brasa ETL configurations requires identifying reader.function and handler-based fields in legacy templates, then applying migration rules and pipeline writer blocks to transform them into the modern pipeline-based format.

Can I include scripts and reference components when creating a new brasa YAML template?▼

Yes, when creating a new brasa YAML template, you can include optional component directories such as scripts, references, and assets to support your data pipeline configuration and ensure production-ready outputs.

Does the brasa template migration process automatically detect legacy YAML formats?▼

Yes, the brasa template migration process features mode detection that automatically identifies whether to write a new template from scratch or migrate an existing legacy template based on the presence of reader.function and handler fields.

What are the limitations when migrating brasa YAML templates for data pipelines?▼

Migration limitations include dependency on the official pipeline schema structure; templates lacking required frontmatter fields like name and description will fail alignment, and unsupported legacy reader formats may need manual transformation before applying pipeline writer blocks.