generating-model

Generate or revise a single dbt model artifact from migration context.

3|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/accelerate-data/migration-utility --skill generating-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generating-model
Source: https://github.com/accelerate-data/migration-utility/tree/main/skills/generating-model
Command: npx skills add https://github.com/accelerate-data/migration-utility --skill generating-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate or revise a single dbt model artifact from deterministic migration context. This capability helps maintain consistency during targeted migrations by preserving business logic and ensuring a stable, reviewable model artifact for a single subject.

Core Features & Use Cases

  • Preserve the selected transformed SQL when possible and use refactored_sql for ordinary writers, ensuring the final model remains faithful to the migration intent.
  • Derive model naming mechanically from the target object's name, and return a single ModelGenerationOutput aligned with the internal contract.
  • Support focused, single-item generation workflows and avoid batch orchestration, enabling precise revisions and faster feedback loops.

Quick Start

Provide the target object and project context to generate or revise a single dbt model.

Frequently Asked Questions about generating-model

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

FAQPage Schema
How do I generate a single dbt model from an existing SQL transformation during a migration?

Generate a single dbt model by providing the target object and project context; the skill preserves the selected transformed SQL and mechanically derives the model name from the target object to produce a reviewable artifact.

Can I revise one dbt model artifact without triggering a full batch orchestration?

Yes, you can revise a single dbt model artifact independently; the skill supports focused, single-item generation workflows to enable precise adjustments and faster feedback loops without batch orchestration.

What's the best way to ensure my dbt model naming stays consistent when migrating tables?

To ensure consistent dbt model naming during migration, the skill derives the model_name mechanically from the target object's name, maintaining deterministic alignment with your migration context.

Does generating a dbt model artifact validate compile and test results?

Generating a dbt model artifact validates invariants and returns a ModelGenerationOutput with execution flags reflecting dbt compile and test results for the single item.

When should I use refactored_sql instead of the original transformed SQL for dbt model generation?

Use refactored_sql for dbt model generation when appropriate for ordinary writers; the skill enforces preservation of the selected transformed SQL by default to remain faithful to migration intent.