What makes KWDB Intelligent Inspection notable?

1.2K downloads. Trust evidence available

How should KWDB Intelligent Inspection be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

KWDB Intelligent Inspection

Run KaiwuDB inspection and health-check tasks. Use this skill for database health checks, metrics collection, anomaly detection, and inspection report generation.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.2k

Updated

Oct 10, 2026

Version

1.2.1

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.2K downloadsadoption · observed Oct 10, 2026
Latest release: 1.2.1release · observed Aug 28, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17e2f9k2hwm2p7q50y9wz03fs8445dh:kwdb-intelligent-inspection

Install using `clawhub skill install s17e2f9k2hwm2p7q50y9wz03fs8445dh:kwdb-intelligent-inspection` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/kwdb/kwdb-intelligent-inspection before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-kwdb-kwdb-intelligent-inspection/snapshot"

Documentation

CLAWHUB

84,090 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: kwdb-intelligent-inspection
description: |
Run KaiwuDB inspection and health-check tasks. Use this skill for database health checks, metrics collection, anomaly detection, and inspection report generation.
triggers:
- show me all database metrics
- database metrics for my KWDB cluster
- kwdb cluster metrics
- check database health
- inspect KWDB cluster
- database health check
- collect database metrics
- kwdb inspection
- 巡检
- 数据库指标
- 查看数据库指标
- 检查数据库健康
---

## Critical Constraints (non-negotiable)

❝ **Never skip Step 1.** Collecting metrics before confirming node addresses, ports, and inspection scope with the user is forbidden. The inspection must not proceed until the user explicitly confirms the node addresses, ports, and inspection scope. ❞

❝ **Never call a script without reading its usage doc first.** Before running any script under `scripts/`, you MUST read the corresponding `references/*-script-usage.md` file. This is the only way to know the correct parameters, defaults, and required arguments. Guessing parameters is forbidden. ❞

❝ **Anomaly rules are user-driven.** If user does not request alerting, skip alerting. If user requests alerting without specific thresholds, apply default rules from `references/anomaly-rules.md`. If user provides custom thresholds, use those instead. ❞

## Workflow

### Step 1: Confirm target and scope

**Before collecting any metrics**, follow `references/inspection-requirements-confirmation.md` EXACTLY in order:
1. Parse user intent → confirm target (host, ports)
2. Probe connectivity → verify ports reachable (see `references/inspection-port-listening-reference.md`)
3. TLS mode detection → determine if inspection supported
4. Present scope menu → user confirms before proceeding

### Step 2: Collect metrics

**MANDATORY: Read the script usage doc BEFORE calling any script.**
- `references/ts-metrics-script-usage.md` — for `get_kwdb_ts_metrics.py`
- `references/statements-script-usage.md` — for `get_kwdb_statements.py`

Do not call any script without first reading its usage doc. Verify the parameter names, required arguments, and defaults match what you are about to pass.

- **Port listener status**: Use Step 1 connectivity probe results.
- **Most metrics**: Use `scripts/get_kwdb_ts_metrics.py` per `references/ts-metrics-script-usage.md`.
- **Slow queries**: Use `scripts/get_kwdb_statements.py` per `references/statements-script-usage.md`.

### Step 3: Apply anomaly rules

Apply anomaly judgment rules only when user requests alerting. See `references/anomaly-rules.md` for default rules and configurable rules.

### Step 4: Generate report

Produce a Markdown inspection report with metric values, anomaly judgments, and data-source notes per `references/output-rules.md`.

## Anomaly Rules

See `references/anomaly-rules.md` for default rules and configurable rules.

## Output Rules

See `references/output-rules.md` — **do not deviate from these rules when producing any inspect

_meta.json

{
  "ownerId": "kn7fr8q8f22jd6gzb6f7prf9g183z64v",
  "slug": "kwdb-intelligent-inspection",
  "version": "1.2.1",
  "publishedAt": 1787878056030
}

references/anomaly-rules.md

## Anomaly Rules

These rules apply only when the user requests alerting. If no alerting is requested, skip all rules.

### Default Rules (applied when user requests alerting without custom thresholds)

1. **Database Down**: `cr.node.liveness.livenodes == 0` or port listener check failure
2. **Port Anomaly**: Port 26257 or 8080 not listening
3. **Frequent Restarts**: Database restarts > 1 time/day
4. **Replica sync lag > 5s**: `cr.store.raft.replica.consistent.latency-p99` via `/ts/query` API
5. **Unavailable Replicas > 0**: `cr.store.ranges.unavailable` via `/ts/query` API — ranges with fewer replicas than quorum requires

