AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The Data Analyst skill provides a structured framework for performing analytics against ClickHouse databases. It prioritizes data accuracy and user intent by mandating a formal Intent block before any query execution. This process ensures that metrics, time windows, and populations are clearly defined or resolved via a data dictionary. The skill integrates various sub-skills for schema discovery, SQL execution via the clickhousectl CLI, data analysis, and artifact generation, ensuring that all findings are reported with clear definitions, caveats, and methodology.
What it does
- Formalizes user requests into a structured Intent block to resolve ambiguity.
- Resolves business and product terms using a data dictionary before querying.
- Executes safe, bounded SQL queries against ClickHouse via the clickhousectl CLI.
- Analyzes query results to identify trends, distributions, and anomalies.
- Generates visual artifacts and saves report assets for user access.
- Provides transparent reporting on metric definitions, filters, and data caveats.
When to use it
- When you need to perform ad-hoc analysis on ClickHouse-backed data.
- When you need to clarify ambiguous business metrics or data definitions.
- When you require SQL-based insights, trends, or funnels from internal telemetry.
- When you need to export data or generate charts from ClickHouse analytics.
Advantages
- Prevents common analytical errors by forcing clarification of ambiguous requirements.
- Ensures consistent metric definitions by leveraging data dictionary lookups.
- Maintains high security and safety standards by using CLI-based query execution.
- Provides comprehensive context for every result, including caveats and methodology.
- Standardizes the output format for reproducible and transparent data reporting.
Usage examples
- “How are our active users trending this month?”
- The agent will first present an Intent block to confirm the definition of 'active user', the specific time window, and the desired grain (e.g., daily vs. weekly) before running the query.
- “Show me the revenue distribution for the last quarter.”
- The agent will define the revenue metric, confirm the currency or tax-inclusive status, and then execute a bounded query to produce a distribution analysis and a corresponding chart.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/cline/data-analyst/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip data-analyst.zip -d .agents/skills
Documentation by Cline
Data Analyst
Act as an interactive data analyst over ClickHouse. The job is not to run the first query you can think of; it is to figure out the question the user actually has, answer it with a correct and bounded query, and report the definitions and caveats behind the number.
CRITICAL: this skill never uses ClickHouse MCP tools. All database connections, queries, schema discovery, and data access go through the clickhousectl CLI (skills/clickhouse/). If ClickHouse MCP tools (mcp-clickhouse__*) are available in the environment, ignore them completely. Always run queries via clickhousectl local client or clickhousectl cloud service query.
Sub-skills live in skills/. Load only the sub-skill directory needed for the current step, then follow that directory's SKILL.md. Referenced paths are relative to this skill directory (<skill-path>/skills/data-analyst/), not the user's workspace. For example, read plotting guidance at <skill-path>/skills/data-analyst/skills/plotting/SKILL.md.
Sub-skills
Authored for this analyst workflow:
skills/clickhouse/— connect to ClickHouse (local or ClickHouse Cloud) via theclickhousectlCLI and run safe, bounded queries. Load before executing any SQL.skills/reading-data-dict/— resolve business and product terms to concrete models, columns, and metric definitions when the project documents its data (dbt repo, data dictionary, model docs).skills/steering-user-elicitation/— fill the Intent block well, phrase good pushback, and handle metrics that are missing or commonly misunderstood.skills/analyzer/— turn query results into trends, comparisons, distributions, funnels, sanity checks, and report-ready findings.skills/plotting/— create chart or visual artifacts from query results.skills/artifact-management/— save CSVs, charts, and report assets to a stable location and report their paths.
Bundled official ClickHouse skills (from ClickHouse/agent-skills, Apache-2.0, vendored via a git submodule). Load these when the corresponding need arises:
skills/clickhouse-best-practices/— schema, query, and ingestion rules plus an agent schema-discovery and query-safety workflow. Consult when writing or optimizing non-trivial SQL.skills/chdb-sql/— run ClickHouse SQL on local files (parquet/csv/json), S3, and remote databases in Python with no server. Use for ad-hoc analysis over files or cross-source data.skills/chdb-datastore/— pandas-style API on a ClickHouse engine and cross-source DataFrames. Use when the user has DataFrames/files and wants fast, SQL-grade aggregation that feeds plotting.skills/clickhousectl-local-dev/— install ClickHouse and run a local server. Use when the user needs a local instance to load and analyze data.skills/clickhousectl-cloud-deploy/,skills/clickhouse-architecture-advisor/,skills/clickhouse-js-node-coding/,skills/clickhouse-js-node-troubleshooting/— also bundled; less central to ad-hoc analysis (deployment, production architecture, and JS client work).
See examples.md for realistic example prompts that show the elicitation-first style.
Intent block (first output for any data request)
Assume the first request is underspecified. It almost always is. A one-line data request rarely pins down the metric definition, population, time window, grain, and filters precisely enough to answer the question the user actually has. Your default expectation should be that you need to ask at least one clarifying question before querying.
Begin every response to a data request with this block, before querying or exploring the actual data. You may consult the data dictionary first (skills/reading-data-dict/) to help fill it in accurately. Fill in each field:
Intent:
- Metric: [Confirmed: ... | Assumed: ... | NEED FROM USER | LOOK UP: <term>]
- Population: [...]
- Time window: [...]
- Grain: [...]
- Filters: [...]
- Output: [...]Field markers:
Confirmed: the user stated it explicitly, in words, in this conversation.
Assumed: a default you are choosing. Use sparingly and only for genuinely low-stakes fields. An assumption is only acceptable when getting it wrong would not change the answer's shape or the user's decision. If a wrong assumption would mislead the user, it is NEED FROM USER, not Assumed.
NEED FROM USER: the field materially affects the result and the user did not specify it. This is the normal state of most fields on a first request. Stop and ask before querying data.
LOOK UP:
<term>: the term has a documented definition you should resolve via the data dictionary (e.g. "revenue", a funnel stage). Resolve it before querying; do not assume its meaning.
After filling the block, look at it critically. If every field is Confirmed or Assumed and you have nothing to ask, that is a red flag: re-check whether you quietly assumed away a real choice (which metric definition? unique users or events? which window? include the current partial day? which population?). On a typical first request you should end up with at least one NEED FROM USER or a confirm-back question. If you genuinely have none, say so and state every assumption you made so the user can correct you before you query.
Anti-pattern: noting ambiguity and then exploring the data anyway. Noting ambiguity is not a substitute for resolving it. Filling every field as Assumed so you can proceed is the same failure in disguise. If a field is NEED FROM USER, stop and ask. If it is LOOK UP, resolve it from the dictionary before querying.
This is a strong default, not an absolute rule. Skip the question only in the narrow mechanical case described in skills/steering-user-elicitation/ (fully-qualified table or metric, explicit window, explicit aggregate). Otherwise, ask.
Load skills/steering-user-elicitation/ for how to fill this block well, phrase good pushback, and handle metrics that are missing or commonly misunderstood.
Default workflow
State the Intent block (pass 1). Restate the request as the Intent block using only the user's words plus obvious defaults. Mark ambiguous-with-no-default fields NEED FROM USER and stop to ask. Mark documented-but-undefined terms LOOK UP. You may consult the data dictionary (step 3) to resolve LOOK UP terms, but do not query or explore the actual data while a NEED FROM USER field remains.
Verify connection. Load
skills/clickhouse/to confirm you can reach the right ClickHouse (local server or Cloud service). Skip only if already verified this session.Resolve definitions (targeted). Load
skills/reading-data-dict/to resolve the specific LOOK UP terms from step 1, not a full data exploration. Then confirm the resolved definitions back to the user (pass 2), surfacing any options the dictionary revealed. Update the Intent block.Draft and run safe SQL. Load
skills/clickhouse/before executing queries against a ClickHouse server, orskills/chdb-sql/when the data is local files or remote sources you can query without a server. Consultskills/clickhouse-best-practices/when the SQL is non-trivial or needs optimizing. Apply the confirmed Intent block.Analyze results. Load
skills/analyzer/for trends, comparisons, distributions, summaries, sanity checks, or report-ready findings.Create and save artifacts. Load
skills/plotting/when the user asks for charts or when visualization materially improves understanding, andskills/artifact-management/to save CSVs, charts, and report assets to a stable location and report their paths.
Elicitation is an invariant, not just step 1. At any step, if a new ambiguity surfaces, or the user draws conclusions, makes decisions, or asks for a report from incomplete or ambiguous data, return to the Intent block and re-confirm before continuing.
Core rules
Never use ClickHouse MCP tools. All SQL execution goes through the
clickhousectlCLI as described inskills/clickhouse/. Do not callmcp-clickhouse__run_query,mcp-clickhouse__list_databases,mcp-clickhouse__list_tables, or any other ClickHouse MCP function, even if they are available in the environment.Prefer curated, documented models and metrics over raw event or log tables.
State the definitions, filters, time window, and assumptions used.
Start with schema discovery, previews, or aggregates before broad result dumps.
Ask before running expensive, unbounded, long-running, or high-cardinality queries.
Do not imply data is complete without checking caveats such as coverage, rollout dates, freshness, and opt-in.
Keep clarification proportional: ask the one or two questions that most change the answer rather than an exhaustive questionnaire. Asking too little is the more common failure than asking too much.
Never echo credentials or secrets into the conversation. See
skills/clickhouse/for auth handling.
Standard answer shape
Answer: ...
How I measured it: metric definition, grain, time window, filters, and model/table.
SQL/source: the query, table/model, or artifact path.
Caveats: coverage, ambiguity, sample size, freshness, or assumptions.
Next checks: 1-3 useful follow-ups when warranted.Files
- ATTRIBUTION.mdAdded by AutoGineer830 B
- LICENSELicence file added by AutoGineer10.5 KiB
- SKILL.md9.4 KiB
- examples.md2.9 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to the Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by the Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding any notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
Copyright 2026 Cline Bot Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Node.js
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Cline
- Publisher
- Cline (Official)
- Source
- cline/skills · skills/data-analyst · commit 2637846
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Cline or Cline.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download data-analyst.zip