airbyte-cloud-airflow-to-orchestraUse this skill when the user wants to convert an Airflow task that uses AirbyteTriggerSyncOperator or AirbyteSensor (apache-airflow-providers-airbyte) into an equivalent Orchestra pipeline task targeting Airbyte Cloud. Triggers: any mention of migrating, converting, or rewriting Airflow Airbyte task
airbyte-cloud-dagster-to-orchestraUse this skill when the user wants to convert a Dagster integration that syncs Airbyte Cloud — AirbyteCloudResource, build_airbyte_assets, load_airbyte_cloud_asset_specs, or airbyte_assets — into an equivalent Orchestra pipeline task targeting Airbyte Cloud. Triggers: any mention of migrating or rew
airbyte-cloud-prefect-to-orchestraUse this skill when the user wants to convert a Prefect task that syncs Airbyte Cloud — AirbyteConnection block, trigger_sync_run_and_wait_for_completion, or AirbyteSyncResult — into an equivalent Orchestra pipeline task targeting Airbyte Cloud. Triggers: any mention of migrating or rewriting Prefec
airbyte-server-airflow-to-orchestraUse this skill when the user wants to convert an Airflow task that uses AirbyteTriggerSyncOperator or AirbyteSensor pointed at a self-hosted Airbyte Server instance into an equivalent Orchestra pipeline task. Triggers: any mention of migrating or converting Airflow self-hosted Airbyte tasks to Orche
airbyte-server-dagster-to-orchestraUse this skill when the user wants to convert a Dagster integration that syncs a self-hosted Airbyte Server (open-source / OSS) instance — AirbyteResource (with host/port) plus build_airbyte_assets — into an equivalent Orchestra pipeline task. Triggers: any mention of migrating self-hosted Airbyte D
airbyte-server-prefect-to-orchestraUse this skill when the user wants to convert a Prefect task that syncs a self-hosted Airbyte Server — AirbyteConnection block, trigger_sync_run_and_wait_for_completion, or AirbyteSyncResult pointed at a non-Cloud host — into an equivalent Orchestra pipeline task targeting Airbyte Server. Triggers:
airflow-alerts-to-orchestraUse this skill when an Airflow DAG uses on_failure_callback, on_success_callback, on_retry_callback, sla_miss_callback, EmailOperator, PagerDutyEventsHook, or any notification/alerting pattern. Covers all seven Orchestra alert destination types: SLACK, EMAIL, PAGER_DUTY, MICROSOFT_TEAMS, GOOGLE_CHAT
airflow-bash-ssh-to-orchestraUse this skill when an Airflow DAG contains BashOperator (non-dbt), SSHOperator (non-dbt), WinRMOperator, or KubernetesPodOperator. Triggers: any task using bash_command= that isn't running dbt, any task using ssh_conn_id= that isn't running dbt, any KubernetesPodOperator or DockerOperator. Note: Ba
airflow-conditions-to-orchestraUse this skill when an Airflow DAG contains conditional execution logic: trigger_rule (all_done, one_failed, none_failed, one_success, none_skipped), BranchPythonOperator, ShortCircuitOperator, or LatestOnlyOperator. Triggers: any Airflow task with a non-default trigger_rule; any DAG using branching
airflow-connections-to-orchestraUse this skill when converting Airflow code that references credentials via Airflow's connection system: any operator/hook kwarg ending in `_conn_id` (conn_id=, aws_conn_id=, snowflake_conn_id=, ssh_conn_id=, slack_conn_id=, gcp_conn_id=, http_conn_id=), any `BaseHook.get_connection(...)` or `Connec
airflow-cross-dag-to-orchestraUse this skill when an Airflow DAG uses TriggerDagRunOperator, ExternalTaskSensor, or SubDagOperator to create cross-DAG dependencies or trigger downstream pipelines. Triggers: any DAG with external_dag_id=, trigger_dag_id=, SubDagOperator, or Airflow Datasets.
airflow-dag-structure-to-orchestraUse this skill when converting any Airflow DAG to Orchestra YAML to handle DAG-level configuration. Triggers: any Airflow DAG definition containing schedule_interval, default_args, max_active_runs, catchup, params, start_date, or DAG-level tags. Must be applied before converting individual tasks — i
airflow-dynamic-task-mapping-to-orchestraUse this skill when an Airflow DAG uses dynamic task mapping — task.expand(param=[...]), task.expand(param=XComArg(...)), task.partial(...).expand(...), or expand_kwargs() (Airflow 2.3+) — to create a variable number of task instances at runtime from a list, dict, or an upstream task's output. Trigg
airflow-sensors-to-orchestraUse this skill when an Airflow DAG contains sensor operators: S3KeySensor, FileSensor, SqlSensor, ExternalTaskSensor, TimeSensor, or any *Sensor class. Triggers: any DAG with poke_interval, mode='reschedule', or sensor-based waiting patterns. Sensors in Orchestra are first-class pipeline triggers de
airflow-testing-to-orchestraUse this skill when an Airflow DAG contains data quality or testing operators: SqlCheckOperator, SQLThresholdCheckOperator, GreatExpectationsOperator, SodaCheckOperator, DbtTestOperator, or any custom SQL assertion task. Triggers: any task with sql= parameter used for validation, any use of Great Ex
airflow-xcoms-to-orchestraUse this skill when an Airflow DAG uses xcom_push, xcom_pull, or the TaskFlow API @task return values to pass data between tasks. Triggers: any DAG with ti.xcom_push(), context['ti'].xcom_pull(), @task decorated functions that return values, or BranchPythonOperator decisions driven by upstream XCom
dagster-alerts-to-orchestraUse this skill when a Dagster project sends notifications: @run_failure_sensor, @run_status_sensor, make_email_on_run_failure_sensor, make_slack_on_run_failure_sensor, PagerDuty/Teams/Datadog resources used in hooks or sensors, or @failure_hook/@success_hook. Covers all seven Orchestra alert destina
dagster-asset-checks-to-orchestraUse this skill when a Dagster project contains data quality / testing logic: @asset_check, asset checks with AssetCheckResult, build_metadata_bounds_checks, dbt tests run via dagster-dbt, dagster-pandera / dagstermill expectations, or ExpectationResult. Triggers: any @asset_check decorated function,
dagster-branching-to-orchestraUse this skill when a Dagster job/graph contains conditional execution logic: ops with multiple Out/branching outputs that are conditionally yielded, @op functions that decide which downstream op runs, DynamicOut fan-out used for branching, or conditional asset materialization (AutomationCondition /
dagster-connections-to-orchestraUse this skill when converting Dagster code that references resources holding credentials (ConfigurableResource subclasses, EnvVar, integration resources like SnowflakeResource / S3Resource / DbtCliResource, or resources wired into Definitions) to Orchestra. Triggers: any Dagster resource that store
dagster-cross-job-to-orchestraUse this skill when a Dagster project creates dependencies between jobs/code locations or triggers downstream runs: @run_status_sensor (on SUCCESS) yielding RunRequest, @asset_sensor watching another job's asset, cross-code-location asset dependencies (SourceAsset / AssetKey across locations), or a
dagster-definitions-to-orchestraUse this skill when converting any Dagster job/schedule/Definitions to Orchestra YAML to handle top-level configuration. Triggers: any Dagster code containing ScheduleDefinition, @schedule, build_schedule_from_partitioned_job, RetryPolicy, op/run concurrency limits, run tags (dagster/max_runtime), C
dagster-io-managers-to-orchestraUse this skill when a Dagster project passes data between ops/assets via return values, Out/In wiring, IO managers, or context.add_output_metadata, and you need that data flow represented in Orchestra. Triggers: any op/asset that returns a value consumed downstream, any custom or built-in IOManager,
dagster-sensors-to-orchestraUse this skill when a Dagster project contains sensors that watch external state and trigger runs: @sensor, @asset_sensor, @multi_asset_sensor, build_sensor_for_freshness_checks, or sensors polling S3/files/tables. Triggers: any @sensor that yields RunRequest based on external state (a file arriving
dagster-shell-ssh-to-orchestraUse this skill when a Dagster project shells out or runs containers (non-dbt): PipesSubprocessClient / open_pipes_session, dagster-shell (execute_shell_command / create_shell_command_op), SSHResource (dagster-ssh) running remote commands, k8s_job_op / PipesK8sClient, PipesECSClient, or PipesDatabric
dbt-core-airflow-to-orchestraUse this skill when the user wants to convert an Airflow task that runs dbt Core commands — via BashOperator, SSHOperator, PythonOperator, KubernetesPodOperator, or Astronomer Cosmos — into an equivalent Orchestra pipeline task. Triggers: any mention of migrating or rewriting dbt Core Airflow tasks
dbt-core-dagster-to-orchestraUse this skill when the user wants to convert a Dagster dbt integration — DbtCliResource, @dbt_assets, dbt_assets, build_dbt_asset_selection, or DbtProject — into an equivalent Orchestra pipeline task. Triggers: any mention of migrating or rewriting Dagster dbt assets to Orchestra; Dagster code impo
dbt-core-prefect-to-orchestraUse this skill when the user wants to convert a Prefect task that runs dbt Core commands — DbtCoreOperation block, ShellOperation running dbt CLI, run_dbt_build / run_dbt_test tasks, or DbtCloudJob — into an equivalent Orchestra pipeline task. Triggers: any mention of migrating or rewriting Prefect
fivetran-airflow-to-orchestraUse this skill when the user wants to convert an Airflow task that uses FivetranOperator or FivetranSensor (apache-airflow-providers-fivetran) into an equivalent Orchestra pipeline task. Triggers: any mention of migrating or rewriting Fivetran Airflow tasks to Orchestra; Airflow DAG code containing
fivetran-dagster-to-orchestraUse this skill when the user wants to convert a Dagster Fivetran integration — FivetranResource / FivetranWorkspace, build_fivetran_assets, load_fivetran_asset_specs, or fivetran_assets — into an equivalent Orchestra pipeline task. Triggers: any mention of migrating or rewriting Dagster Fivetran ass
fivetran-prefect-to-orchestraUse this skill when the user wants to convert a Prefect task that syncs Fivetran — FivetranConnector block, trigger_sync_and_wait_for_completion, or FivetranSyncResult — into an equivalent Orchestra pipeline task. Triggers: any mention of migrating or rewriting Prefect Fivetran tasks to Orchestra; a
powerbi-airflow-to-orchestraUse this skill when the user wants to convert an Airflow task that uses PowerBIDatasetRefreshOperator (apache-airflow-providers-microsoft-azure, module airflow.providers.microsoft.azure.operators.powerbi) into an equivalent Orchestra pipeline task targeting Power BI. Triggers: any mention of migrati
powerbi-dagster-to-orchestraUse this skill when the user wants to convert a Dagster Power BI integration — PowerBIWorkspace, PowerBIServicePrincipal/PowerBIToken, load_powerbi_asset_specs, build_semantic_model_refresh_asset_definition, or a custom resource/op calling power_bi.trigger_and_poll_refresh — into an equivalent Orche
powerbi-prefect-to-orchestraUse this skill when the user wants to convert a Prefect @task that refreshes a Power BI dataset (semantic model) or dataflow — typically using msal/requests against the Power BI REST API, or a custom PowerBIBlock/ConfigurableResource wrapping it — into an equivalent Orchestra pipeline task targeting
prefect-alerts-to-orchestraUse this skill when a Prefect project sends notifications: @flow(on_failure=...) or @flow(on_completion=...) hooks, Prefect Automation notification actions (Slack, email, Teams, PagerDuty), SlackWebhook block notifications, or MicrosoftTeamsWebhook block notifications. Covers all seven Orchestra ale
prefect-automations-to-orchestraUse this skill when a Prefect project uses Automations to trigger flow runs based on external events — storage events (S3/GCS file arrivals), database polling, scheduled automations, or webhook-triggered deployments. Triggers: any Prefect Automation watching external state, any flow.serve() with eve
prefect-conditions-to-orchestraUse this skill when a Prefect flow contains conditional execution logic: tasks that only run based on the result of upstream tasks, if/else branches driven by task return values, allow_failure=True patterns, or conditional .submit() calls. Triggers: any Prefect flow with if/else branching on task ou
prefect-connections-to-orchestraUse this skill when converting Prefect code that references blocks holding credentials (SnowflakeCredentials, AwsCredentials, SlackWebhook, or any other loaded via Block.load()), Secret blocks, or environment-variable-based credentials to Orchestra. Triggers: any Prefect block that stores host/login
prefect-cross-flow-to-orchestraUse this skill when a Prefect flow triggers another deployment using run_deployment(), or when a flow is called as a subflow from a parent @flow. Triggers: any Prefect code with run_deployment(), await run_deployment(), or a @flow function called inside another @flow (subflow pattern).
prefect-data-passing-to-orchestraUse this skill when a Prefect flow passes data between tasks via return values (.result()), task.submit() futures, Prefect Artifacts, or .map() for fan-out. Triggers: any Prefect flow where a downstream task consumes the return value of an upstream task, any .map() usage, any Prefect Artifact that i
prefect-flow-structure-to-orchestraUse this skill when converting any Prefect flow to Orchestra YAML to handle flow-level configuration. Triggers: any Prefect flow definition containing @flow, schedule= (CronSchedule, IntervalSchedule, RRuleSchedule), retries=, timeout_seconds=, flow.deploy() or flow.serve() deployment config, flow p
prefect-secrets-to-orchestraUse this skill when the user has Prefect Secret blocks, SecretStr fields, SecretDict, or prefect.blocks.system.Secret usage to move into Orchestra. Triggers: any Prefect code using Secret.load(), .get_secret_value(), SecretStr type annotations, or external secret-store blocks (AWS Secrets Manager, A
prefect-testing-to-orchestraUse this skill when a Prefect flow contains data quality or testing logic: @task functions that run SQL assertions, Great Expectations checkpoints called from a @task, Soda check tasks, or threshold checks that raise exceptions on failure. Triggers: any Prefect @task that queries a database to valid
python-airflow-to-orchestraUse this skill when the user wants to convert an Airflow task that uses PythonOperator or PythonVirtualenvOperator into an equivalent Orchestra Python pipeline task. Triggers: any mention of migrating or rewriting PythonOperator tasks to Orchestra; Airflow DAG code using PythonOperator, PythonVirtua
python-dagster-to-orchestraUse this skill when the user wants to convert a Dagster @op or @asset that runs arbitrary Python (computation, API calls, pandas, boto3) into an equivalent Orchestra Python pipeline task. Triggers: any mention of migrating or rewriting Dagster ops/assets to Orchestra; plain @op / @asset / @multi_ass
python-prefect-to-orchestraUse this skill when the user wants to convert a Prefect @task function containing arbitrary Python logic (computation, API calls, pandas, boto3, etc.) into an equivalent Orchestra Python pipeline task. Triggers: any mention of migrating or rewriting Prefect @task functions to Orchestra; Prefect flow
slack-airflow-to-orchestraUse this skill when the user wants to convert an Airflow task that uses SlackAPIOperator, SlackWebhookOperator, or SlackAPIPostMessageOperator — or Airflow on_failure_callback / on_success_callback functions that send Slack messages — into an equivalent Orchestra pipeline alert or task. Also covers
slack-dagster-to-orchestraUse this skill when the user wants to convert Dagster Slack notifications — SlackResource, make_slack_on_run_failure_sensor, make_slack_on_freshness_policy_status_change_sensor, or op success/failure hooks that post to Slack — into an equivalent Orchestra pipeline alert or task. Triggers: any mentio
slack-prefect-to-orchestraUse this skill when the user wants to convert Prefect Slack notifications into an equivalent Orchestra pipeline alert or task. This covers both hook-based notifications — SlackWebhook block, @flow on_failure/on_completion hooks, Prefect Automation Slack notifications — AND explicit mid-flow Slack me
tableau-airflow-to-orchestraUse this skill when the user wants to convert an Airflow task that uses TableauOperator or TableauRefreshWorkbookOperator (apache-airflow-providers-tableau) into an equivalent Orchestra pipeline task targeting Tableau Cloud. Triggers: any mention of migrating or rewriting Tableau Airflow tasks to Or
tableau-dagster-to-orchestraUse this skill when the user wants to convert a Dagster Tableau integration — TableauCloudWorkspace, TableauServerWorkspace, load_tableau_asset_specs, or build_tableau_materializable_assets_definition — into an equivalent Orchestra pipeline task targeting Tableau Cloud. Triggers: any mention of migr
tableau-prefect-to-orchestraUse this skill when the user wants to convert a Prefect @task that refreshes a Tableau workbook or extract — using tableau-server-client (TSC) library, RefreshWorkbookRequest, or ScheduleItem — into an equivalent Orchestra pipeline task targeting Tableau Cloud. Triggers: any mention of migrating Tab