cloud-saas-mode

Manage dual-product behavior across chmonitor Cloud SaaS and self-hosted editions.

255|42|Updated Nov 16, 2023
One-click install
npx skills add https://github.com/chmonitor/chmonitor --skill cloud-saas-mode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cloud-saas-mode
Source: https://github.com/chmonitor/chmonitor/tree/main/.claude/skills/cloud-saas-mode
Command: npx skills add https://github.com/chmonitor/chmonitor --skill cloud-saas-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of maintaining consistent, drift-free functionality across chmonitor's Cloud SaaS offering and self-hosted open-source edition, which share a single codebase but have distinct runtime behaviors for hosts, user access, and onboarding flows.

Core Features & Use Cases

  • Cloud Mode Flag Management: Configure and validate the runtime flag that toggles between SaaS and self-hosted behavior, ensuring fail-closed defaults that never break core self-hosted monitoring features.
  • User Flow Configuration: Manage welcome/setup onboarding pages, demo host visibility for anonymous vs signed-in users, and per-user ClickHouse connection storage for SaaS deployments.
  • Connection Error Handling: Implement and update the connection error classifier that provides user-friendly error messages and linked documentation for common connection issues like invalid credentials, DNS failures, or TLS errors.
  • Use Case Example: When adding a new connection error type for expired ClickHouse API keys, use this skill to follow the existing classification pattern, update the error docs link, and ensure the change does not affect self-hosted deployments.

Quick Start

Use the cloud-saas-mode skill to update the welcome page to show a new onboarding step for SaaS users connecting their first ClickHouse host, following the existing variant logic for signed-in and anonymous users.

Frequently Asked Questions about cloud-saas-mode

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

FAQPage Schema
How do I manage cloud mode flags for a dual SaaS and self-hosted codebase without breaking open-source features?▼

Cloud mode flag management configures the runtime toggle between SaaS and self-hosted behavior using fail-closed defaults, ensuring self-hosted core monitoring functionality remains unmodified when cloud-specific features are updated.

How do I add a new ClickHouse connection error type for invalid credentials or TLS failures?▼

Connection error handling implements a classifier providing user-friendly error messages and linked documentation for common connection issues like invalid credentials, DNS failures, or TLS errors, following existing classification patterns without affecting self-hosted deployments.

How do I configure onboarding flow visibility for demo hosts with anonymous versus signed-in users?▼

User flow configuration manages welcome and setup onboarding pages alongside demo host visibility rules, applying variant logic to differentiate what anonymous versus signed-in users see during the SaaS onboarding experience.

How does per-user database connection storage work for SaaS deployments?▼

Per-user ClickHouse connection storage manages individual database connections for SaaS deployments, allowing each user to configure and access their own ClickHouse hosts through the cloud-mode interface.

Can I update SaaS onboarding pages to add new setup steps for connecting a first ClickHouse host?▼

Updating the welcome page to show new onboarding steps for SaaS users connecting their first ClickHouse host follows existing variant logic for signed-in and anonymous users, maintaining consistent behavior across both deployment models.

Why do connection errors need classification when adding cloud-specific features to a shared codebase?▼

Connection error classification provides user-friendly messages and documentation links for issues like expired ClickHouse API keys, ensuring consistent error handling patterns that do not affect self-hosted deployments when cloud features are added.