lfx-cdp-snowflake-connectors

Scaffold Snowflake connector integrations for crowd.dev with sources, types, and migrations.

8|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-cdp-snowflake-connectors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lfx-cdp-snowflake-connectors
Source: https://github.com/linuxfoundation/lfx-skills/tree/main/lfx-cdp-snowflake-connectors
Command: npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-cdp-snowflake-connectors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold end-to-end Snowflake connector integration scaffolding for crowd.dev, enabling rapid, consistent addition of new data-source connectors.

Core Features & Use Cases

  • Automatically scaffold source, types, buildSourceQuery, transformer, and required migrations for a Snowflake connector.
  • Enforce explicit user validation for all business logic and ensure exact column naming from the schema registry.
  • Wire up all touchpoints from data-source discovery through production deployments (types, activity mapping, and attribute sources).

Quick Start

Provide the platform and source details to start scaffolding a Snowflake connector for a new data source.

Frequently Asked Questions about lfx-cdp-snowflake-connectors

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

FAQPage Schema
How do I scaffold a Snowflake connector for a new data source?

Scaffolding a Snowflake connector requires providing platform and source details to automatically generate source queries, types, transformers, and migrations for crowd.dev integration.

What is included in end-to-end Snowflake connector scaffolding?

End-to-end Snowflake connector scaffolding includes source definitions, buildSourceQuery functions, types, transformers, activity mapping, attribute sources, and required database migrations.

Do I need to manually validate column names when building a Snowflake connector?

Manual column name validation is not needed because the scaffolding enforces exact column naming from the schema registry and requires explicit user validation for business logic.

Can I use this scaffolding to add a new source within an existing crowd.dev platform?

Adding a new source within an existing platform is supported, applying the same scaffolding logic to generate transformations, types, migrations, and registration touchpoints.

What's the best way to ensure consistent Snowflake connector integration across multiple platforms?

Automated scaffolding ensures consistent Snowflake connector integration by wiring up touchpoints from data-source discovery through production deployments with standardized types and activity mapping.

Why does Snowflake connector scaffolding require explicit user validation for business logic?

Explicit user validation is required to guarantee accuracy for every piece of business logic, ensuring generated transformations and source queries match the intended data model exactly.