Delegating to Otto

Otto is Astronomer's data-engineering agent, bundled with the Astro CLI as astro otto. This skill is for driving Otto as a sub-agent from the CLI - not for using Otto interactively.

If you are Otto, stop here. Otto already bundles Astronomer's Airflow skills. Never spawn astro otto from inside Otto.

Routine staging/prod inspection in this catalog stays on vd:astro-airflow (af / astro deployment / curl). Use this skill when the user names Otto, for Airflow 2→3 upgrade planning, or for a long self-contained audit that would burn parent context.

When to delegate

Do:

• Airflow 2→3 upgrades / runtime / provider compatibility (Otto's compatibility KB; pass --persona airflow-upgrade for upgrade work)
• Live production diagnosis that should run in its own session
• Long audits, fleet-wide DAG analysis
• Parallel branches via --fork
• Tasks that should inherit .astro/memory/

Don't: