{"id":"b3881d8a-b57d-47ea-8b84-b7e5ec90337e","entityType":"agent","slug":"clawhub-hith3sh-clickhouse-analytics","name":"ClickHouse","canonicalUrl":"https://www.xpersona.co/agent/clawhub-hith3sh-clickhouse-analytics","canonicalPath":"/agent/clawhub-hith3sh-clickhouse-analytics","generatedAt":"2026-10-10T02:15:55.398Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T13:35:02.926Z","emptyReason":null},"description":"Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics da... Skill: ClickHouse Owner: hith3sh Summary: Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics da... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:05:15.678Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic so","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.6K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:clickhouse-analytics","sourceUrl":"https://clawhub.ai/hith3sh/clickhouse-analytics","homepage":"https://clawhub.ai/hith3sh/skills/clickhouse-analytics","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/hith3sh/clickhouse-analytics","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/hith3sh/skills/clickhouse-analytics","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":68,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics da..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T13:35:02.926Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T13:35:02.926Z","emptyReason":null},"stars":null,"forks":null,"downloads":2555,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"2.6K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T13:35:02.926Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T13:35:02.926Z","lastCrawledAt":"2026-10-09T13:35:02.926Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T13:35:02.926Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-06-09T07:05:15.678Z","changelog":"Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.","fileCount":3,"zipByteSize":5235},{"version":"1.0.4","createdAt":"2026-06-09T04:45:04.969Z","changelog":"- Removed the sample file skill-card.md. - No functional or behavioral changes to the skill itself. - Documentation and usage instructions remain unchanged.","fileCount":3,"zipByteSize":5218},{"version":"1.0.2","createdAt":"2026-06-08T16:45:13.246Z","changelog":"- No file changes detected in this release. - The skill version has been updated to 1.0.2, but no new features, bug fixes, or documentation updates are present.","fileCount":3,"zipByteSize":5071},{"version":"1.0.1","createdAt":"2026-06-08T16:26:45.208Z","changelog":"clickhouse-analytics 1.0.1 - Added a ClickHouse logo image to the documentation for improved branding. - Minor content revision to SKILL.md for clarity and presentation. - Removed obsolete skill-card.md file. - No changes to actual tool logic or functionality.","fileCount":3,"zipByteSize":5173},{"version":"0.1.1","createdAt":"2026-06-07T13:27:36.660Z","changelog":"Full rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.","fileCount":3,"zipByteSize":4962},{"version":"0.1.0","createdAt":"2026-05-24T16:06:39.811Z","changelog":"Initial release of clickhouse-analytics. - Enables inspection of databases and schemas and running analytics queries in ClickHouse via ClawLink. - Supports a read-first workflow with clear setup and execution steps. - Guides users through ClawLink pairing and ClickHouse connection without sharing raw credentials. - Dynamic tool discovery based on user’s connected integrations. - Provides best practices and rules for using ClickHouse tools securely within OpenClaw.","fileCount":3,"zipByteSize":3479}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:clickhouse-analytics","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-clickhouse-analytics/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-clickhouse-analytics/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-clickhouse-analytics/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-clickhouse-analytics/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-clickhouse-analytics/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-clickhouse-analytics/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T02:15:55.397Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-clickhouse-analytics/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-clickhouse-analytics/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-clickhouse-analytics/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-clickhouse-analytics/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T13:35:02.926Z","emptyReason":null},"readme":"Skill: ClickHouse\n\nOwner: hith3sh\n\nSummary: Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics da...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-06-09T07:05:15.678Z | user\n\nAdd UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.\n\nv1.0.4 | 2026-06-09T04:45:04.969Z | auto\n\n- Removed the sample file skill-card.md.\n- No functional or behavioral changes to the skill itself.\n- Documentation and usage instructions remain unchanged.\n\nv1.0.2 | 2026-06-08T16:45:13.246Z | auto\n\n- No file changes detected in this release.\n- The skill version has been updated to 1.0.2, but no new features, bug fixes, or documentation updates are present.\n\nv1.0.1 | 2026-06-08T16:26:45.208Z | auto\n\nclickhouse-analytics 1.0.1\n\n- Added a ClickHouse logo image to the documentation for improved branding.\n- Minor content revision to SKILL.md for clarity and presentation.\n- Removed obsolete skill-card.md file.\n- No changes to actual tool logic or functionality.\n\nv0.1.1 | 2026-06-07T13:27:36.660Z | user\n\nFull rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.\n\nv0.1.0 | 2026-05-24T16:06:39.811Z | auto\n\nInitial release of clickhouse-analytics.\n\n- Enables inspection of databases and schemas and running analytics queries in ClickHouse via ClawLink.\n- Supports a read-first workflow with clear setup and execution steps.\n- Guides users through ClawLink pairing and ClickHouse connection without sharing raw credentials.\n- Dynamic tool discovery based on user’s connected integrations.\n- Provides best practices and rules for using ClickHouse tools securely within OpenClaw.\n\nArchive index:\n\nArchive v1.0.5: 3 files, 5235 bytes\n\nFiles: skill-card.md (2333b), SKILL.md (11888b), _meta.json (139b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: clickhouse-analytics\ndescription: Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics data, explore database schemas, or run read-only SQL queries for business intelligence.\n---\n\n# ClickHouse\n\n\n\nWork with ClickHouse from chat — inspect databases, review schemas, and run read-only SQL analytics queries via the ClickHouse HTTP API with API key authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=clickhouse-analytics) for hosted connection flows and credentials so you do not need to configure ClickHouse API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect ClickHouse |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect ClickHouse |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ ClickHouse HTTP API│\n│ (User Chat) │ │ (API Key) │ │ (SQL Queries) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect ClickHouse│ │\n │ │ 4. Secure Key │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ ClickHouse│\n │ File │ │ Auth │ │ Queries │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for ClickHouse again.\"\n\n## Quick Start\n\n```bash\n# List databases\nclawlink_call_tool --tool \"clickhouse_list_databases\" --params '{}'\n\n# List tables in a database\nclawlink_call_tool --tool \"clickhouse_list_tables\" --params '{\"database\": \"default\"}'\n\n# Get database schema overview\nclawlink_call_tool --tool \"clickhouse_get_database_schema\" --params '{\"database\": \"default\"}'\n```\n\n## Authentication\n\nAll ClickHouse tool calls are authenticated automatically by ClawLink using the user's connected ClickHouse account.\n\n**No credentials are required in chat.** ClawLink stores the connection details securely and injects them into every ClickHouse request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=clickhouse and connect ClickHouse.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `clickhouse` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration clickhouse\n```\n\n**Response:** Returns the live tool catalog for ClickHouse.\n\n### Reconnect\n\nIf ClickHouse tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=clickhouse\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration clickhouse`\n\n## Security & Permissions\n\n- ClickHouse queries are read-only by design in ClawLink — no INSERT, ALTER, DROP, or TRUNCATE operations are exposed.\n- **Query operations require user confirmation** for large result sets or expensive queries (full table scans, GROUP BY without limits).\n- Avoid running queries that could lock tables or consume excessive resources.\n\n## Tool Reference\n\n### Schema Discovery\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_list_databases` | List all databases in the ClickHouse instance | Read |\n| `clickhouse_list_tables` | List tables in a database with engine, size, and row count | Read |\n| `clickhouse_get_database_schema` | Get full schema overview including all tables and columns | Read |\n| `clickhouse_get_table_schema` | Get detailed schema for a specific table including columns and types | Read |\n\n### Query Execution\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_execute_query` | Execute a read-only SQL query and return results | Read |\n\n### Interface\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_get_play_interface` | Get the ClickHouse Play web interface URL for interactive queries | Read |\n\n## Code Examples\n\n### List all databases\n\n```bash\nclawlink_call_tool --tool \"clickhouse_list_databases\" \\\n --params '{}'\n```\n\n### Get database schema\n\n```bash\nclawlink_call_tool --tool \"clickhouse_get_database_schema\" \\\n --params '{\n \"database\": \"analytics\"\n }'\n```\n\n### Execute a simple query\n\n```bash\nclawlink_call_tool --tool \"clickhouse_execute_query\" \\\n --params '{\n \"query\": \"SELECT * FROM events WHERE date >= today() - 7 LIMIT 100\"\n }'\n```\n\n### Get table schema\n\n```bash\nclawlink_call_tool --tool \"clickhouse_get_table_schema\" \\\n --params '{\n \"database\": \"analytics\",\n \"table\": \"events\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm ClickHouse is connected.\n2. Call `clawlink_list_tools --integration clickhouse` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `clickhouse`.\n5. If no ClickHouse tools appear, direct the user to https://claw-link.dev/dashboard?add=clickhouse.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ SCHEMA DISCOVERY (Always first) │\n│ list_databases → list_tables → get_table_schema │\n│ │\n│ Example: Discover tables → Understand schema → Then query │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ QUERY EXECUTION (Read-only) │\n│ describe → preview → confirm → execute │\n│ │\n│ Example: Describe query → Preview results → User approves │\n│ → Execute read-only query │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. Always explore the schema first with `clickhouse_list_databases` and `clickhouse_get_database_schema` before running queries.\n2. For unfamiliar tables, call `clickhouse_get_table_schema` to understand column names and types.\n3. Keep queries targeted with WHERE clauses and LIMIT — avoid full table scans when possible.\n4. For large or complex queries, confirm the expected result size with the user before executing.\n5. If the tool call fails, report the real error. Do not invent results.\n\n## Notes\n\n- ClickHouse SQL syntax differs from standard SQL — use ClickHouse-specific functions and syntax.\n- All queries are read-only — no data modification is possible through ClawLink tools.\n- Use `LIMIT` to prevent accidentally large result sets.\n- Sample data can be included in table schema responses — use it to understand data types.\n- The Play interface provides an interactive HTML UI with Monaco Editor for manual query writing.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration clickhouse`. |\n| Missing connection | ClickHouse is not connected. Direct the user to https://claw-link.dev/dashboard?add=clickhouse. |\n| `SyntaxError` | SQL syntax error in query. Check ClickHouse SQL syntax. |\n| `TableNotFound` | Table or database does not exist. Verify names with schema tools first. |\n| `Query error` | Query failed. Check query logic and table structure. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Query Errors\n\n1. Always use schema tools first to verify table and column names.\n2. Verify the database name with `clickhouse_list_databases`.\n3. Use `LIMIT` to test queries with small result sets first.\n\n## Resources\n\n- [ClickHouse Documentation](https://clickhouse.com/docs)\n- [ClickHouse SQL Reference](https://clickhouse.com/docs/en/sql-reference/)\n- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=clickhouse-analytics\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Datadog](https://clawhub.ai/hith3sh/datadog-monitoring) — For Datadog observability and metrics\n- [Snowflake](https://clawhub.ai/hith3sh/snowflake-data) — For Snowflake data warehouse queries\n- [PostgreSQL](https://clawhub.ai/hith3sh/postgresql-database) — For PostgreSQL database operations\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=clickhouse-analytics)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"clickhouse-analytics\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1780988715678\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nInspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, data analysts, and analytics engineers use this skill to discover ClickHouse schemas, inspect tables, and run read-only SQL analytics queries from an agent workflow.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill uses ClawLink to store ClickHouse connection details and mediate queries and results.\n\nMitigation: Review ClawLink credential handling and revocation processes before installation.\n\nRisk: Database queries can expose sensitive data or consume excessive ClickHouse resources if account permissions are broad.\n\nMitigation: Use a dedicated ClickHouse account with server-enforced read-only permissions, minimal database and table access, and query or resource limits.\n\nRisk: Large result sets or expensive queries can affect performance.\n\nMitigation: Explore schemas first, keep queries targeted with WHERE clauses and LIMIT, and require user confirmation for large result sets or expensive queries.\n\n## Reference(s):\n\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/clickhouse-analytics)\n- [ClickHouse Documentation](https://clickhouse.com/docs)\n- [ClickHouse SQL Reference](https://clickhouse.com/docs/en/sql-reference/)\n- [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=clickhouse-analytics)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n\n## Skill Output:\n\n**Output Type(s):** [markdown, shell commands, configuration, guidance, API calls]\n\n**Output Format:** [Markdown with inline bash and JSON command examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Outputs guide schema discovery, connection checks, and read-only query execution through ClawLink tools.]\n\n## Skill Version(s):\n\n1.0.5 (source: ClawHub release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 3 files, 5218 bytes\n\nFiles: skill-card.md (2478b), SKILL.md (11669b), _meta.json (139b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: clickhouse-analytics\ndescription: Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics data, explore database schemas, or run read-only SQL queries for business intelligence.\n---\n\n# ClickHouse\n\n\n\nWork with ClickHouse from chat — inspect databases, review schemas, and run read-only SQL analytics queries via the ClickHouse HTTP API with API key authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure ClickHouse API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect ClickHouse |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect ClickHouse |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ ClickHouse HTTP API│\n│ (User Chat) │ │ (API Key) │ │ (SQL Queries) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect ClickHouse│ │\n │ │ 4. Secure Key │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ ClickHouse│\n │ File │ │ Auth │ │ Queries │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for ClickHouse again.\"\n\n## Quick Start\n\n```bash\n# List databases\nclawlink_call_tool --tool \"clickhouse_list_databases\" --params '{}'\n\n# List tables in a database\nclawlink_call_tool --tool \"clickhouse_list_tables\" --params '{\"database\": \"default\"}'\n\n# Get database schema overview\nclawlink_call_tool --tool \"clickhouse_get_database_schema\" --params '{\"database\": \"default\"}'\n```\n\n## Authentication\n\nAll ClickHouse tool calls are authenticated automatically by ClawLink using the user's connected ClickHouse account.\n\n**No credentials are required in chat.** ClawLink stores the connection details securely and injects them into every ClickHouse request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=clickhouse and connect ClickHouse.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `clickhouse` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration clickhouse\n```\n\n**Response:** Returns the live tool catalog for ClickHouse.\n\n### Reconnect\n\nIf ClickHouse tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=clickhouse\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration clickhouse`\n\n## Security & Permissions\n\n- ClickHouse queries are read-only by design in ClawLink — no INSERT, ALTER, DROP, or TRUNCATE operations are exposed.\n- **Query operations require user confirmation** for large result sets or expensive queries (full table scans, GROUP BY without limits).\n- Avoid running queries that could lock tables or consume excessive resources.\n\n## Tool Reference\n\n### Schema Discovery\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_list_databases` | List all databases in the ClickHouse instance | Read |\n| `clickhouse_list_tables` | List tables in a database with engine, size, and row count | Read |\n| `clickhouse_get_database_schema` | Get full schema overview including all tables and columns | Read |\n| `clickhouse_get_table_schema` | Get detailed schema for a specific table including columns and types | Read |\n\n### Query Execution\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_execute_query` | Execute a read-only SQL query and return results | Read |\n\n### Interface\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_get_play_interface` | Get the ClickHouse Play web interface URL for interactive queries | Read |\n\n## Code Examples\n\n### List all databases\n\n```bash\nclawlink_call_tool --tool \"clickhouse_list_databases\" \\\n --params '{}'\n```\n\n### Get database schema\n\n```bash\nclawlink_call_tool --tool \"clickhouse_get_database_schema\" \\\n --params '{\n \"database\": \"analytics\"\n }'\n```\n\n### Execute a simple query\n\n```bash\nclawlink_call_tool --tool \"clickhouse_execute_query\" \\\n --params '{\n \"query\": \"SELECT * FROM events WHERE date >= today() - 7 LIMIT 100\"\n }'\n```\n\n### Get table schema\n\n```bash\nclawlink_call_tool --tool \"clickhouse_get_table_schema\" \\\n --params '{\n \"database\": \"analytics\",\n \"table\": \"events\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm ClickHouse is connected.\n2. Call `clawlink_list_tools --integration clickhouse` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `clickhouse`.\n5. If no ClickHouse tools appear, direct the user to https://claw-link.dev/dashboard?add=clickhouse.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ SCHEMA DISCOVERY (Always first) │\n│ list_databases → list_tables → get_table_schema │\n│ │\n│ Example: Discover tables → Understand schema → Then query │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ QUERY EXECUTION (Read-only) │\n│ describe → preview → confirm → execute │\n│ │\n│ Example: Describe query → Preview results → User approves │\n│ → Execute read-only query │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. Always explore the schema first with `clickhouse_list_databases` and `clickhouse_get_database_schema` before running queries.\n2. For unfamiliar tables, call `clickhouse_get_table_schema` to understand column names and types.\n3. Keep queries targeted with WHERE clauses and LIMIT — avoid full table scans when possible.\n4. For large or complex queries, confirm the expected result size with the user before executing.\n5. If the tool call fails, report the real error. Do not invent results.\n\n## Notes\n\n- ClickHouse SQL syntax differs from standard SQL — use ClickHouse-specific functions and syntax.\n- All queries are read-only — no data modification is possible through ClawLink tools.\n- Use `LIMIT` to prevent accidentally large result sets.\n- Sample data can be included in table schema responses — use it to understand data types.\n- The Play interface provides an interactive HTML UI with Monaco Editor for manual query writing.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration clickhouse`. |\n| Missing connection | ClickHouse is not connected. Direct the user to https://claw-link.dev/dashboard?add=clickhouse. |\n| `SyntaxError` | SQL syntax error in query. Check ClickHouse SQL syntax. |\n| `TableNotFound` | Table or database does not exist. Verify names with schema tools first. |\n| `Query error` | Query failed. Check query logic and table structure. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Query Errors\n\n1. Always use schema tools first to verify table and column names.\n2. Verify the database name with `clickhouse_list_databases`.\n3. Use `LIMIT` to test queries with small result sets first.\n\n## Resources\n\n- [ClickHouse Documentation](https://clickhouse.com/docs)\n- [ClickHouse SQL Reference](https://clickhouse.com/docs/en/sql-reference/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Datadog](https://clawhub.ai/hith3sh/datadog-monitoring) — For Datadog observability and metrics\n- [Snowflake](https://clawhub.ai/hith3sh/snowflake-data) — For Snowflake data warehouse queries\n- [PostgreSQL](https://clawhub.ai/hith3sh/postgresql-database) — For PostgreSQL database operations\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"clickhouse-analytics\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1780980304969\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:
\nInspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, analysts, and operators use this skill in OpenClaw to inspect ClickHouse schemas and run read-only analytics queries through a connected ClawLink account.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill requires access to a ClickHouse connection through ClawLink, which may expose schemas and query results to OpenClaw workflows.
\nMitigation: Install only if you trust ClawLink with the ClickHouse connection and are comfortable with OpenClaw inspecting schemas and read-only query results.
\nRisk: Large or expensive analytics queries can consume database resources.
\nMitigation: Review queries before approval, prefer targeted WHERE clauses and LIMITs, and avoid full table scans or broad GROUP BY operations unless explicitly intended.
\nRisk: Incorrect SQL or assumptions about table structure can produce failed or misleading results.
\nMitigation: Use schema discovery tools first, verify database, table, and column names, and report real query errors instead of inventing results.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/clickhouse-analytics)
\n- [ClickHouse Documentation](https://clickhouse.com/docs)
\n- [ClickHouse SQL Reference](https://clickhouse.com/docs/en/sql-reference/)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and tool-call examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include SQL query guidance, schema summaries, and ClawLink tool-call parameters.]
\n\n## Skill Version(s):
\n1.0.4 (source: server-resolved release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.2: 3 files, 5071 bytes\n\nFiles: skill-card.md (2197b), SKILL.md (11669b), _meta.json (139b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: clickhouse-analytics\ndescription: Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics data, explore database schemas, or run read-only SQL queries for business intelligence.\n---\n\n# ClickHouse\n\n\n\nWork with ClickHouse from chat — inspect databases, review schemas, and run read-only SQL analytics queries via the ClickHouse HTTP API with API key authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure ClickHouse API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect ClickHouse |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect ClickHouse |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ ClickHouse HTTP API│\n│ (User Chat) │ │ (API Key) │ │ (SQL Queries) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect ClickHouse│ │\n │ │ 4. Secure Key │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ ClickHouse│\n │ File │ │ Auth │ │ Queries │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for ClickHouse again.\"\n\n## Quick Start\n\n```bash\n# List databases\nclawlink_call_tool --tool \"clickhouse_list_databases\" --params '{}'\n\n# List tables in a database\nclawlink_call_tool --tool \"clickhouse_list_tables\" --params '{\"database\": \"default\"}'\n\n# Get database schema overview\nclawlink_call_tool --tool \"clickhouse_get_database_schema\" --params '{\"database\": \"default\"}'\n```\n\n## Authentication\n\nAll ClickHouse tool calls are authenticated automatically by ClawLink using the user's connected ClickHouse account.\n\n**No credentials are required in chat.** ClawLink stores the connection details securely and injects them into every ClickHouse request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=clickhouse and connect ClickHouse.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `clickhouse` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration clickhouse\n```\n\n**Response:** Returns the live tool catalog for ClickHouse.\n\n### Reconnect\n\nIf ClickHouse tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=clickhouse\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration clickhouse`\n\n## Security & Permissions\n\n- ClickHouse queries are read-only by design in ClawLink — no INSERT, ALTER, DROP, or TRUNCATE operations are exposed.\n- **Query operations require user confirmation** for large result sets or expensive queries (full table scans, GROUP BY without limits).\n- Avoid running queries that could lock tables or consume excessive resources.\n\n## Tool Reference\n\n### Schema Discovery\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_list_databases` | List all databases in the ClickHouse instance | Read |\n| `clickhouse_list_tables` | List tables in a database with engine, size, and row count | Read |\n| `clickhouse_get_database_schema` | Get full schema overview including all tables and columns | Read |\n| `clickhouse_get_table_schema` | Get detailed schema for a specific table including columns and types | Read |\n\n### Query Execution\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_execute_query` | Execute a read-only SQL query and return results | Read |\n\n### Interface\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_get_play_interface` | Get the ClickHouse Play web interface URL for interactive queries | Read |\n\n## Code Examples\n\n### List all databases\n\n```bash\nclawlink_call_tool --tool \"clickhouse_list_databases\" \\\n --params '{}'\n```\n\n### Get database schema\n\n```bash\nclawlink_call_tool --tool \"clickhouse_get_database_schema\" \\\n --params '{\n \"database\": \"analytics\"\n }'\n```\n\n### Execute a simple query\n\n```bash\nclawlink_call_tool --tool \"clickhouse_execute_query\" \\\n --params '{\n \"query\": \"SELECT * FROM events WHERE date >= today() - 7 LIMIT 100\"\n }'\n```\n\n### Get table schema\n\n```bash\nclawlink_call_tool --tool \"clickhouse_get_table_schema\" \\\n --params '{\n \"database\": \"analytics\",\n \"table\": \"events\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm ClickHouse is connected.\n2. Call `clawlink_list_tools --integration clickhouse` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `clickhouse`.\n5. If no ClickHouse tools appear, direct the user to https://claw-link.dev/dashboard?add=clickhouse.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ SCHEMA DISCOVERY (Always first) │\n│ list_databases → list_tables → get_table_schema │\n│ │\n│ Example: Discover tables → Understand schema → Then query │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ QUERY EXECUTION (Read-only) │\n│ describe → preview → confirm → execute │\n│ │\n│ Example: Describe query → Preview results → User approves │\n│ → Execute read-only query │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. Always explore the schema first with `clickhouse_list_databases` and `clickhouse_get_database_schema` before running queries.\n2. For unfamiliar tables, call `clickhouse_get_table_schema` to understand column names and types.\n3. Keep queries targeted with WHERE clauses and LIMIT — avoid full table scans when possible.\n4. For large or complex queries, confirm the expected result size with the user before executing.\n5. If the tool call fails, report the real error. Do not invent results.\n\n## Notes\n\n- ClickHouse SQL syntax differs from standard SQL — use ClickHouse-specific functions and syntax.\n- All queries are read-only — no data modification is possible through ClawLink tools.\n- Use `LIMIT` to prevent accidentally large result sets.\n- Sample data can be included in table schema responses — use it to understand data types.\n- The Play interface provides an interactive HTML UI with Monaco Editor for manual query writing.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration clickhouse`. |\n| Missing connection | ClickHouse is not connected. Direct the user to https://claw-link.dev/dashboard?add=clickhouse. |\n| `SyntaxError` | SQL syntax error in query. Check ClickHouse SQL syntax. |\n| `TableNotFound` | Table or database does not exist. Verify names with schema tools first. |\n| `Query error` | Query failed. Check query logic and table structure. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Query Errors\n\n1. Always use schema tools first to verify table and column names.\n2. Verify the database name with `clickhouse_list_databases`.\n3. Use `LIMIT` to test queries with small result sets first.\n\n## Resources\n\n- [ClickHouse Documentation](https://clickhouse.com/docs)\n- [ClickHouse SQL Reference](https://clickhouse.com/docs/en/sql-reference/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Datadog](https://clawhub.ai/hith3sh/datadog-monitoring) — For Datadog observability and metrics\n- [Snowflake](https://clawhub.ai/hith3sh/snowflake-data) — For Snowflake data warehouse queries\n- [PostgreSQL](https://clawhub.ai/hith3sh/postgresql-database) — For PostgreSQL database operations\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"clickhouse-analytics\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1780937113246\n}\n\nFile v1.0.2:skill-card.md\n\n## Description:
\nInspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, data analysts, and operations teams use this skill to inspect ClickHouse schemas and run read-only analytics queries from an OpenClaw chat workflow.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Schema details and query results may expose sensitive business data from the connected ClickHouse instance.
\nMitigation: Use a read-only, least-privilege ClickHouse account, limit result sizes, and review queries before execution.
\nRisk: Expensive or broad analytics queries can consume database resources even when they are read-only.
\nMitigation: Inspect schemas first, keep queries targeted with WHERE clauses and LIMIT, and confirm large or complex queries before running them.
\n\n\n## Reference(s):
\n- [ClickHouse Documentation](https://clickhouse.com/docs)
\n- [ClickHouse SQL Reference](https://clickhouse.com/docs/en/sql-reference/)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Produces read-only database discovery and query guidance; query results may include sensitive business data from the connected ClickHouse instance.]
\n\n## Skill Version(s):
\n1.0.2 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 3 files, 5173 bytes\n\nFiles: skill-card.md (2395b), SKILL.md (11669b), _meta.json (139b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: clickhouse-analytics\ndescription: Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics data, explore database schemas, or run read-only SQL queries for business intelligence.\n---\n\n# ClickHouse\n\n\n\nWork with ClickHouse from chat — inspect databases, review schemas, and run read-only SQL analytics queries via the ClickHouse HTTP API with API key authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure ClickHouse API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect ClickHouse |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect ClickHouse |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ ClickHouse HTTP API│\n│ (User Chat) │ │ (API Key) │ │ (SQL Queries) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect ClickHouse│ │\n │ │ 4. Secure Key │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ ClickHouse│\n │ File │ │ Auth │ │ Queries │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for ClickHouse again.\"\n\n## Quick Start\n\n```bash\n# List databases\nclawlink_call_tool --tool \"clickhouse_list_databases\" --params '{}'\n\n# List tables in a database\nclawlink_call_tool --tool \"clickhouse_list_tables\" --params '{\"database\": \"default\"}'\n\n# Get database schema overview\nclawlink_call_tool --tool \"clickhouse_get_database_schema\" --params '{\"database\": \"default\"}'\n```\n\n## Authentication\n\nAll ClickHouse tool calls are authenticated automatically by ClawLink using the user's connected ClickHouse account.\n\n**No credentials are required in chat.** ClawLink stores the connection details securely and injects them into every ClickHouse request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=clickhouse and connect ClickHouse.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `clickhouse` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration clickhouse\n```\n\n**Response:** Returns the live tool catalog for ClickHouse.\n\n### Reconnect\n\nIf ClickHouse tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=clickhouse\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration clickhouse`\n\n## Security & Permissions\n\n- ClickHouse queries are read-only by design in ClawLink — no INSERT, ALTER, DROP, or TRUNCATE operations are exposed.\n- **Query operations require user confirmation** for large result sets or expensive queries (full table scans, GROUP BY without limits).\n- Avoid running queries that could lock tables or consume excessive resources.\n\n## Tool Reference\n\n### Schema Discovery\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_list_databases` | List all databases in the ClickHouse instance | Read |\n| `clickhouse_list_tables` | List tables in a database with engine, size, and row count | Read |\n| `clickhouse_get_database_schema` | Get full schema overview including all tables and columns | Read |\n| `clickhouse_get_table_schema` | Get detailed schema for a specific table including columns and types | Read |\n\n### Query Execution\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_execute_query` | Execute a read-only SQL query and return results | Read |\n\n### Interface\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_get_play_interface` | Get the ClickHouse Play web interface URL for interactive queries | Read |\n\n## Code Examples\n\n### List all databases\n\n```bash\nclawlink_call_tool --tool \"clickhouse_list_databases\" \\\n --params '{}'\n```\n\n### Get database schema\n\n```bash\nclawlink_call_tool --tool \"clickhouse_get_database_schema\" \\\n --params '{\n \"database\": \"analytics\"\n }'\n```\n\n### Execute a simple query\n\n```bash\nclawlink_call_tool --tool \"clickhouse_execute_query\" \\\n --params '{\n \"query\": \"SELECT * FROM events WHERE date >= today() - 7 LIMIT 100\"\n }'\n```\n\n### Get table schema\n\n```bash\nclawlink_call_tool --tool \"clickhouse_get_table_schema\" \\\n --params '{\n \"database\": \"analytics\",\n \"table\": \"events\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm ClickHouse is connected.\n2. Call `clawlink_list_tools --integration clickhouse` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `clickhouse`.\n5. If no ClickHouse tools appear, direct the user to https://claw-link.dev/dashboard?add=clickhouse.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ SCHEMA DISCOVERY (Always first) │\n│ list_databases → list_tables → get_table_schema │\n│ │\n│ Example: Discover tables → Understand schema → Then query │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ QUERY EXECUTION (Read-only) │\n│ describe → preview → confirm → execute │\n│ │\n│ Example: Describe query → Preview results → User approves │\n│ → Execute read-only query │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. Always explore the schema first with `clickhouse_list_databases` and `clickhouse_get_database_schema` before running queries.\n2. For unfamiliar tables, call `clickhouse_get_table_schema` to understand column names and types.\n3. Keep queries targeted with WHERE clauses and LIMIT — avoid full table scans when possible.\n4. For large or complex queries, confirm the expected result size with the user before executing.\n5. If the tool call fails, report the real error. Do not invent results.\n\n## Notes\n\n- ClickHouse SQL syntax differs from standard SQL — use ClickHouse-specific functions and syntax.\n- All queries are read-only — no data modification is possible through ClawLink tools.\n- Use `LIMIT` to prevent accidentally large result sets.\n- Sample data can be included in table schema responses — use it to understand data types.\n- The Play interface provides an interactive HTML UI with Monaco Editor for manual query writing.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration clickhouse`. |\n| Missing connection | ClickHouse is not connected. Direct the user to https://claw-link.dev/dashboard?add=clickhouse. |\n| `SyntaxError` | SQL syntax error in query. Check ClickHouse SQL syntax. |\n| `TableNotFound` | Table or database does not exist. Verify names with schema tools first. |\n| `Query error` | Query failed. Check query logic and table structure. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Query Errors\n\n1. Always use schema tools first to verify table and column names.\n2. Verify the database name with `clickhouse_list_databases`.\n3. Use `LIMIT` to test queries with small result sets first.\n\n## Resources\n\n- [ClickHouse Documentation](https://clickhouse.com/docs)\n- [ClickHouse SQL Reference](https://clickhouse.com/docs/en/sql-reference/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Datadog](https://clawhub.ai/hith3sh/datadog-monitoring) — For Datadog observability and metrics\n- [Snowflake](https://clawhub.ai/hith3sh/snowflake-data) — For Snowflake data warehouse queries\n- [PostgreSQL](https://clawhub.ai/hith3sh/postgresql-database) — For PostgreSQL database operations\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"clickhouse-analytics\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1780936005208\n}\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nInspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, data analysts, and operations teams use this skill to inspect ClickHouse schemas and run read-only SQL analytics through ClawLink-connected ClickHouse accounts.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill requires ClawLink-connected ClickHouse credentials, and query results may contain sensitive data.
\nMitigation: Use least-privilege, preferably read-only ClickHouse credentials and avoid exposing confidential query results in shared chats or logs.
\nRisk: Broad or expensive SQL queries can return large result sets or consume database resources.
\nMitigation: Explore schemas first, use targeted WHERE clauses and LIMITs, and require user approval before large result sets or expensive queries.
\nRisk: Incorrect SQL can produce misleading analytics or fail against ClickHouse-specific syntax.
\nMitigation: Verify database, table, and column names with schema tools before querying, and report real tool errors instead of inventing results.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/hith3sh/clickhouse-analytics)
\n- [ClickHouse Documentation](https://clickhouse.com/docs)
\n- [ClickHouse SQL Reference](https://clickhouse.com/docs/en/sql-reference/)
\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, guidance]
\n**Output Format:** [Markdown with inline shell commands and SQL examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Read-only ClickHouse tool calls should be preceded by schema discovery and user approval for large or expensive queries.]
\n\n## Skill Version(s):
\n1.0.1 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.1.1: 3 files, 4962 bytes\n\nFiles: skill-card.md (1935b), SKILL.md (11552b), _meta.json (139b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: clickhouse-analytics\ndescription: Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics data, explore database schemas, or run read-only SQL queries for business intelligence.\n---\n\n# ClickHouse\n\nWork with ClickHouse from chat — inspect databases, review schemas, and run read-only SQL analytics queries via the ClickHouse HTTP API with API key authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure ClickHouse API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect ClickHouse |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect ClickHouse |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ ClickHouse HTTP API│\n│ (User Chat) │ │ (API Key) │ │ (SQL Queries) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect ClickHouse│ │\n │ │ 4. Secure Key │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ ClickHouse│\n │ File │ │ Auth │ │ Queries │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for ClickHouse again.\"\n\n## Quick Start\n\n```bash\n# List databases\nclawlink_call_tool --tool \"clickhouse_list_databases\" --params '{}'\n\n# List tables in a database\nclawlink_call_tool --tool \"clickhouse_list_tables\" --params '{\"database\": \"default\"}'\n\n# Get database schema overview\nclawlink_call_tool --tool \"clickhouse_get_database_schema\" --params '{\"database\": \"default\"}'\n```\n\n## Authentication\n\nAll ClickHouse tool calls are authenticated automatically by ClawLink using the user's connected ClickHouse account.\n\n**No credentials are required in chat.** ClawLink stores the connection details securely and injects them into every ClickHouse request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=clickhouse and connect ClickHouse.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `clickhouse` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration clickhouse\n```\n\n**Response:** Returns the live tool catalog for ClickHouse.\n\n### Reconnect\n\nIf ClickHouse tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=clickhouse\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration clickhouse`\n\n## Security & Permissions\n\n- ClickHouse queries are read-only by design in ClawLink — no INSERT, ALTER, DROP, or TRUNCATE operations are exposed.\n- **Query operations require user confirmation** for large result sets or expensive queries (full table scans, GROUP BY without limits).\n- Avoid running queries that could lock tables or consume excessive resources.\n\n## Tool Reference\n\n### Schema Discovery\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_list_databases` | List all databases in the ClickHouse instance | Read |\n| `clickhouse_list_tables` | List tables in a database with engine, size, and row count | Read |\n| `clickhouse_get_database_schema` | Get full schema overview including all tables and columns | Read |\n| `clickhouse_get_table_schema` | Get detailed schema for a specific table including columns and types | Read |\n\n### Query Execution\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_execute_query` | Execute a read-only SQL query and return results | Read |\n\n### Interface\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `clickhouse_get_play_interface` | Get the ClickHouse Play web interface URL for interactive queries | Read |\n\n## Code Examples\n\n### List all databases\n\n```bash\nclawlink_call_tool --tool \"clickhouse_list_databases\" \\\n --params '{}'\n```\n\n### Get database schema\n\n```bash\nclawlink_call_tool --tool \"clickhouse_get_database_schema\" \\\n --params '{\n \"database\": \"analytics\"\n }'\n```\n\n### Execute a simple query\n\n```bash\nclawlink_call_tool --tool \"clickhouse_execute_query\" \\\n --params '{\n \"query\": \"SELECT * FROM events WHERE date >= today() - 7 LIMIT 100\"\n }'\n```\n\n### Get table schema\n\n```bash\nclawlink_call_tool --tool \"clickhouse_get_table_schema\" \\\n --params '{\n \"database\": \"analytics\",\n \"table\": \"events\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm ClickHouse is connected.\n2. Call `clawlink_list_tools --integration clickhouse` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `clickhouse`.\n5. If no ClickHouse tools appear, direct the user to https://claw-link.dev/dashboard?add=clickhouse.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ SCHEMA DISCOVERY (Always first) │\n│ list_databases → list_tables → get_table_schema │\n│ │\n│ Example: Discover tables → Understand schema → Then query │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ QUERY EXECUTION (Read-only) │\n│ describe → preview → confirm → execute │\n│ │\n│ Example: Describe query → Preview results → User approves │\n│ → Execute read-only query │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. Always explore the schema first with `clickhouse_list_databases` and `clickhouse_get_database_schema` before running queries.\n2. For unfamiliar tables, call `clickhouse_get_table_schema` to understand column names and types.\n3. Keep queries targeted with WHERE clauses and LIMIT — avoid full table scans when possible.\n4. For large or complex queries, confirm the expected result size with the user before executing.\n5. If the tool call fails, report the real error. Do not invent results.\n\n## Notes\n\n- ClickHouse SQL syntax differs from standard SQL — use ClickHouse-specific functions and syntax.\n- All queries are read-only — no data modification is possible through ClawLink tools.\n- Use `LIMIT` to prevent accidentally large result sets.\n- Sample data can be included in table schema responses — use it to understand data types.\n- The Play interface provides an interactive HTML UI with Monaco Editor for manual query writing.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration clickhouse`. |\n| Missing connection | ClickHouse is not connected. Direct the user to https://claw-link.dev/dashboard?add=clickhouse. |\n| `SyntaxError` | SQL syntax error in query. Check ClickHouse SQL syntax. |\n| `TableNotFound` | Table or database does not exist. Verify names with schema tools first. |\n| `Query error` | Query failed. Check query logic and table structure. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Query Errors\n\n1. Always use schema tools first to verify table and column names.\n2. Verify the database name with `clickhouse_list_databases`.\n3. Use `LIMIT` to test queries with small result sets first.\n\n## Resources\n\n- [ClickHouse Documentation](https://clickhouse.com/docs)\n- [ClickHouse SQL Reference](https://clickhouse.com/docs/en/sql-reference/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Datadog](https://clawhub.ai/hith3sh/datadog-monitoring) — For Datadog observability and metrics\n- [Snowflake](https://clawhub.ai/hith3sh/snowflake-data) — For Snowflake data warehouse queries\n- [PostgreSQL](https://clawhub.ai/hith3sh/postgresql-database) — For PostgreSQL database operations\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v0.1.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"clickhouse-analytics\",\n \"version\": \"0.1.1\",\n \"publishedAt\": 1780838856660\n}\n\nFile v0.1.1:skill-card.md\n\n## Description:
\nInspect ClickHouse databases, review schemas, and run read-only SQL analytics queries via the ClickHouse HTTP API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, data analysts, and business intelligence users use this skill to inspect ClickHouse schema metadata and run targeted read-only analytics queries from an agent workflow.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Review before execution as proposals could introduce incorrect or misleading guidance into skills.
\nMitigation: Review and scan skill before deployment.
\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/clickhouse-analytics)
\n- [ClickHouse Documentation](https://clickhouse.com/docs)
\n- [ClickHouse SQL Reference](https://clickhouse.com/docs/en/sql-reference/)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, configuration, API calls, SQL queries]
\n**Output Format:** [Markdown with inline shell commands and SQL examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires a trusted ClawLink ClickHouse connection; use read-only ClickHouse access and limit expensive queries.]
\n\n## Skill Version(s):
\n0.1.1 (source: server-resolved release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.1.0: 3 files, 3479 bytes\n\nFiles: skill-card.md (2442b), SKILL.md (5023b), _meta.json (139b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: clickhouse-analytics\ndescription: Inspect databases, review schemas, and run analytics queries in ClickHouse - powered by ClawLink.\n---\n\n# ClickHouse\n\nWork with ClickHouse from chat - inspect databases, review schemas, and run analytics queries with a read-first workflow.\n\nPowered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure ClickHouse API access yourself.\n\n## Quick start\n\n1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`\n2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet\n3. If ClawLink is not configured, call `clawlink_begin_pairing`\n4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device\n5. After the user confirms approval, call `clawlink_get_pairing_status`\n6. Tell the user to connect ClickHouse at [claw-link.dev/dashboard?add=clickhouse](https://claw-link.dev/dashboard?add=clickhouse)\n7. When the user confirms ClickHouse is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `clickhouse` integration slug\n\n## Setup details\n\n### Installing the plugin\n\nIf the ClawLink plugin is not installed yet, tell the user to run:\n\n```\nopenclaw plugins install clawhub:clawlink-plugin\n```\n\nIf the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.\n\n### Pairing ClawLink\n\nIf ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.\n\n1. Call `clawlink_begin_pairing`.\n2. Tell the user to open the returned pairing URL in their browser.\n3. The user signs in to ClawLink if needed and approves the OpenClaw device.\n4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.\n\nThe resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.\n\n### Connecting ClickHouse\n\nTell the user to open https://claw-link.dev/dashboard?add=clickhouse and connect ClickHouse there. The page opens the add-connection panel filtered to ClickHouse. ClawLink's hosted page runs the ClickHouse provider connection flow. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `clickhouse`.\n\n## Using ClickHouse tools\n\nClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.\n\n### Discovery\n\n1. Call `clawlink_list_integrations` to confirm ClickHouse is connected.\n2. Call `clawlink_list_tools` with integration `clickhouse`.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `clickhouse`.\n5. If no ClickHouse tools appear, direct the user to https://claw-link.dev/dashboard?add=clickhouse.\n\n### Execution\n\n1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.\n2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.\n3. Prefer listing databases, tables, and schemas before running queries.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.\n5. Execute with `clawlink_call_tool`.\n6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## What you can do\n\nTypical ClickHouse tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):\n\n- List available databases and tables\n- Inspect full database schemas and table schemas\n- Run read-only SQL queries for analytics\n- Open the ClickHouse Play interface when available\n- Use schema-first workflows before wider queries\n\n## Rules\n\n- Always use ClawLink tools for ClickHouse. Do not ask the user for separate ClickHouse credentials.\n- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.\n- Do not invent slash commands or ask the user to paste raw credentials.\n- Ask for confirmation before broad, expensive, or potentially disruptive query runs.\n- If ClickHouse is not connected, direct the user to https://claw-link.dev/dashboard?add=clickhouse.\n- Never echo or repeat the user's ClawLink credential.\n\n## Resources\n\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n- ClawLink Source: https://github.com/hith3sh/clawlink\n- ClickHouse Docs: https://clickhouse.com/docs\n\nFile v0.1.0:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"clickhouse-analytics\",\n \"version\": \"0.1.0\",\n \"publishedAt\": 1779638799811\n}\n\nFile v0.1.0:skill-card.md\n\n## Description:
\nInspect databases, review schemas, and run analytics queries in ClickHouse - powered by ClawLink.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, data engineers, and analysts use this skill to connect an OpenClaw chat to ClickHouse through ClawLink, inspect databases and schemas, and run analytics queries with a read-first workflow.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: ClawLink mediates access to the user's ClickHouse connection.
\nMitigation: Install only if the user trusts ClawLink, connect ClickHouse through the hosted ClawLink flow, and do not paste raw credentials into chat.
\nRisk: Broad, expensive, or state-changing ClickHouse operations could affect cost, performance, or data.
\nMitigation: Prefer schema-first and read-only workflows, preview or describe unfamiliar tools, and ask for confirmation before broad, expensive, or potentially disruptive actions.
\nRisk: Available ClickHouse capabilities vary by account permissions and the live ClawLink tool catalog.
\nMitigation: List, search, and describe the current ClickHouse tools before use instead of assuming that a capability exists.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/clickhouse-analytics)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n- [ClickHouse Docs](https://clickhouse.com/docs)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown guidance with inline shell commands and URLs]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Tool availability depends on the user's connected ClickHouse account, permissions, scopes, and current ClawLink tool catalog.]
\n\n## Skill Version(s):
\n0.1.0 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: ClickHouse Owner: hith3sh Summary: Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics da... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:05:15.678Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic so","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ ClickHouse HTTP API│\n│ (User Chat) │ │ (API Key) │ │ (SQL Queries) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect ClickHouse│ │\n │ │ 4. Secure Key │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ ClickHouse│\n │ File │ │ Auth │ │ Queries │\n └──────────┘ └──────────┘ └──────────┘"},{"language":"bash","snippet":"openclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart"},{"language":"bash","snippet":"# List databases\nclawlink_call_tool --tool \"clickhouse_list_databases\" --params '{}'\n\n# List tables in a database\nclawlink_call_tool --tool \"clickhouse_list_tables\" --params '{\"database\": \"default\"}'\n\n# Get database schema overview\nclawlink_call_tool --tool \"clickhouse_get_database_schema\" --params '{\"database\": \"default\"}'"},{"language":"bash","snippet":"clawlink_list_integrations"},{"language":"bash","snippet":"clawlink_list_tools --integration clickhouse"},{"language":"bash","snippet":"clawlink_call_tool --tool \"clickhouse_list_databases\" \\\n --params '{}'"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: clickhouse-analytics\ndescription: Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics data, explore database schemas, or run read-only SQL queries for business intelligence.\n---\n\n# ClickHouse\n\n\n\nWork with ClickHouse from chat — inspect databases, review schemas, and run read-only SQL analytics queries via the ClickHouse HTTP API with API key authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=clickhouse-analytics) for hosted connection flows and credentials so you do not need to configure ClickHouse API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect ClickHouse |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect ClickHouse |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ ClickHouse HTTP API│\n│ (User Chat) │ │ (API Key) │ │ (SQL Queries) │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect ClickHouse│ │\n │ │ 4. Secure Key │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ ClickHouse│\n │ File │ │ Auth │ │ Queries │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for ClickHouse again.\"\n\n## Quick Start\n\n```bash\n# List databases\nclawlink_call_tool --tool \"clickhouse_list_databases\" --params '{}'\n\n# List tables in a database\nclawlink_call_tool --tool \"clickhouse_list_tables\" --params '{\"data"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"clickhouse-analytics\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1780988715678\n}"},{"path":"skill-card.md","content":"## Description:\n\nInspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, data analysts, and analytics engineers use this skill to discover ClickHouse schemas, inspect tables, and run read-only SQL analytics queries from an agent workflow.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill uses ClawLink to store ClickHouse connection details and mediate queries and results.\n\nMitigation: Review ClawLink credential handling and revocation processes before installation.\n\nRisk: Database queries can expose sensitive data or consume excessive ClickHouse resources if account permissions are broad.\n\nMitigation: Use a dedicated ClickHouse account with server-enforced read-only permissions, minimal database and table access, and query or resource limits.\n\nRisk: Large result sets or expensive queries can affect performance.\n\nMitigation: Explore schemas first, keep queries targeted with WHERE clauses and LIMIT, and require user confirmation for large result sets or expensive queries.\n\n## Reference(s):\n\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/clickhouse-analytics)\n- [ClickHouse Documentation](https://clickhouse.com/docs)\n- [ClickHouse SQL Reference](https://clickhouse.com/docs/en/sql-reference/)\n- [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=clickhouse-analytics)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n\n## Skill Output:\n\n**Output Type(s):** [markdown, shell commands, configuration, guidance, API calls]\n\n**Output Format:** [Markdown with inline bash and JSON command examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Outputs guide schema discovery, connection checks, and read-only query execution through ClawLink tools.]\n\n## Skill Version(s):\n\n1.0.5 (source: ClawHub release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics da... Skill: ClickHouse Owner: hith3sh Summary: Inspect ClickHouse databases, review schemas, and run SQL analytics queries via the ClickHouse HTTP API. Use this skill when users want to query analytics da... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:05:15.678Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic so","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1046,"uniquenessScore":51,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T13:35:02.926Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T13:35:02.926Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T02:15:55.398Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}