all publishers

ClickHouse

@clickhouse source repo

29 published skills

  1. ▌
    Loom Session · clickhouse
    Use ONLY when the user asks to restore or save session context: "resume", "restore the context of <branch/session>", "where was I on X", "load the last session", "restore full context", "save this session", "hand this off to a teammate". Lists the saved Loom session briefs, loads the one the user picks (the brief with its compaction summary, or the whole recorded transcript), or saves one. Never load a brief the user did not ask for. NOT for durable facts (loom-memory) and NOT for code questions (loom-code).
    0 installs
  2. ▌
    Loom Optimize · clickhouse bundle
    Use when the user says "optimize my loom namespace", "audit memory", "my memory search is bad", "loom keeps abstaining", or asks why recall over a namespace their agent writes to does not work, or when the mentor's `documents_as_memories` / `checkpoints_as_memory` / `records_for_identities` hint names rows to rework. Runs `namespace.audit`, turns each finding into a plan the owner approves, and reworks the rows with `memory.move` so every old key stays readable through a redirect. Retires nothing. NOT for deciding what to write in the first place (loom-memory) and NOT for client-side failures (loom-status).
    0 installs
  3. ▌
    Improve Loom For My Repo · clickhouse
    Use at the END of a session in which loom's code tools were used, when the user asks to improve loom, report what it got wrong, or asks "why did loom miss that". Harvests THIS session's own transcript — where loom answered, where you fell back to grep or whole-file reads, what you couldn't trust — and turns each gap into a reproducible finding the loom maintainers can act on. First sessions count most. NOT for filing bugs about repos loom doesn't index, and NOT for gaps this session did not actually hit.
    0 installs
  4. ▌
    Loom · clickhouse bundle
    How an agent uses Loom: memory, documents, working state, runs and code intelligence that persist across sessions and are shared with other agents. WHEN: you have a Loom server (LOOM_BASE_URL, an SDK `Agent`, `loom_*` MCP tools) and you start a task, learn a durable fact, hold a document or a large blob, need to resume, hand work to another agent, or answer from what an earlier session knew. Covers MCP, the Python and TypeScript SDKs and plain HTTP.
    0 installs
  5. ▌
    Loom Code · clickhouse
    Route-then-read code intelligence for a loom-indexed repository. WHEN: the repo is indexed by loom (LOOM_BASE_URL set, or a `.loom` marker), and you would otherwise read whole files, grep the tree, or guess who calls a function. Use loom's code.* tools to find the exact unit first, then read only that. FOR SINGLE OPERATIONS: call the code.* MCP tool directly.
    0 installs
  6. ▌
    Loom Code 2 · clickhouse bundle
    Use the moment you are about to grep, glob, or open files to answer a question about a loom-indexed codebase — "where is X", "how does X work", "who calls Y", "is it safe to change Z", "what does this stack trace touch". The tell is linguistic: if you just thought "let me search the codebase", "let me grep for that", or "let me read a few files", that sentence is the trigger — code.grep covers exact literals too. NOT for repos loom hasn't indexed (a code.search that abstains on everything is the tell), and NOT for your own uncommitted files (grep those; pass your diff to code.impact for blast radius).
    0 installs
  7. ▌
    Loom Memory · clickhouse bundle
    Use when you are about to write something to Loom, when the user states, decides or corrects a fact, and at the END of any substantial task before you report done. Decides what is durable memory versus scratchpad, how to write a fact so a future session can trust it, how to read what Loom hands back (persisted or not, conflict, abstain, verified or stale), and how to run the end-of-task memory review. NOT for code questions (loom-code), NOT for "is this already reported?" / duplicate or bisect checks (call loom_search or loom_tracker_duplicate_check directly — nothing to read first) and NOT for filing loom defects (improve-loom-for-my-repo).
    0 installs
  8. ▌
    Loom Mentor · clickhouse bundle
    Use when a loom hint (a tool result's `hint`, an `X-Loom-Hint` header or a "Loom mentor" line) names a plane or op you do not know how to use, or when the user asks "what can loom do", "how should I be using loom", "am I using loom well", "loom mentor". A hint that already names the op to call needs no skill: call it or carry on with the task. Maps a situation to the loom plane and op that fits — code index, tracker record, documents, records, working memory, offload, the entity graph, runs, decisions, procedures, duplicates, conflicts, bisect — and says what to do about each hint code. NOT for deciding the shape of one write (loom-memory), NOT for grep-vs-code.* in an indexed repo (loom-code), NOT for reworking a namespace that already holds the wrong shape (loom-optimize).
    0 installs
  9. ▌
    Loom Status · clickhouse bundle
    Use when Loom seems quiet or wrong: a loom tool answers "unauthenticated", "not available" or an empty result for something the user says was saved; the session-start primer did not appear; the user asks "is loom working", "why didn't it remember", "is my token ok", or a Loom hook says `Executable not found in $PATH: "node"` or `node: not found`, or prints a `loom:` line about Node.js 18+. Checks the Node hook runtime, then runs the plugin's client check and reads its lines, so the answer names the cause (missing runtime, unreachable server, rejected or expired token, no writer grant on the write namespace, plugin or MCP entry missing, stranded captures) and the one fix. NOT for server-side operations (that is `loom doctor` on the server) and NOT for deciding what to remember (loom-memory).
    0 installs
  10. ▌
    Code Review 2 · clickhouse
    Review pull requests for clickhouse-connect. Use this skill for every GitHub Copilot code review.
    1 install
  11. ▌
    Setup 2 · clickhouse
    Guides users through setting up the ClickHouse MCP server connection bundled with this plugin. Use when the user first installs the plugin or has trouble connecting to ClickHouse.
    6 installs
  12. ▌
    Review 2 · clickhouse
    Review a Pull Request for correctness, safety, performance, and compliance. Use when the user wants to review a PR or diff.
    6 installs
  13. ▌
    Review Pr · clickhouse bundle
    Review a numbered GitHub pull request for correctness, API safety, Go idioms, and protocol coverage, then post inline comments plus one updating summary. Use only when the user asks to review an open PR by number. For a local or pre-PR diff, do not use this skill — apply review-core.md in this directory instead.
    2 installs
  14. ▌
    Check CI · clickhouse
    Fetch and report CI results for a silk PR. Use when the user asks to investigate, address, or fix CI failures, or refers to a PR without specifying what's broken.
    5 installs
  15. ▌
    Review · clickhouse
    Review a Pull Request for correctness, safety, performance, and compliance. Use when the user wants to review a PR or diff.
    4 installs
  16. ▌
    Nerve Development · clickhouse
    Nerve backend (Python) and frontend (React/TS) development and code contribution. Use when writing Python code for Nerve, fixing bugs, adding features, reviewing Nerve PRs, building the frontend, running tests, or working with the Nerve codebase. Triggers on "nerve code", "nerve PR", "fix nerve", "nerve feature", "nerve test", "build nerve UI", "nerve migration".
    7 installs
  17. ▌
    Nerve Workspace Config · clickhouse
    Change your own configuration — skills, cron jobs, sources, and settings that live in the workspace. Covers both routes: a pull request when the workspace is a shared config repo (and the only route when this instance is locked), or a direct edit when the workspace is purely local. Use when asked to add/edit/remove a cron job, create or change a skill, adjust settings, or "change your config". Triggers on "add a cron", "change your schedule", "edit your config", "update settings", "propose a config change".
    6 installs
  18. ▌
    Code Review · clickhouse
    Review changes in clickhouse-java for correctness, compatibility, API stability, and missing tests. Use when reviewing pull requests, commits, diffs, patches, or when the user asks for a code review.
    5 installs
  19. ▌
    Triage Issues · clickhouse bundle
    Analyzes a single GitHub issue at a time. Reads the description, defines labels and priority, researches additional information, and provides a short but detailed report. Use when the user asks to triage an issue, analyze a bug report, or categorize a GitHub issue.
    6 installs
  20. ▌
    Write Doc Examples · clickhouse
    Write, rewrite, and format documentation code snippets into reusable, production-ready methods with necessary library imports and clean linting. Use when writing, updating, or formatting Java code examples in integration guides and documentation (such as docs/integration-client.md or docs/integration-jdbc.md).
    8 installs
  21. ▌
    Update Keyword Engine Lists · clickhouse
    Update ALLOWED_KEYWORD_ALIASES in ClickHouseSqlUtils.java and ENGINE_TO_TABLE_TYPE in DatabaseMetaDataImpl.java from failing test output. Use when StatementSQLTest.testAllowedKeywordAliasesMatchSystemKeywords or DatabaseMetaDataTest.testAllTableEnginesFromSystemTableEnginesAreMapped fails.
    8 installs
  22. ▌
    Setup · clickhouse
    Set up the `clickhouse-js` repository in a fresh checkout so the agent can run tests, lints, type checks, builds, or examples. Use this skill before invoking any `npm run test:*`, `npm run lint`, `npm run typecheck`, `npm run build`, or `npm run run-examples` script — or after pulling changes that touch any `package.json` (root, `examples/node`, or `examples/web`). Covers Node.js version requirements, installing dependencies across the npm workspaces and the two independent example packages, building the workspace packages so inter-package imports resolve, and starting ClickHouse via Docker Compose for integration tests. Do NOT use this skill for downstream user projects that merely depend on `@clickhouse/client` or `@clickhouse/client-web`; it is specific to contributing to the `ClickHouse/clickhouse-js` repo itself.
    7 installs
  23. ▌
    Release · clickhouse
    Drive a package release of `ClickHouse/clickhouse-js` end to end: bump the version, sync the protected `release` branch from `main`, watch the npm publish (which is gated by a manual approval on the `npm-publish` environment), and create the GitHub Release from the CHANGELOG. Use this skill whenever the task is to "release", "cut a release", "publish a new version", or "ship" one of the packages: `@clickhouse/client` (Node.js), `@clickhouse/client-web` (Web), `@clickhouse/client-common` (deprecated, rarely released), the standalone `@clickhouse/datatype-parser` (the type parser, under `packages/datatype-parser`), or `@clickhouse/rowbinary` (the RowBinary codec skill/package, under `skills/clickhouse-js-node-rowbinary`). The agent drives the GitHub Actions workflows (`gh workflow run`), watches CI, pauses at the human-judgment points (PR review, the approval gate, GitHub Release text), and hands the deployment-approval link back to the human. Do NOT use this for fixing a failing release PR — that is the `fix-r
    7 installs
  24. ▌
    Fix Release Pr · clickhouse
    Fix CI failures and address code-review comments on a pull request that targets the protected `release` branch of `ClickHouse/clickhouse-js`. Release PRs are snapshots of `main` (their head branch is usually `main` itself) and cannot be edited directly — branch protection blocks pushing fixes onto them. Use this skill whenever the work is "fix the CI / address the review comments on PR #N" and that PR's base branch is `release`: it routes the fix through a separate PR to `main`, then closes the loop on the original release PR by replying to and resolving the review threads. Triggers on phrasing like "fix this release PR", "the release PR is failing CI", "address the review comments but it's a release branch", or after checking out a PR whose base is `release`. Do NOT use this for ordinary feature/fix PRs that target `main` — for those, just push to the PR's own branch.
    5 installs
  25. ▌
    Typescript Lsp · clickhouse
    Use the TypeScript language server (`typescript-language-server`) for precise code intelligence in the `clickhouse-js` repository: go-to-definition, find references, hover (type signatures and JSDoc, including `@deprecated` info), workspace-wide symbol search, completions, and per-file type diagnostics. Prefer this over grep when you need to resolve a symbol's actual definition, find all usages of an exported API, or inspect inferred types across the `packages/*` workspaces. The server is preinstalled as a root devDependency — run the repository `setup` skill (`npm install`) first so `node_modules` is populated. Do NOT use this skill for downstream projects that merely depend on `@clickhouse/client`; it is specific to working inside this repo.
    8 installs
  26. ▌
    Clickstack Otel Collector · clickhouse bundle
    Use when a user wants to wire an OpenTelemetry collector into a Managed ClickStack service on ClickHouse Cloud, either by deploying a new local collector (Docker run or Docker Compose) or by configuring their own existing collector, then send rich synthetic telemetry and verify it is visible in ClickStack.
    6 installs
  27. ▌
    Infra Clickhouse · clickhouse bundle
    Sets up and manages ClickHouse using the clickhousectl CLI — installs and runs a local ClickHouse server for development, and creates managed ClickHouse Cloud services for production (authentication, service creation, schema migration, application connection). Use when the user wants to build an application with ClickHouse, set up a local ClickHouse dev environment, create tables and start querying, deploy ClickHouse to production or ClickHouse Cloud, or migrate from a local setup to the cloud.
    7 installs
  28. ▌
    Infra Postgres · clickhouse bundle
    Sets up and manages Postgres using the clickhousectl CLI — runs a local Docker-backed Postgres for development, and creates and operates managed ClickHouse Cloud Postgres services (connections, TLS, runtime config, read replicas, failover, point-in-time restore). Use when the user wants a Postgres or PostgreSQL database for their application, a local Postgres dev environment, psql access, or a managed/production Postgres in ClickHouse Cloud, or mentions moving a local Postgres to production.
    7 installs
  29. ▌
    Clickhouse Best Practices · clickhouse
    MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 28 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.
    10 installs