scaffold-snowflake-connector

Scaffold Snowflake connector boilerplate for new crowd.dev data sources.

3.4k|728|Updated Jun 28, 2022

Search Tags:#integration #scaffold #codegen #connector #snowflake #crowd.dev

Ready to run

npx skills add https://github.com/linuxfoundation/crowd.dev --skill scaffold-snowflake-connector

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scaffold-snowflake-connector
Source: https://github.com/linuxfoundation/crowd.dev/tree/main/.claude/skills/scaffold-snowflake-connector
Command: npx skills add https://github.com/linuxfoundation/crowd.dev --skill scaffold-snowflake-connector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill scaffolds all code scaffolding required to add a new snowflake-connector data source to crowd.dev, including platform/source boilerplate, buildSourceQuery, transformer, activity types, migrations, and type registrations.

Core Features & Use Cases

Scaffolds all touch points for a new snowflake-connector data source, one platform/source per run.
Generates boilerplate for type definitions, migrations, and integration wiring to ensure zero-assumption practices and explicit validation before writing any file.
Works with the crowd.dev architecture to produce consistent code structure for new platform-source combinations.

Quick Start

Provide the platform name and source name, then run the scaffold to generate all required Snowflake connector files for the new data source.

Frequently Asked Questions about scaffold-snowflake-connector

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

FAQPage Schema

How do I scaffold a new Snowflake connector data source for crowd.dev?▼

Scaffolding a Snowflake connector data source for crowd.dev requires providing the platform name and source name to generate boilerplate files, including buildSourceQuery, transformer, activity types, migrations, and type registrations across multiple touch points with explicit user validation.

What boilerplate files are needed to add a Snowflake connector to crowd.dev?▼

Adding a Snowflake connector to crowd.dev requires boilerplate files for buildSourceQuery, transformers, activity types, migrations, type definitions, and integration wiring. The scaffold generates these files across multiple touch points while following existing platform conventions to ensure structural consistency.

Can I scaffold multiple platforms or sources in a single Snowflake connector run?▼

No, the Snowflake connector scaffold manages exactly one platform and one source per run. This limitation enforces zero-assumption practices and explicit user validation before writing any file, ensuring structural consistency across the crowd.dev architecture.

What inputs are required to generate Snowflake connector boilerplate code?▼

Generating Snowflake connector boilerplate requires two explicit inputs: the platform name and the source name. These values drive the scaffolding of type definitions, migrations, integration wiring, and transformer functions while following existing crowd.dev platform conventions.

How does code generation ensure consistency for new crowd.dev data sources?▼

Code generation ensures consistency for new crowd.dev data sources by following existing platform conventions and producing a uniform code structure for new platform-source combinations. The scaffold applies zero-assumption practices with explicit validation before writing any boilerplate files.