メニュー
Run, monitor, create, and manage Dalgo orchestration pipelines (Prefect deployments), including the trigger-poll-verify loop. Use whenever a user asks to run a pipeline or check whether one succeeded.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Work with Dalgo data ingestion — Airbyte sources, connections, stream catalogs, and sync history. Use when a user asks to sync a source, check whether a sync ran, or inspect what a connection syncs.
Route Dalgo MCP tool workflows. Use when a request involves Dalgo data, pipelines, syncs, transforms, dashboards, charts, or reports, to pick the right domain skill and stay on MCP tools.
Build and run dbt transformations in Dalgo — the transform canvas, operations, model materialization, dbt runs, and publishing to git. Use when a user asks to run dbt, build or edit models, or modify the transform canvas.
Diagnose Dalgo failures — failed pipeline runs, sync errors, dbt errors — and handle notifications. Use when a user asks why something failed, what went wrong, or what their notifications say.
Create and manage Dalgo charts, dashboards, and reports. Use when a user asks to visualize data, build or modify a dashboard, or snapshot data into a report.
Explore the Dalgo data warehouse — schemas, tables, columns, row counts, and sample data. Use for questions about what data exists or what values a table contains.
SOC 職業分類に基づく
| name | dalgo-pipelines |
| description | Run, monitor, create, and manage Dalgo orchestration pipelines (Prefect deployments), including the trigger-poll-verify loop. Use whenever a user asks to run a pipeline or check whether one succeeded. |
Use for pipeline workflows through Dalgo MCP tools.
dalgo_trigger_pipeline_run only schedules a run — poll dalgo_get_flow_run to a terminal status before reporting the outcome.deployment_id via dalgo_list_pipelines before any detail or mutation call.FAILED, CRASHED, or CANCELLED, fetch dalgo_get_flow_run_logs and quote the actual error before suggesting fixes.dalgo_delete_pipeline; it is irreversible.dalgo_get_pipeline_run_history with limit=1 — do not trigger a new run.dalgo-troubleshooting.COMPLETED, FAILED, CRASHED, CANCELLED. Non-terminal: SCHEDULED, PENDING, RUNNING.flow_run_id for a later check.dalgo_list_pipelines → match by name → deployment_id.dalgo_trigger_pipeline_run(deployment_id) → save flow_run_id; if the trigger errors, report and stop.dalgo_get_flow_run(flow_run_id) until terminal or poll limit.COMPLETED: report success with timing. Failure: fetch logs, show the last ~30 lines, explain the error and a next step.