clickhouse-monitor

Plugin clickhouse-monitor in chmonitor/chmonitor. Commands read from the repo's manifest — today.

Skills (113)

• anomaly-detection

  Detect cluster abnormalities by comparing recent activity (last 1h) to a baseline (preceding 24h) using the raw query tool.

• build-agent

  Build an AI-agent application end-to-end — from an empty repo or an existing codebase. Use when the user wants to "build an agent", "scaffold an agent app", "add an agent API", "build an agent UI/chat", "pick an agent framework", or set up tool calling, tracing, or an AI gateway. Interviews the user

• clickhouse-best-practices

  Production operational practices: insert batching, async writes, query cache, connection pooling, and recommended settings.

• cluster-operations

  Cluster management: distributed tables, ON CLUSTER DDL, node lifecycle, resharding, load balancing, and Keeper migration.

• concept-explainer

  Explains core ClickHouse concepts with accurate mental models — MergeTree, indexes, replication, sharding, and special engines.

• data-analysis

  Analyze cluster data and metrics using raw SQL recipes against system.query_log and system.parts when no dedicated tool exists.

• embedded-captions

  Add captions to a talking-head video. ONE catalog (CATALOG.md) of 32 visual identities behind two engines: column-flow (captions composited INTO the scene — matte occlusion + mix-blend; cream/ink/editorial/keynote/documentary/loud/neon/glitch/chrome/velocity) and themed constitutions (anchor/ordnanc

• faceless-explainer

  turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video, up to ~3 min (sweet spot 30-90s), where every visual is invented (typography, abstract graphics, diagrams, data-viz) rather than captured. There is no URL, no website capture, and no real assets. Use this sk

• general-video

  The fallback workflow for authoring custom HyperFrames video compositions at any length or format — longer or multi-scene pieces, brand / sizzle reels, montages, title cards, static loops, and freeform compositions. Input- and length-agnostic. If a specialized workflow clearly fits the input — a mar

• hardware-tuning

  Detect server cores/RAM/disk from system tables, then recommend ClickHouse settings sized to that hardware.

• hyperframes-animation

  All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animatio

• hyperframes-cli

  HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, tts, or remove-background, or when

• hyperframes-core

  The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.

• hyperframes-creative

  Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-a

• hyperframes-media

  Audio and media assets for HyperFrames compositions, produced by one shared audio engine (`scripts/audio.mjs`) — multi-provider TTS (HeyGen / ElevenLabs / Kokoro local), background music + sound effects (HeyGen audio-library retrieval by default, with local Lyria / MusicGen BGM generation and a bund

• hyperframes-registry

  Install and wire registry blocks and components into HyperFrames compositions. Use when running hyperframes add, installing a block or component, wiring an installed item into index.html, or working with hyperframes.json. Covers the add command, install locations, block sub-composition wiring, compo

• hyperframes

  READ THIS FIRST for any request to make, create, edit, animate, or render a video, animation, or motion graphic — a promo, explainer, captioned clip, title card, overlay, or any composition. HyperFrames renders video from HTML; this is the entry skill and the default way an agent authors or edits vi

• incident-response

  Structured triage recipes for common ClickHouse incidents: disk, errors, replication, mutations, cluster health, and slow queries.

• media-use

  Agent Media OS — resolve any media need (BGM, SFX, image, icon) into a frozen local file + ledger record. One verb (`resolve`) handles the full cascade — project cache, global cache, HeyGen catalog search, freeze, register. Keeps search noise on disk, hands the agent a path. Use when a composition n

• migration-patterns

  Schema migrations: ALTER patterns, engine changes, zero-downtime swaps, clickhouse-local offline migrations, lightweight UPDATE/DELETE strategies, and Postgres→ClickHouse migration planning (type mapping, schema pitfalls, PeerDB CDC, validation, schema introspection).

• motion-graphics

  Use when the user wants a short, design-led motion graphic where motion is the message: kinetic typography, stat or number count-up, chart/data-viz hit, logo sting, brand lockup, lower-third, callout, social overlay, animated headline/tweet/news item, motion poster, or quick captured-page highlight.

• music-to-video

  Use when the user has a music track (an audio file, or a video to pull audio from) and wants a beat-synced HyperFrames video, calm to hard-hitting. The music drives everything: one analyzer reads it once, the orchestrator lays out the frames and fills a per-frame plan, and one sub-agent builds each

• optimization-plan

  Build and present a ranked, recommend-only ClickHouse optimization plan from the findings the advisors already stored: unread tables, unused projections, detached parts, TTL rewrite and OPTIMIZE-on-unchanged-data merge cost, retention, schema suggestions. Load for optimization plan, what to optimize

• plan-and-verify

  Decompose multi-step tasks into an explicit update_plan checklist, then verify each result before stating it as fact.

• polar-integration

  Add Polar billing to a TypeScript/JavaScript app using the @polar-sh/sdk package. Use this skill whenever the user wants to add a Checkout endpoint, a Customer Portal endpoint, or a Webhooks endpoint for Polar to any framework — Next.js, Express, Hono, Astro, SvelteKit, Remix, TanStack Start, Nuxt,

• polar-migration

  Guide for migrating to Polar from other payment platforms (Stripe Billing, Paddle, Lemon Squeezy, Gumroad). Use this skill when: (1) Planning a migration from another payment provider to Polar; (2) Migrating customer data and subscriptions; (3) Running parallel systems during transition; (4) Mapping

• polar-testing

  Guide for testing Polar payment integrations using the sandbox environment. Use this skill when: (1) Setting up the Polar sandbox for development; (2) Testing checkout flows without real payments; (3) Using Stripe test cards with Polar; (4) Writing integration tests for payment flows; (5) Testing we

• pr-to-video

  turn a GitHub pull request (a PR URL like github.com/<owner>/<repo>/pull/<N>, an <owner>/<repo>#<N> ref, or 'this PR' in a checked-out repo) into a code-change explainer video, up to ~3 min (sweet spot 30-90s) — changelog, feature reveal, fix, or refactor walkthrough, rendered from the diff / commit

• product-launch-video

  turn a product or marketing URL, pasted script, or brief into a product launch video, including SaaS promos, feature reveals, app launches, company promos, and product marketing videos. Use this skill when the user wants to market, launch, promote, or reveal a product. Do not use it for general non-

• query-optimization

  Advanced query tuning: join algorithms, skip index selection, EXPLAIN interpretation, ProfileEvents profiling, and optimizer settings. Also the autonomous diagnose-loop for open-ended questions like why is my database slow?

• query-tuning-advisor

  Diagnose a slow or expensive query with EXPLAIN and query_log, then propose concrete rewrites and better join strategies.

• remotion-to-hyperframes

  Port an existing Remotion (React) composition to HyperFrames HTML. Use ONLY when the user explicitly asks to port/convert/migrate/translate a Remotion source. Do NOT use: (a) authoring a new HyperFrames composition; (b) Remotion mentioned in passing; (c) Remotion code shared as reference only; (d) "

• replication-guide

  ReplicatedMergeTree operations, failover procedures, lag diagnosis, quorum writes, and Keeper management.

• schema-design-advisor

  Recommend table ORDER BY keys, partition strategies, column data-type right-sizing, codecs, skip indexes, and projections for ClickHouse tables.

• security-hardening

  RBAC configuration, row policies, quotas, network security, audit logging, and access control best practices.

• seo-audit

  When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "s

• settings-audit

  Read-only audit of ClickHouse settings: lists changed settings in system.settings, system.merge_tree_settings and system.server_settings, flags Experimental, Beta and Obsolete ones in use, explains each from its description, and recommends (never applies) changes. Load for audit settings, experiment

• setup-polar

  Interactive onboarding wizard to set up Polar payment integration from scratch. Use this skill when: (1) User wants to "set up Polar" or "integrate Polar" in their project; (2) User is starting fresh with Polar and needs guided setup; (3) User asks "how do I get started with Polar"; (4) User wants t

• slideshow

  Author a HyperFrames slideshow composition — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching sequences, and hotspot navigation. Use as an intent check when the user asks for a presentation, pitch deck, slide deck, interactive deck, or page-to-deck co

• storage-optimization

  Compression codecs, TTL policies, tiered storage, part management, and disk space optimization.

• system-tables-reference

  Exact column names for the system tables the agent queries most (processes, query_log, parts, merges, mutations, replicas, replication_queue, disks, settings, zookeeper, users/grants, metrics) plus rules for choosing dedicated tools over raw SQL. Load before hand-writing SQL against system tables.

• talking-head-recut

  Package an existing talking-head / interview / podcast video by layering timed, designed GRAPHIC OVERLAY cards onto the playing video — titles, lower-thirds, data callouts, quotes, side panels, picture-in-picture — synced to the transcript. The source video plays in full; the agent designs and write

• troubleshooting

  Diagnose and resolve ClickHouse issues: OOM, slow merges, stuck mutations, query failures with error codes, and systematic error clustering.

• version-upgrade-advisor

  Advises whether and how to upgrade ClickHouse — versioning scheme, upgrade path, what you gain, pre/post-upgrade checklist.

• website-to-video

  Capture a general website/URL and turn it into a HyperFrames video (site tour, showcase, or social clip from the site's own visuals). Uses headless Chrome screenshots + brand assets. Use when intent is general — portfolio/blog/landing-page showcase or social clip from the site. NOT for: product/SaaS

• api-self-audit

  Hunt for chmonitor API routes that ship without an auth guard, and triage each one: guard it, or allowlist it with a reason. Use when adding or changing a route under apps/dashboard/src/routes/api/, when auth-guard-coverage.test.ts fails, when allowlisting a public route in PUBLIC_ROUTES, or when re

• ch-version-onboarding

  Audit chmonitor against a new ClickHouse release: diff system.columns between official binaries, EXPLAIN every query config on the new version, regenerate the support matrix, file one issue per broken config. Use when a ClickHouse release ships, a page errors only on a newer server, before bumping t

• clickhouse-query-config

  Version-aware ClickHouse query configs. Use when adding or changing a QueryConfig in apps/dashboard/src/lib/query-config/, adding a BackgroundBar column, or fixing a query that fails on one ClickHouse version.

• cloud-saas-mode

  Cloud (dash.chmonitor.dev) vs self-hosted behaviour in chmonitor's one codebase. Use when changing the cloud-mode flag, demo hosts, what anonymous vs signed-in users see, the welcome/setup page, per-user (D1) connections, the "Test connection" error classifier, the sample ClickHouse preset, guest AI

• product-design

  chmonitor's design system and UX conventions. Use before building or reviewing any dashboard UI: a page, chart, card, dialog, table, badge, loading/empty/error state, settings or alert surface, sidebar or menu entry, hub page, command palette, What's new, Schema Compare, or Advisor. Covers tokens, s

• pstack

  Project-local pstack validation router for chmonitor. Use when proving a dashboard, API, auth or security, PeerDB, alerts and webhooks, Helm and GitOps, deployment, or CLI change. Prefer CI checks and capture observable evidence instead of running heavy local builds.

• architect

  Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

• arena

  Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.

• automate-me

  Use for \"automate me\", \"create/update/refresh my -mode skill\", \"turn/capture my preferences or working style into a skill\", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via plugin-dev:skill-development + unslop, optionally pulling fresh evidence from

• babysit

  Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.

• blast-radius

  Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something a

• bro

  Restate the last message in plain human language, with no jargon. Use for /bro or when asked to say it plainly.

• create-verification-skill

  Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, \"make a control skill for this repo\", \"make a driver skill for this repo\", or when a project has no scripted way to prove UI/CLI/servic

• deslop

  Remove AI-generated code slop and clean up code style

• figure-it-out

  Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migrati

• fix-ci

  Find failing PR checks, inspect logs or external check links, and apply focused fixes

• fix-merge-conflicts

  Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution

• get-pr-comments

  Fetch and summarize review comments from the active pull request

• how

  Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motiva

• interrogate

  Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.

• maintain-verification-skill

  Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or \"audit the verify skill\".

• make-pr-easy-to-review

  Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".

• no-comments

  Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.

• poteto-mode

  poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

• principle-attack-the-premise

  Apply when repeated fixes sharing an assumption fail. State the assumption and choose an observation that can challenge it before trying another fix that depends on it.

• principle-boundary-discipline

  Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

• principle-build-the-lever

  Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.

• principle-encode-lessons-in-structure

  Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.

• principle-exhaust-the-design-space

  Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

• principle-experience-first

  Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

• principle-fix-root-causes

  Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.

• principle-foundational-thinking

  Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.

• principle-guard-the-context-window

  Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.

• principle-laziness-protocol

  Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

• principle-make-operations-idempotent

  Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

• principle-migrate-callers-then-delete-legacy-apis
• principle-minimize-reader-load
• principle-model-the-domain
• principle-never-block-on-the-human
• principle-outcome-oriented-execution
• principle-prove-it-works
• principle-redesign-from-first-principles
• principle-separate-before-serializing-shared-state
• principle-sequence-verifiable-units
• principle-subtract-before-you-add
• principle-test-behavior-not-implementation
• principle-type-system-discipline
• recall
• reflect
• setup-pstack
• show-me-your-work
• swarm
• tdd
• teach
• technical-writing
• thermo-nuclear-code-quality-review
• typescript-best-practices
• unslop
• what-did-i-get-done
• why
• release-screenshots
• ui-ux-audit
• verify-agent-tool-gates
• verify-agent
• verify-production
• verify-query-attribution
• verify-release
• verify-chmonitor

MCP servers (1)

• shadcn

  runs: npx shadcn@latest mcp

Similar plugins