菜单
Show a doctor-style report of the phData Toolkit CLI installation — binary, Java, project, datasources, and optional connectivity. Use when the user asks whether the toolkit is set up, why a toolkit command might be failing, or wants a health check before starting toolkit work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Add or verify a JDBC connection and datasource in toolkit.conf for any supported type — Snowflake, SQL Server, Oracle, Postgres, MySQL, Hive, Databricks, Athena — including JDBC driver installation for non-bundled types and verification via a scoped ds scan. Use when configuring data sources, fixing connection errors, or when toolkit-check reports no datasource.
Configure the optional llmClient block in toolkit.conf so toolkit agent commands (discovery, pipeline-build, fix-sql, codegen ask) can call an LLM — Amazon Bedrock, OpenAI, or Anthropic. Use when agent commands fail for lack of an LLM, when switching providers or models, or when onboarding to the toolkit agent workflows.
Install and configure the phData Toolkit CLI end to end — verify Java, get the toolkit binary on PATH, authenticate, initialize a toolkit project, and extract Data Source tool defaults. Use when the toolkit is missing, toolkit-check fails, or a user is onboarding to phData Toolkit workflows.
Run toolkit agent pipeline-build to generate pipeline code from approved data contracts — SQL, dbt, or PySpark transforms plus data-quality tests and a synthetic-data (datagen) spec. Use after discovery produces contracts, or when the user wants to generate, regenerate, apply, or test pipelines from contracts.
Run toolkit agent discovery to resolve a dataspec against a live datasource into a reviewable data contract, then walk the human-review resolve loop until the contract is approved. Use when the user has (or needs) a dataspec and wants source-to-target mappings, or mentions data contracts, discovery, or humanReviewItems.
Author or validate a DiscoveryConfig dataspec — the YAML describing a target table (columns, grain, business rules, load strategy) consumed by toolkit agent discovery. Use when the user wants to define a new pipeline target, has a dataspec to check, or asks what a dataspec needs to contain.
| name | status |
| description | Show a doctor-style report of the phData Toolkit CLI installation — binary, Java, project, datasources, and optional connectivity. Use when the user asks whether the toolkit is set up, why a toolkit command might be failing, or wants a health check before starting toolkit work. |
Run both helpers and render one readable report:
toolkit-check # layered checks: binary -> project -> datasource
toolkit-setup detect # raw facts: os, java, install path, project, datasources
Present a short table: binary (path + version), Java, project (toolkit.conf path), datasources
(names), and LLM client (llm_client from detect; none means the phData Bedrock fallback for
agent commands). Use the ok/fail lines from toolkit-check as the source of truth and
detect output for the detail values.
If the user wants connectivity verified too (this touches the network and connection-tests the datasource), add:
toolkit-check --level connect --datasource <name>
End with the recommended next step:
fail binary/fail java/fail project → /toolkit-core:setupfail datasource or fail connect → /toolkit-core:connect/toolkit-pipeline:discover) are ready to use.