agentleFS
duyetduyet/clickhouse-monitoring/.claude/skills/ch-version-onboarding/SKILL.md

ch-version-onboarding

Skill303 starsChanged 18 days agoGPL-3.0View on GitHub

Audit chmonitor against a newly released ClickHouse version: detect the newest stable and LTS tags, compare with the newest docs/clickhouse-schemas/v*.md, diff system.columns between the official binaries for every system table the query configs read, EXPLAIN each config's SQL on the new binary, regenerate the support matrix, and file one issue per broken config. Use when a ClickHouse release ships, when a page errors only on a newer server, before bumping the CI ClickHouse pin, or when adding a `since:` variant. Triggers: "new ClickHouse version", "ClickHouse 26.x", "onboard version", "since variant", "system table changed", "column missing on new version", "support matrix", "LTS", "bump CI ClickHouse".

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.