[scope:session] CRON CONFIG CHANGE RULE: Before modifying any cron job's prov...¶
[scope:session] CRON CONFIG CHANGE RULE: Before modifying any cron job's provider, model, schedule, or deliver field, ALWAYS load the cron-tier-provider-architecture skill first and verify the change aligns with the documented tier assignments. No exceptions — even "simple" provider field changes.
[scope:session] CRON CONFIG CHANGE RULE: Before modifying any cron job's provider/model/schedule/deliver, ALWAYS load cron-tier-provider-architecture skill first. Verify against documented tier assignments — no exceptions. Tier 1 (no skills) = gemini-cli. Tier 2 (needs tools) = nvidia.
Related¶
scopesession-CRON-CONFIG-Before-modifying-any-cron-job-providermodelsch¶
[scope:session] CRON CONFIG: Before modifying any cron job provider/model/sch...¶
[scope:session] CRON CONFIG: Before modifying any cron job provider/model/schedule/deliver — ALWAYS load cron-tier-provider-architecture skill first. Tier 1 (no skills) = gemini-cli. Tier 2 (needs tools) = nvidia. No skipping even for "simple" changes.
Related¶
evictedsession-CRON-CONFIG-Before-modifying-any-cron-job-providermodels¶
[evicted:session] CRON CONFIG: Before modifying any cron job provider/model/s...¶
[evicted:session] CRON CONFIG: Before modifying any cron job provider/model/schedule/deliver — ALWAYS load cron-tier-provider-architecture skill first. Tier 1 (no skills) = gemini-cli. Tier 2 (needs tools) = nvidia. No skipping even for "simple" changes.
Related¶
scopesession-CRON-CONFIG-Before-modifying-any-cron-job-providermodelsch¶
[scope:session] CRON CONFIG: Before modifying any cron job provider/model/sch...¶
[scope:session] CRON CONFIG: Before modifying any cron job provider/model/schedule/deliver — ALWAYS load cron-tier-provider-architecture skill first. Tier 1 (no skills) = gemini-cli. Tier 2 (needs tools) = nvidia. No skipping even for "simple" changes.