snowflake-create-resource-monitor
SkillDatabases & dataConsult Snowflake CREATE RESOURCE MONITOR parameter reference before generating any CREATE RESOURCE MONITOR DDL.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the snowflake-create-resource-monitor skill
What this skill tells your AI
The instructions your AI receives, as published by gyrus-dev/frosty in skills/snowflake-create-resource-monitor/SKILL.md and read by ahel’s review.
Before writing a CREATE RESOURCE MONITOR statement:
- Read
references/parameters.mdto review all available parameters and their defaults. - For each parameter, decide whether the user's request implies a non-default value.
- Include only the parameters that differ from the default or that the user explicitly requested.
- Never use
CREATE OR REPLACE— always useCREATE RESOURCE MONITOR IF NOT EXISTS. - Always set CREDIT_QUOTA to a concrete number reflecting the intended budget. Always include at least one NOTIFY trigger (e.g., ON 75 PERCENT DO NOTIFY) before any SUSPEND trigger so administrators receive advance warning. Use SUSPEND (not SUSPEND_IMMEDIATE) as the default action unless immediate cancellation of running queries is explicitly required. Always set FREQUENCY and START_TIMESTAMP together — they are interdependent. List only users in NOTIFY_USERS who have verified email addresses, and observe the 5 non-administrator user maximum.
Signals
- GitHub stars
- 77
- Forks
- 9
- Last commit
- Apr 2026
Advanced
- Catalog kind
- skill
- Gateway key
snowflake-create-resource-monitor- Source
- github.com/gyrus-dev/frosty