ClawHub

SQLBot

v1.1.0

Manage SQLBot workspaces, datasources, ask-data flows, and dashboards, including listing and switching workspace or datasource context, asking questions agai...

⭐ 0· 106·0 current·0 all-time
by@xuwei-fit2cloud·duplicate of @xuwei-fit2cloud/sqlboot

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for xuwei-fit2cloud/sqlbot.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "SQLBot" (xuwei-fit2cloud/sqlbot) from ClawHub.
Skill page: https://clawhub.ai/xuwei-fit2cloud/sqlbot
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install sqlbot

ClawHub CLI

Package manager switcher

npx clawhub@latest install sqlbot
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description match the included script and instructions: the skill is a CLI wrapper that lists/switches workspaces and datasources, asks questions, lists and exports dashboards. The script expects SQLBot base URL and API key pair in a .env file — that is appropriate for a service-integrating skill. One minor inconsistency: the registry metadata shows no required env vars, but the SKILL.md and the script clearly require SQLBOT_BASE_URL, SQLBOT_API_KEY_ACCESS_KEY and SQLBOT_API_KEY_SECRET_KEY; this is an omission in the registry metadata rather than a functional mismatch.
ℹ
Instruction Scope
The SKILL.md tells the agent to run the bundled python script under ${CLAUDE_SKILL_DIR} and to check for and use a .env next to the skill. The script will read that .env and may be given a different --env-file. It will make HTTP calls to the configured SQLBot base URL and may invoke Playwright (browser) for exports. The skill also writes a small local state file (default .sqlbot-skill-state.json) to persist current workspace/datasource. It does not instruct the agent to read arbitrary unrelated system files or transmit data to unknown external endpoints — network activity is scoped to SQLBOT_BASE_URL (derived frontend preview URLs are deduced from that base URL).
✓
Install Mechanism
There is no install spec; this is essentially an instruction-only skill that runs the included Python script. No external downloads or remote installers are referenced in SKILL.md. The only optional runtime dependency is Playwright for exports, which the SKILL.md instructs how to install via pip/playwright (a known tool).
ℹ
Credentials
The script legitimately needs SQLBot credentials (base URL, access key, secret key) to call the service; those are requested via a .env file. That is proportionate to the stated functionality. As noted above, the skill registry entry did not declare those env vars as required, so the registry metadata underreports the secrets the skill needs. The script keeps credentials in process memory to sign API requests but does not appear to persist the secrets to disk (it does persist only the workspace/datasource state).
✓
Persistence & Privilege
The skill writes a local state file (by default in the skill directory) to persist current workspace and datasource selection — this is reasonable for its workflow. It does not request always: true and does not modify other skills or global agent configs. SKILL.md sets disable-model-invocation: true (it will not invoke the model autonomously), which reduces risk.
Assessment
This skill appears to do what it says: it runs a local Python script that calls your SQLBot instance and saves a small local state file. Things to consider before installing: - You must supply SQLBOT_BASE_URL and an API key pair in a .env next to the skill (or via --env-file). Only provide these credentials if you trust the SQLBot endpoint and are okay with the skill making signed requests on your behalf. - The skill will write a state file (default .sqlbot-skill-state.json) into the skill directory (or another configured path). If you need isolation, change SQLBOT_STATE_FILE to a safe location. - Exporting dashboards uses Playwright (a browser) and a derived frontend preview URL — the browser will send the same API auth headers to the SQLBot frontend. Install Playwright only if you trust this workflow. - The registry metadata omits the required env vars. Confirm you’re comfortable creating a .env with secrets before enabling the skill. If you want extra assurance, review the full sqlbot_skills.py source locally or run it in an isolated environment/container.

Like a lobster shell, security has layers — review code before you run it.

latestvk97bqraxt8tbjcetkp4zy2vpdd83yjv8
106downloads
0stars
2versions
Updated 4w ago
v1.1.0
MIT-0
@xuwei-fit2cloud
latest
Download

SQLBot Workspace Datasource Dashboard Skill

Use this skill when the user wants to operate SQLBot workspaces, datasources, ask-data flows, or dashboards from Claude Code / Agent Skills compatible tools.

This skill wraps the bundled script ${CLAUDE_SKILL_DIR}/sqlbot_skills.py.

Before you run it

  1. Check whether ${CLAUDE_SKILL_DIR}/.env exists.
  2. If it does not exist, tell the user to copy ${CLAUDE_SKILL_DIR}/.env.example to .env and fill in:
    • SQLBOT_BASE_URL
    • SQLBOT_API_KEY_ACCESS_KEY
    • SQLBOT_API_KEY_SECRET_KEY
  3. For export requests, if Playwright is missing, tell the user to install it with:
pip install playwright
playwright install chromium

Map the user request to one of these commands

  • List workspaces:
python3 "${CLAUDE_SKILL_DIR}/sqlbot_skills.py" workspace list
  • Switch workspace:
python3 "${CLAUDE_SKILL_DIR}/sqlbot_skills.py" workspace switch "<workspace>"
  • List datasources:
python3 "${CLAUDE_SKILL_DIR}/sqlbot_skills.py" datasource list --workspace "<workspace>"
  • Switch datasource:
python3 "${CLAUDE_SKILL_DIR}/sqlbot_skills.py" datasource switch "<datasource>" --workspace "<workspace>"
  • Ask data:
python3 "${CLAUDE_SKILL_DIR}/sqlbot_skills.py" ask "<question>" --datasource "<datasource>" --workspace "<workspace>"

or continue an existing chat:

python3 "${CLAUDE_SKILL_DIR}/sqlbot_skills.py" ask "<question>" --chat-id 101
  • List dashboards:
python3 "${CLAUDE_SKILL_DIR}/sqlbot_skills.py" dashboard list --workspace "<workspace>"

Optional flags:

  • --node-type folder

  • --node-type leaf

  • --flat

  • Show dashboard:

python3 "${CLAUDE_SKILL_DIR}/sqlbot_skills.py" dashboard show "<dashboard-id>" --workspace "<workspace>"
  • Export dashboard:
python3 "${CLAUDE_SKILL_DIR}/sqlbot_skills.py" dashboard export "<dashboard-id>" --workspace "<workspace>" --output "./dashboard.jpg"

or

python3 "${CLAUDE_SKILL_DIR}/sqlbot_skills.py" dashboard export "<dashboard-id>" --workspace "<workspace>" --format pdf --output "./dashboard.pdf"

Execution rules

  • Prefer exact workspace names or numeric workspace IDs when switching or querying.
  • Prefer exact datasource names or numeric datasource IDs when switching or asking.
  • Remember that SQLBot dashboard APIs are scoped by the current workspace and current user, so switch workspace before listing or showing dashboards in another workspace.
  • Datasource list and ask-data also depend on the current workspace context.
  • SQLBot has no standalone datasource-switch API, so datasource switch updates the skill-local state file and ask uses that datasource by default when starting a new chat.
  • Preserve the user's requested output path for exports whenever possible.
  • If the user does not provide an export path, use the script default (./<dashboard-id>.jpg unless another format is specified).
  • Summarize the command output clearly after execution.

Additional resources

  • Detailed usage and installation notes: reference.md
  • Repository overview and manual usage examples: README.md

Comments

Loading comments...