| name | solutions-installer |
| id | solutions-installer |
| title | Install Snowflake Solutions |
| summary | Install pre-built industry solutions into your Snowflake account from the sf-solutions repository. |
| description | Use for ALL requests to install, set up, deploy, or tear down a pre-built Snowflake industry solution. This skill reads a solution's manifest.json for metadata, then executes its setup SQL scripts against the user's Snowflake account. Triggers: install solution, coco solutions install, set up solution, deploy solution, teardown solution, uninstall solution, sf-solutions, solution accelerator, demo environment. Do NOT use for: adding pages to the solutions catalog website (use snowflake-solutions-catalog instead), building custom solutions from scratch, or general SQL authoring. |
| tools | ["snowflake_sql_execute","snowflake_object_search","Bash","Read","Write","Glob","Grep","WebFetch"] |
| prompt | $solutions-installer <solution-name> |
| language | en |
| status | beta |
| authors | Sho Tanaka |
| type | snowflake |
| categories | solutions, demo, installer |
Install Snowflake Industry Solutions
Installs a pre-built industry solution from the sf-solutions repository into the user's Snowflake account. Each solution contains a manifest.json describing its metadata and a scripts/ directory with SQL setup/teardown files.
When to Use
- User wants to install a solution:
$solutions-installer <solution-name> where <solution-name> is a directory name in the sf-solutions repository (e.g., manufacturing-predictive-maintenance)
- User wants to tear down / uninstall a solution
- User wants to set up a demo environment for an industry use case
- Do NOT use for editing the solutions catalog website
What This Skill Provides
- Clones or locates the sf-solutions repository
- Reads the solution's
manifest.json to understand what will be created
- Executes
install_scripts (setup SQL) against the user's Snowflake account
- Supports teardown via
teardown_scripts
- Verifies the installation by checking created objects
Solution Directory Convention
Each solution follows this structure:
<solution-slug>/
├── manifest.json # REQUIRED: solution metadata (see schema below)
├── README.md # Solution overview, architecture, prerequisites
└── scripts/
├── setup.sql # Main installation script
└── teardown.sql # Cleanup script (drops all created objects)
manifest.json Schema
{
"name": "solution-slug",
"display_name": "Human-Readable Solution Name",
"version": "1.0.0",
"industry": "Manufacturing",
"source"
