メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
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.
| name | dalgo-ingestion |
| description | 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. |
Use for source and connection workflows through Dalgo MCP tools.
source_id); a connection syncs a source into the warehouse (connection_id); a pipeline wraps a connection sync plus optional dbt steps. Syncing happens at the connection level.dalgo-pipelines loop), not directly — raw connection triggering is not exposed as a tool.dalgo_get_sync_history if you didn't.dalgo_delete_source; it is irreversible and breaks dependent connections.dalgo-pipelines trigger-poll-verify loop.dalgo_list_connections → dalgo_get_sync_history(connection_id) → report the latest run's status, time, and records synced.dalgo_get_connection_catalog(connection_id) for streams, sync modes, and enabled state.dalgo_list_source_definitions.dalgo_list_sources → match by name → source_id.dalgo_list_connections → connection(s) referencing that source.dalgo-pipelines. Checking: dalgo_get_sync_history.