fcakyon/claude-codex-settings / plugins/hetzner-skills/skills/hetzner-deploy
hetzner-deploy
VerifiedThis skill should be used when user asks to "deploy to Hetzner", "create Hetzner server", "manage Hetzner Cloud", "hcloud CLI", or works with Hetzner Cloud infrastructure including servers, networks, firewalls, load balancers, DNS zones, and volumes.
references/getting-started/output-options.md
View on GitHub<!--
---
date: "2026-09-07"
date_changed: "2026-09-07"
title: "Output options"
tags: []
language: "en"
description: ""
docs_type: ["how_to"]
product_category: ["Integrations"]
translation: ["Integrations", "CLI", "Guides", "Output options"]
scrape_type: "whole"
priority: 100
---
-->
# Using output options
The CLI allows you to customize the output format of some commands using the `--output` flag.
This guide shows you how to use this feature and use it in combination with other tools.
## JSON
`describe`, `list` and `create` commands support JSON output format. To use it, simply add the `--output json` flag to your command.
For example, to get the details of a location in JSON format, you can use the following command:
```bash
$ hcloud location describe fsn1 --output json
{
"id": 1,
"name": "fsn1",
"description": "Falkenstein DC Park 1",
"country": "DE",
"city": "Falkenstein",
"latitude": 50.47612,
"longitude": 12.370071,
"network_zone": "eu-central"
}
```
You can combine this with other tools to process the output. For example, you can use `jq` to filter the output:
```bash
$ hcloud location describe fsn1 --output json | jq '.name'
"fsn1"
```
```bash
$ hcloud location describe fsn1 --output json | jq '{id, name}'
{
"id": 1,
"name": "fsn1"
}
```
`list` commands return a list of objects in JSON format. For example, to get a list of all locations in JSON format, you can use the following command:
```bash
$ hcloud location list --output json
[
{
"id": 1,
"name": "fsn1",
"description": "Falkenstein DC Park 1",
"country": "DE",
"city": "Falkenstein",
"latitude": 50.47612,
"longitude": 12.370071,
"network_zone": "eu-central"
},
{
"id": 2,
"name": "nbg1",
"description": "Nuremberg DC Park 1",
"country": "DE",
"city": "Nuremberg",
"latitude": 49.452102,
"longitude": 11.076665,
"network_zone": "eu-central"
},
...
]
```
Once again, you can use `jq` to filter the output. Following example shows how to get the names of all locations of which the network zone is `eu-central`:
```bash
$ hcloud location list --output json | jq '[.[] | select(.network_zone == "eu-central") | .name]'
[
"fsn1",
"nbg1",
"hel1"
]
```
## YAML
`describe`, `list` and `create` commands support YAML output format as well.
```bash
$ hcloud location describe fsn1 --output yaml
id: 1
name: fsn1
description: Falkenstein DC Park 1
country: DE
city: Falkenstein
latitude: 50.47612
longitude: 12.370071
network_zone: eu-central
```
For YAML, you can use `yq` instead of `jq`.
```bash
$ hcloud location list --output yaml | yq '.[] | [{"id": .id, "name": .name}]'
- id: 1
name: fsn1
- id: 2
name: nbg1
- id: 3
name: hel1
- id: 4
name: ash
- id: 5
name: hil
- id: 6
name: sin
```
## Go Template Format
`describe` commands support the Go string template format as well. You can read up on the syntax in the
[Go documentation](https://pkg.go.dev/text/template). The data structures passed to the template are defined
by our API and can be found in [hcloud-go](https://pkg.go.dev/github.com/hetznercloud/hcloud-go/v2/hcloud/schema).
For example, you could obtain the number of cores of a server using the following command:
```bash
$ hcloud server describe my-server --output format='{{.ServerType.Cores}}'
2
```
## Table options
`list` commands support table options as well. These options allow you to customize the output format of the output table,
if not using JSON or YAML.
> [!NOTE]
> You can also combine both of the below options to use them at once: `--output noheader --output columns=id,name,network_zone`
### noheader
This option removes the header from the output table.
```bash
$ hcloud location list --output noheader
1 fsn1 Falkenstein DC Park 1 eu-central DE Falkenstein
2 nbg1 Nuremberg DC Park 1 eu-central DE Nuremberg
3 hel1 Helsinki DC Park 1 eu-central FI Helsinki
4 ash Ashburn, VA us-east US Ashburn, VA
5 hil Hillsboro, OR us-west US Hillsboro, OR
6 sin Singapore ap-southeast SG Singapore
```
### columns
This option allows you to filter by columns.
```bash
$ hcloud location list --output columns=id,name,network_zone
ID NAME NETWORK ZONE
1 fsn1 eu-central
2 nbg1 eu-central
3 hel1 eu-central
4 ash us-east
5 hil us-west
6 sin ap-southeast
```
Using the `--help` flag will show you a list of all available columns for this command. Note that these might include
more than the default columns.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |