clickhouse-incident-runbook

A model-agnostic agent-skills platform.

审核状态：已审核Quality 72Security 52

复制安装命令

用 Codex 或 Claude 安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它先审查 Skill 页面再帮你安装。

复制前请先查看来源、License 和安全提示。

项目 README

来源文件：README.md

抓取于 2026年8月28日

Tons of Skills

A model-agnostic agent-skills platform. The canonical layer is harness-free by construction; Claude Code is currently the verified-native harness. Other harnesses remain engineering candidates until their native-path integration is verified; source research alone is never presented as public support.

Version semantics: the release badge is this marketplace's display version. npm packages, including the ccpi CLI and publishable plugins, retain their own package versions; they are intentionally not expected to equal the display version. The version-surface checker governs the display surfaces without rewriting package semver.

Install

Inside Claude Code, one command installs the whole marketplace:

/plugin marketplace add jeremylongshore/claude-code-plugins

Or use the CLI:

pnpm add -g @intentsolutionsio/ccpi
ccpi install devops-automation-pack

Browse the marketplace · Explore plugins · Download bundles

Killer Skill of the Week — no-ai-slop by Peter Yang

Strip AI slop from any draft — named-pattern edits that keep the writer's real voice

no-ai-slop does two jobs and refuses to fake a third. In Edit mode it makes the minimum effective edit — cutting throat-clearing, weak verbs, and abstract nouns while deliberately preserving the writer's cadence, bluntness, humor, and honest admissions, so a rough draft still sounds like the same person afterward. In Detect mode it names each AI-slop pattern it finds, quotes the offending line, and gives the fix in a few words — and pointedly does NOT score the draft or guess whether an AI wrote it. That restraint is the whole point: AI detectors guess; named patterns are evidence the reader can check. MIT-licensed, single focused skill, actively maintained by Peter Yang.

"AI detectors guess. Named patterns are evidence the user can check." — Peter Yang

Grade: A | Week of July 22, 2026 (W30) | View on GitHub

Previous picks: tonone, mnemos, databricks-pack, kobiton-automate, skyvern, code-cleanup, web-analytics, token-optimizer, executive-assistant-skills, skill-creator, cursor-pack, crypto-portfolio-tracker. See all at tonsofskills.com.

Scale, labeled

Every number below names the cohort it counts and the command that reproduces it — an unlabeled count is how a corpus ends up with five contradictory answers to "how many skills."

Count	Cohort	Reproduce with
442	catalog plugins (catalog-entry cohort)	`node scripts/generate-readme-toc.mjs` over `marketplace.extended.json`
3,067	marketplace-visible skills (distinct)	`node -e "import('./scripts/corpus-resolver.mjs').then(m=>console.log(m.resolveCorpus('marketplace-visible').length))"`
347	agent definitions in plugins	`git ls-files 'plugins/*' \| grep '/agents/.\.md'`
19	plugin categories	`ls -d plugins/*/`

📦 Live npm Downloads

Across 396 published packages in the claude-code-plugins namespace. Updated daily by GitHub Actions.

Window	All packages	Established (>30d)
Last 24 hours	962	962
Last 7 days	2,920	2,916
Last 30 days	12,868	12,779

_{"Established" excludes packages first published within the last 30 days, so a bulk-publish event doesn't dominate the headline.}

Top 10 by last 30 days:

#	Package	Last 30d
1	`@intentsolutionsio/openrouter-pack`	556
2	`@intentsolutionsio/groq-pack`	496
3	`@intentsolutionsio/databricks-pack`	274
4	`@intentsolutionsio/clickhouse-pack`	273
5	`@intentsolutionsio/wallet-security-auditor`	263
6	`@intentsolutionsio/notion-pack`	258
7	`@intentsolutionsio/elevenlabs-pack`	244
8	`@intentsolutionsio/freshie-inventory-manager`	214
9	`@intentsolutionsio/supabase-pack`	210
10	`@intentsolutionsio/agency-os`	204

_{Last refreshed 2026-08-19T03:03:05.709Z.}

Ways in

Five real questions, five doors — each resolves to a live, generated surface, never a hand-maintained list:

By category — the table below, regenerated from the catalog on every sync.
By plugin — tonsofskills.com/explore, the full browsable catalog.
By skill — tonsofskills.com/skills, searchable across the whole corpus.
By job to be done — tonsofskills.com/cowork, curated bundles as one-click downloads.
By certification tier — the Certification section below, rendered from the live report.

Browse by category

The 19 categories below link into the live marketplace. Plugin counts are the catalog-entry cohort — regenerated from marketplace.extended.json by this generator; the catalog itself lives on tonsofskills.com, never in this file (§ 6A of the platform blueprint).

	Category	Plugins
🤖	AI & Machine Learning	36
🎭	AI Agents & Agency	10
🔌	API Development	26
💼	Business Tools	6
👥	Community	21
₿	Crypto & Web3	27
💾	Database	26
🎨	Design	2
🔧	DevOps & Infrastructure	36
📚	Examples & Templates	5
🧩	MCP Servers	16
📦	Packages	5
⚡	Performance	25
✅	Productivity	30
🎁	SaaS Skill Packs	106
🔐	Security	27
✨	Skill Enhancers	9
🧪	Testing	28
📁	Analytics	1

What the classes mean

Four artifact classes live in this repository, distinguished on sight and never blurred — provenance is a truth requirement here, not a UX nicety:

Class	What it is	How the reader can tell
Canonical skill	First-party, harness-free, the source of truth	No `.source.json` in its plugin directory
Generated adapter	A thin, machine-produced harness projection	Lives under a generated path with a "generated — do not edit" header
First-party package	An Intent Solutions distribution (npm, cowork zip)	`@intentsolutionsio` scope, IS-authored license
Upstream mirror	Somebody else's work, hosted mirror-by-default	`.source.json` present — upstream author, license, and pinned commit recorded

Certification

Not yet certified. The certification program (tiers T0–T4 with retained, hash-matched evidence) is a later epic of the platform blueprint; until its report exists, no artifact on this surface claims a tier. This line is rendered from the absence of certification-report.json — honestly, not cosmetically.

Contribute

Start with the contribution guide, then the intake and review standards every submission passes through:

Contribution requirements — including the AI-assistance disclosure expectation.
Skill submission intake standard — the tiered document matrix new plugins ship with.
External-PR review standard — how maintainers triage and what gets a submission merged.

Governance

STANDARDS.md — the public spec posture and the canonical-documents index (one owner per fact class).
The platform master blueprint — CI gates, release, docs governance, and this README's own landing contract.
GOVERNANCE.md · SECURITY.md · LICENSE

Provenance

External plugins are hosted mirror-by-default: the contributor's repository stays the source of truth, every mirrored source is pinned in a content lockfile, and upstream credit — author, license, resolved commit — is recorded in the mirror itself. Improvements flow by upstreaming to the author's repository, never by silently editing the mirror. The full decision record is the external-sync model.

License

MIT for the repository scaffolding and first-party tooling; each plugin carries its own license in its manifest, and mirrored plugins keep their upstream license verbatim.

其他

高风险

来源需自行核对维护者身份。
包含脚本或命令调用，安装前请复核。
可能需要外部 token、网络权限或第三方服务。
存在潜在风险命令，请谨慎安装。
扫描发现：3 条。

Codex — Git Clone 安装

安装前请先查看来源仓库和风险报告。
克隆仓库：git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
将 "skills/.curated/clickhouse-incident-runbook" 文件夹复制到 Codex 的 skills 目录中。
重启 Codex 让新的 skill 生效。

Codex — 手动复制安装

安装前请先查看来源仓库和风险报告。
从源仓库下载 SKILL.md 及相关文件。
在 Codex 的 skills 目录中创建新文件夹。
将所有 skill 文件复制到新文件夹中。
重启 Codex 让新的 skill 生效。

Claude Code — Git Clone 安装

安装前请先查看来源仓库和风险报告。
克隆仓库：git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
将 "skills/.curated/clickhouse-incident-runbook" 文件夹复制到 Claude Code 的 skills 目录中。
重启 Claude Code 让新的 skill 生效。

Claude Code — 手动复制安装

安装前请先查看来源仓库和风险报告。
从源仓库下载 SKILL.md 及相关文件。
在 Claude Code 的 skills 目录中创建新文件夹。
将所有 skill 文件复制到新文件夹中。
重启 Claude Code 让新的 skill 生效。

Cursor — Git Clone 安装

安装前请先查看来源仓库和风险报告。
克隆仓库：git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
将 "skills/.curated/clickhouse-incident-runbook" 文件夹复制到 Cursor 的 skills 目录中。
重启 Cursor 让新的 skill 生效。

Cursor — 手动复制安装

安装前请先查看来源仓库和风险报告。
从源仓库下载 SKILL.md 及相关文件。
在 Cursor 的 skills 目录中创建新文件夹。
将所有 skill 文件复制到新文件夹中。
重启 Cursor 让新的 skill 生效。

GitHub Copilot — Git Clone 安装

安装前请先查看来源仓库和风险报告。
克隆仓库：git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
将 "skills/.curated/clickhouse-incident-runbook" 文件夹复制到 GitHub Copilot 的 skills 目录中。
重启 GitHub Copilot 让新的 skill 生效。

GitHub Copilot — 手动复制安装

安装前请先查看来源仓库和风险报告。
从源仓库下载 SKILL.md 及相关文件。
在 GitHub Copilot 的 skills 目录中创建新文件夹。
将所有 skill 文件复制到新文件夹中。
重启 GitHub Copilot 让新的 skill 生效。

Windsurf — Git Clone 安装

安装前请先查看来源仓库和风险报告。
克隆仓库：git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
将 "skills/.curated/clickhouse-incident-runbook" 文件夹复制到 Windsurf 的 skills 目录中。
重启 Windsurf 让新的 skill 生效。

Windsurf — 手动复制安装

安装前请先查看来源仓库和风险报告。
从源仓库下载 SKILL.md 及相关文件。
在 Windsurf 的 skills 目录中创建新文件夹。
将所有 skill 文件复制到新文件夹中。
重启 Windsurf 让新的 skill 生效。

查看 SKILL.md 原文

name: clickhouse-incident-runbook
description: |
  ClickHouse incident response — triage, diagnose, and remediate server issues
  using system tables, kill stuck queries, and execute recovery procedures.
  Use when ClickHouse is slow, unresponsive, OOM-killed, out of disk, backing up
  merges, or producing errors in production and you need an on-call playbook.
  Trigger with "clickhouse incident", "clickhouse outage", "clickhouse down",
  "clickhouse emergency", "clickhouse on-call", "clickhouse broken".
allowed-tools: Read, Bash(kubectl:*), Bash(curl:*)
version: 1.7.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- database
- analytics
- clickhouse
- olap
compatibility: Designed for Claude Code

ClickHouse Incident Runbook

Overview

Step-by-step procedures for triaging and resolving ClickHouse incidents using built-in system tables and SQL commands. Start here: assess severity, run quick triage, walk the decision tree, then jump to the matching remediation procedure.

Prerequisites

Network access to the ClickHouse HTTP interface (default port 8123) or a working clickhouse-client.
A user with rights to read system.* tables and issue KILL QUERY / ALTER.
Shell access to the host or container for P1 restarts (systemctl, docker, or kubectl).

Severity Levels

Level	Definition	Response	Examples
P1	ClickHouse unreachable / all queries failing	< 15 min	Server down, OOM, disk full
P2	Degraded performance / partial failures	< 1 hour	Slow queries, merge backlog
P3	Minor impact / non-critical errors	< 4 hours	Single table issue, warnings
P4	No user impact	Next business day	Monitoring gaps, optimization

Instructions

Work the incident top to bottom: triage, classify with the decision tree, then apply the matching procedure.

1. Quick triage (run first)

# 1. Is ClickHouse alive? (8123 is the default ClickHouse HTTP interface port)
curl -sf 'http://localhost:8123/ping' && echo "UP" || echo "DOWN"

# 2. Can it answer a query?
curl -sf 'http://localhost:8123/?query=SELECT+1' && echo "OK" || echo "QUERY FAILED"

# 3. Check ClickHouse Cloud status
curl -sf 'https://status.clickhouse.cloud' | head -5

-- 4. Server health snapshot (run if server responds)
SELECT
    version()                          AS version,
    formatReadableTimeDelta(uptime())  AS uptime,
    (SELECT count() FROM system.processes) AS running_queries,
    (SELECT value FROM system.metrics WHERE metric = 'MemoryTracking')
        AS memory_bytes,
    (SELECT count() FROM system.merges) AS active_merges;

-- 5. Recent errors
SELECT event_time, exception_code, exception, substring(query, 1, 200) AS q
FROM system.query_log
WHERE type = 'ExceptionWhileProcessing'
  AND event_time >= now() - INTERVAL 10 MINUTE
ORDER BY event_time DESC
LIMIT 10;

2. Decision tree — classify the failure

Server responds to ping?
├─ NO → Check process/container status, disk space, OOM killer logs
│       └─ Container/process dead → Restart, check logs
│       └─ Disk full → Emergency: drop old partitions, expand disk
│       └─ OOM killed → Reduce max_memory_usage, add RAM
└─ YES → Queries succeeding?
    ├─ NO → Check error codes below
    │   └─ Auth errors (516) → Verify credentials, check user exists
    │   └─ Too many queries (202) → Kill stuck queries, reduce concurrency
    │   └─ Memory exceeded (241) → Kill large queries, reduce max_threads
    └─ YES but slow → Performance triage below

3. Apply the matching remediation

Each branch maps to a full procedure (SQL + shell, copy-paste ready) in references/remediation-procedures.md:

P1: Server down / OOM — inspect dmesg/journalctl, restart, verify.
P1: Disk full — find largest tables, drop old partitions, check system.disks.
P2: Stuck queries — inspect system.processes, KILL QUERY by id/user/elapsed.
P2: Too many parts — check part counts, raise parts_to_throw_insert, batch inserts.
P2: Memory pressure — rank by memory_usage, kill the largest, cap max_memory_usage.
P3: Replication lag — inspect system.replicas for queue and replica gaps.

4. Collect evidence and communicate

Once mitigated, export the error window and post status updates. Templates and INTO OUTFILE exports are in references/evidence-and-comms.md.

Output

Working through this runbook produces:

A severity classification (P1–P4) and the identified failure class.
Remediation actions applied — killed query ids, dropped partitions, restarted service, or adjusted settings.
A recovery confirmation (SELECT version() / SELECT 1 succeeds again).
Forensic artifacts for the postmortem: /tmp/incident-queries.json and /tmp/incident-metrics.tsv, plus a filled-in postmortem document.

Error Handling

Symptom	Likely Cause	First Action
All queries fail	Server down	Check process, restart
Inserts fail	Too many parts	`KILL QUERY` long merges, raise limit
Selects slow	Memory pressure	Kill large queries, add filters
Disk alerts	No TTL / no cleanup	Drop old partitions
Replication lag	Network / merge backlog	Check `system.replicas`

If the server does not respond to ping at all, do not keep issuing SQL — move straight to the P1 host-level checks (process, disk, OOM logs) before anything else.

Examples

Kill a runaway query (P2). Triage shows one query pinning memory; classify as "queries succeeding but slow", then from the stuck-query procedure:

KILL QUERY WHERE query_id = 'abc-123-def';

Emergency disk reclaim (P1). Ping fails and the host is out of disk; the disk-full procedure drops the oldest partition to restore writes:

ALTER TABLE analytics.events DROP PARTITION '202301';

Full multi-step walkthroughs for every severity live in references/remediation-procedures.md; the post-incident export and comms templates live in references/evidence-and-comms.md.

Resources

ClickHouse Cloud Status
System Tables Reference
KILL QUERY
Related skill: clickhouse-data-handling for data-compliance follow-up.

发现问题？提交给管理员复核

暂无评论，成为第一个评论者吧！