### Configurable Rules (require explicit user threshold)

- **CPU > threshold%**: `cr.node.sys.cpu.combined.percent-normalized`
- **Memory > threshold%**: `cr.node.sys.rss`
- **QPS anomaly**: requires sampling window, do not claim from single snapshot
- **Write/Query latency anomaly**: requires sampling window, do not claim from single snapshot

references/inspection-port-listening-reference.md

# Port Listening Detection Reference

This document describes how to check KaiwuDB port reachability status.

## Critical Constraint (non-negotiable)

**Do not SSH into the target server to run inspection commands there.** Always use local tools on the machine where the inspection is being performed. Only use remote port probing tools (`nc`, `telnet`, `curl`, `wget`) to check if KaiwuDB ports are reachable on target servers.

## Default Ports

| Service | Default Port | Description |
|---------|-------------|-------------|
| SQL Port | `26257` | KaiwuDB SQL/API port |
| Admin Console | `8080` | Admin UI port |

## Supported Detection Methods

Use remote port probing tools to check if KaiwuDB ports are listening on target servers. Common tools:

- **All platforms**: `nc` (netcat), `telnet`
- **For HTTP ports**: `curl`, `wget`

## Tool Installation

If the required port detection tool is not available on the local system:

1. **Do NOT install tool automatically** — always request user permission first
2. Explain to the user which tool is missing and why it is needed
3. Ask for explicit confirmation before proceeding with installation
4. Only after user approval, proceed with installation using system package manager

Example prompt when tool is missing:
```
[TOOL_MISSING] The port probing tool 'nc' is not installed on this system.
Required for: Checking if KaiwuDB ports (26257, 8080) are reachable on target server.
Do you want me to install it? (y/n)
```

## Example Commands

### Using `nc` (netcat)
```bash
nc -zv <target_host> 26257 8080 -w 5
```

### Using `telnet`
```bash
echo "quit" | telnet <target_host> 26257
```

### Using `curl` (for HTTP ports)
```bash
curl -s -o /dev/null -w "%{http_code}" --connect-timeout 5 http://<target_host>:8080
```

### Using `wget` (for HTTP ports)
```bash
wget --spider --timeout=5 -q http://<target_host>:8080
```

## Expected Output

The inspection should verify:
1. Whether each port is reachable (open/closed)
2. Connection response time (if available)

## Output Format

Report the port reachability status:
```json
{
  "port": 26257,
  "reachable": true,
  "response_time_ms": 12
}
```

references/inspection-requirements-confirmation.md

## Inspection Requirements Confirmation

⚠️ **These steps MUST be executed in the following order. Do not skip or reorder any step.**

### Step 1: Parse User Intent

When user provides a target (e.g., "inspect 10.110.10.146 26257 8080"), extract and confirm:
- Node address(es)
- Database port (default 26257)
- Admin console port (default 8080)

**Do NOT proceed to Step 2 until target info is confirmed with user.**

---

### Step 2: Probe Connectivity

After confirming target info with user, verify reachability using appropriate tools (e.g., `nc`, `telnet`, `curl`, `ping`):
- Check database port (26257) and admin console port (8080)
- If ports unreachable: inform user and ask them to verify network/firewall/service
- Only proceed if ports are reachable

**Do NOT proceed to Step 3 until ports are confirmed reachable.**

---

### Step 3: TLS Mode Detection

Only after connectivity is confirmed, check TLS status:

**Must strictly use this exact command format, only replace `<host>` and `<admin-port>` with actual values:**
```
curl -k https://<host>:<admin-port>/health
```
- If output contains `error:0A00010B` or `wrong version number` → TLS not enforced, proceed
- If returns JSON health data with no error → TLS enabled, **inspection not supported** (stop here)

**Do NOT proceed to Step 4 until TLS mode is determined.**

---

### Step 4: Present Scope Menu

Read `references/report-template.md` and `references/anomaly-rules.md`, then show user:
- Full inspection scope (Sections 1-6)
- Default rules and configurable rules (only applied if user requests alerting)
- Ask user to confirm which metrics to inspect and whether to enable alerting

**Do NOT proceed to metrics collection until user confirms the scope.**

Github ReposUpdated 1d agoRank 70

AionUi

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!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

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

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.