Skip to main content
skill CX Codex

authoring-go-sdk-tasks — Claude Code skill: what it does and install

authoring-go-sdk-tasks helps author Apache Airflow task logic in Go using the Airflow Go SDK. Useful when moving compute logic from Python into compiled Go binaries.

Apache-2.0 217 installs ★ 463 updated 2026-10-14

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add astronomer/agents --skill authoring-go-sdk-tasks -a claude-code
Open on GitHub

What authoring-go-sdk-tasks does

This skill guides the agent in writing native Go task code with the github.com/apache/airflow/go-sdk module. DAG graphs remain defined in Python via @task.stub, while task execution runs inside a standalone Go bundle managed by bundlev1.BundleProvider and bundlev1server.Serve.

Task functions use type-based dependency injection. The runtime inspects function parameters and injects values such as context.Context, sdk.TIRunContext, *slog.Logger, or clients like sdk.Client, sdk.VariableClient, and sdk.ConnectionClient. A non-nil return value is automatically pushed as the task XCom return_value.

The Airflow Go SDK is experimental and requires Go 1.24 or later before you build your bundle executables.

What it helps with

  • register Go task functions with Python DAG stubs using bundlev1
  • inject sdk.TIRunContext and logger dependencies by parameter type
  • retrieve Airflow connections and variables within Go routines
  • route function return values directly into task XComs

Example prompts for the agent

  • Write an Airflow extract task in Go using sdk.Client and *slog.Logger
  • Implement a bundlev1.BundleProvider entrypoint for simple_dag
  • Show how to read a JSON variable using UnmarshalJSONVariable in Go

How to install authoring-go-sdk-tasks

1Skills CLI (Vercel)

npx skills add astronomer/agents --skill authoring-go-sdk-tasks -a claude-code

2Manually: put the files in place

~/.claude/skills/authoring-go-sdk-tasks/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/authoring-go-sdk-tasks/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about authoring-go-sdk-tasks

How to install authoring-go-sdk-tasks in Claude Code?

Run npx skills add astronomer/agents --skill authoring-go-sdk-tasks -a claude-code in your terminal.

What does authoring-go-sdk-tasks do?

It guides the agent in writing native Go task implementations, registering them in bundles, and injecting runtime contexts.

What Go version is required for the Airflow Go SDK?

It requires Go 1.24+ because the github.com/apache/airflow/go-sdk package is experimental and under active development.

Source text

SKILL.md · Apache-2.0
---
name: authoring-go-sdk-tasks
description: Writes Airflow task logic in Go using the Airflow Go SDK. Use when the user wants to implement Airflow tasks in Go, asks about `BundleProvider`/`RegisterDags`, the `bundlev1` Registry/Dag interfaces, registering Go tasks (`AddTask`/`AddTaskWithName`), dependency injection by parameter type (`context.Context`, `sdk.TIRunContext`, `*slog.Logger`, `sdk.Client`), or reading connections/variables/XComs from Go. This skill covers the Go-specific native API; the shared Python-stub pattern and conceptual model live in authoring-language-sdk-tasks. For building/packing/shipping the bundle see deploying-go-sdk-bundles; for coordinator config see configuring-airflow-language-sdks.
---

# Authoring Go SDK Tasks

The Airflow Go SDK implements the language-SDK model for Go: your DAG stays in Python, and each task is a compiled Go function registered inside a **bundle** (a single native executable). This skill covers the **Go-specific** native API. The shared model (the Python `@task.stub` pattern, ID matching, the XCom-as-JSON contract) lives in **authoring-language-sdk-tasks**; read that first if you are new to language SDKs.

> **Experimental.** The Go SDK is under active development and not production-ready. Module path `github.com/apache/airflow/go-sdk` (Go 1.24+). APIs may change.

> **Related skills:** **authoring-language-sdk-tasks** (shared Python stub + concepts), **deploying-go-sdk-bundles** (build, pack, and ship the bundle), **configuring-airflow-language-sdks** (route the queue to the Go coordinator).

---

## Recap: the Python side

A Go task is paired with a Python stub that carries no logic; it declares the task, its queue, and the dependency graph. IDs must match the Go registration exactly, and `queue=` routes the task to the Go runtime. Full rules are in **authoring-language-sdk-tasks**; the minimal shape:

```python
from airflow.sdk import dag, task


@task.stub(queue="golang")
def extract(): ...


@task.stub(queue="golang")
def transform(): ...


@dag()
def simple_dag():
    extract() >> transform()


simple_dag()
```

