Authoring Language Sdk Tasks
by astronomercbe1141f547bNo license451 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today
The language-neutral foundation for Airflow language SDKs — implement task logic in a non-Python language while the DAG stays in Python. Use when the user wants to run an Airflow task in another language (Java, Kotlin, Go, or other JVM/native languages), asks how the Python `@task.stub` pairs with native task code, how task/DAG IDs must match across the two sides, how data passes via XCom as JSON, or which language SDKs exist. This skill owns the shared Python-stub pattern and conceptual model; for a specific language's native API, build, and runtime, use that language's skill (e.g. authoring-java-sdk-tasks, authoring-go-sdk-tasks).
Only the file list is public. File contents are available once the skill is installed in a workspace.
| Path | Size | Type |
|---|---|---|
| SKILL.md | 7.2 KB | text/markdown |
Source and attribution
Source:astronomer/agentsinskills/authoring-language-sdk-tasksat commitcbe1141
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from astronomer/agents
Warehouse Init
astronomer
Discovers data warehouse schema metadata and generates a shareable .astro/warehouse.md reference file for fast concept-to-table lookups.
Tracing Upstream Lineage
astronomer
Trace upstream data lineage. Use when the user asks where data comes from, what feeds a table, upstream dependencies, data sources, or needs to understand data origins.
Tracing Downstream Lineage
astronomer
Traces downstream data lineage to assess what breaks when a table or DAG changes.
Testing Dags
astronomer
Guides iterative testing, debugging and fixing of Airflow DAGs using af CLI commands.
Setting Up Astro Project
astronomer
Initializes and configures Astro/Airflow projects with the Astro CLI, covering dependencies, connections, and variables.
Profiling Tables
astronomer
Profiles a database table with SQL statistics, cardinality, samples and a data quality assessment.
More in Software Development
Writing Plans
obra
Use when you have a spec or requirements for a multi-step task, before touching code
Verification Before Completion
obra
Forces running fresh verification commands and reading their output before claiming work is complete, fixed, or passing.
Using Git Worktrees
obra
Sets up an isolated git worktree workspace for feature work, then runs project setup and baseline tests.
Requesting Code Review
obra
Dispatches a code reviewer subagent with crafted context to catch issues before they cascade.
Receiving Code Review
obra
Guides agents receiving code review feedback: verify suggestions, clarify unclear items, push back with technical reasoning, implement fixes one at a time.
Finishing A Development Branch
obra
Guides an agent through finishing a completed development branch: verify tests, choose merge, PR or keep, then clean up.