The `queue` value (`"golang"` here) is an arbitrary label that must match the queue routed to the Go coordinator (`queue_to_coordinator`). See **configuring-airflow-language-sdks**.

---

## The bundle entry point

A bundle implements `bundlev1.BundleProvider`: report its version and register your DAGs and tasks. `main` is one line; `bundlev1server.Serve` wires the bundle to the Airflow runtime for you.

```go
package main

import (
	"log"

	v1 "github.com/apache/airflow/go-sdk/bundle/bundlev1"
	"github.com/apache/airflow/go-sdk/bundle/bundlev1/bundlev1server"
)

type myBundle struct{}

var _ v1.BundleProvider = (*myBundle)(nil)

func (m *myBundle) GetBundleVersion() v1.BundleInfo {
	return v1.BundleInfo{Name: bundleName, Version: &bundleVersion}
}

func (m *myBundle) RegisterDags(dagbag v1.Registry) error {
	simpleDag := dagbag.AddDag("simple_dag")      // dag_id must match the Python @dag name
	simpleDag.AddTask(extract)                    // task_id is the function name; must match the stub
	simpleDag.AddTaskWithName("transform", transform) // or set the task_id explicitly
	return nil
}

func main() {
	if err := bundlev1server.Serve(&myBundle{}); err != nil {
		log.Fatal(err)
	}
}
```

`AddTask(fn)` derives the `task_id` from the Go function's name; use `AddTaskWithName("<task_id>", fn)` when that name can't match the Python stub (an unexported, renamed, or reused function). `RegisterDags` is the single source of truth for task identity: the bundle's manifest (used by the packer and by the coordinator) is generated by running it, never hand-written.

---

## Task functions: dependency injection by parameter type

A task is an ordinary Go function. The runtime inspects its signature and injects arguments **by type**; declare only what you need.

| Parameter type | Injected value |
|----------------|----------------|
| `context.Context` | Task context for cancellation. Always available. |
| `sdk.TIRunContext` | Richer context (embeds `context.Context`) exposing `TaskInstance()` and `DagRun()`. See [Runtime context](#runtime-context). |
| `*slog.Logger` | Logger wired to the Airflow task log. |
| `sdk.Client` | Full Airflow model access: Variables, Connections, XComs. |
| `sdk.VariableClient` / `sdk.ConnectionClient` / `sdk.XComClient` | A narrower slice of `sdk.Client`. Prefer the narrowest you need; it documents intent and is trivial to fake in tests. |

The optional return signature is `(result, error)`: a non-nil `result` is pushed as the task's `return_value` XCom; a non-nil `error` fails the task (which triggers the stub's retry policy). Returning only `error`, or nothing, is also valid.

```go
func extract(ctx sdk.TIRunContext, client sdk.Client, log *slog.Logger) (any, error) {
	conn, err := client.GetConnection(ctx, "test_http")
	if err != nil {
		return nil, err
	}
	log.Info("connected", "host", conn.Host)
	return map[string]any{"go_version": runtime.Version()}, nil
}

func transform(ctx sdk.TIRunContext, client sdk.VariableClient) error {
	val, err := client.GetVariable(ctx, "my_variable")
	if err != nil {
		return err // VariableNotFound (a sentinel error) if absent
	}
	_ = val
	return nil
}
```

---

## The `sdk.Client` surface

| Call | Returns | Notes |
|------|---------|-------|
| `GetVariable(ctx, key)` | `(string, error)` | `VariableNotFound` if absent. |
| `UnmarshalJSONVariable(ctx, key, &ptr)` | `error` | Decode a JSON variable into a struct/pointer. |
| `GetConnection(ctx, connID)` | `(Connection, error)` | `ConnectionNotFound` if absent. |
| `GetXCom(ctx, dagID, runID, taskID, mapIndex, key, value)` | `(any, error)` | `XComNotFound` only if the key is absent; a stored null returns `(nil, nil)`. |
| `PushXCom(ctx, ti, key, value)` | `error` | Rarely needed; a returned value is pushed for you. |

`Connection` exposes `ID`, `Type`, `Host`, `Port` (`int`), `Login *string`, `Password *string` (nil when unset, distinct from empty), `Path` (schema), `Extra map[string]any`, plus `GetURI()`. Not-found cases return the sentinels `sdk.VariableNotFound`, `sdk.ConnectionNotFound`, `sdk.XComNotFound`.

To read an upstream task's result, call `GetXCom` explicitly, taking the `dag_id`/`run_id`/`task_id` you need from the runtime context (below).

---

## Runtime context

Declare an `sdk.TIRunContext` parameter to read metadata about the task instance and its DAG run. It is an interface that embeds `context.Context`, so it is usable anywhere a `context.Context` is expected.

```go
func extract(ctx sdk.TIRunContext, log *slog.Logger) error {
	ti, dagRun := ctx.TaskInstance(), ctx.DagRun()
	log.Info("running",
		"task_id", ti.TaskID,
		"run_id", dagRun.RunID,
		"logical_date", dagRun.LogicalDate)
	return nil
}
```

- `TaskInstance()`: `DagID`, `RunID`, `TaskID`, `MapIndex *int` (nil when unmapped), `TryNumber`.
- `DagRun()`: `DagID`, `RunID`, and the `*time.Time` timestamps `LogicalDate`, `DataIntervalStart`, `DataIntervalEnd` (nil when not sent).

The accessors are populated from the task's startup details before the body runs. Because `TIRunContext` embeds `context.Context`, pass it straight to client calls and cancellation checks (`ctx.Done()`); declare it as your context parameter by default. In tests, build the argument with `sdk.NewTIRunContext(ctx, ti, dagRun)` (it panics on a nil `ctx`).

---

## Go-specific pitfalls

- **IDs must match the Python stub** (`dag_id` from `AddDag`, `task_id` from the registered function name), and the stub's `queue=` must route to the Go coordinator, or the task is never delivered.
- **`RegisterDags` is authoritative.** Do not hand-write the manifest; the packer generates it by running `RegisterDags`.
- **Ask for the narrowest client interface** you need (`sdk.VariableClient` over `sdk.Client`) for clearer intent and easier fakes.
- **A non-nil `error` return fails the task** and applies the stub's retries; a recovered panic is also a failure.
- See **authoring-language-sdk-tasks** for the language-agnostic pitfalls (one process per task instance, set queue and retries on the stub).

---

## Related Skills

- **authoring-language-sdk-tasks**: Shared Python-stub pattern and concepts (read first).
- **deploying-go-sdk-bundles**: Build and pack the bundle with `go tool airflow-go-pack`, then deploy it for the coordinator.
- **configuring-airflow-language-sdks**: Route the queue to the Go coordinator (`ExecutableCoordinator`).
- **authoring-dags**: General Airflow DAG authoring.

© astronomer · Apache-2.0 · astronomer/agents

Similar skills

All skills for Data and databases →

From the same set34

The whole set →
airflow-state-store airflow-state-store — a skill for saving task and asset state across retries and DAG runs in Airflow 3.3+, using built-in key-value stores and a crash-safe mixin for operators that submit jobs to external systems. CX Codex +1 239installs authoring-language-sdk-tasks authoring-language-sdk-tasks guides you through Airflow Language SDKs to run Go or Java tasks while keeping the DAG in Python. Helpful for configuring @task.stub routing and JSON-based XCom. CX Codex +1 220installs configuring-airflow-language-sdks configuring-airflow-language-sdks configures Airflow queues and coordinators for Java and Go SDK tasks. Use it when native tasks are not being routed or picked up by workers. CX Codex +1 219installs deploying-go-sdk-bundles deploying-go-sdk-bundles is a Claude Code skill that builds and packages Go bundles for Airflow and configures their discovery and delivery to workers. It supports deploying Go tasks through ExecutableCoordinator. CX Codex +1 217installs migrating-dagster-to-airflow migrating-dagster-to-airflow is a Claude Code skill that guides step-by-step migration of Dagster and Dagster+ projects to Apache Airflow 3 on Astro Runtime using manifests and asset mapping. CX Codex +1 207installs deploying-java-sdk-bundles deploying-java-sdk-bundles packages compiled Airflow Java SDK bundles as JAR files ready for workers. CX Codex +1 200installs authoring-java-sdk-tasks authoring-java-sdk-tasks — a skill for Claude Code, Codex, Cursor and other agents that covers writing Airflow task logic in Java, Kotlin, or any JVM language via the Airflow Java SDK. CX Codex +1 199installs astronomer-data-agents astronomer-data-agents connects Claude Code to Apache Airflow and data warehouses to inspect DAGs, read task logs, and trace data lineage. ★ 463repo stars

Project sponsors

Companies that keep this analytics open