pp-flight-goat

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Flight Goat — Printing Press CLI

Prerequisites: Install the CLI

前置条件：安装CLI

This skill drives the

flight-goat-pp-cli

binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

Install via the Printing Press installer:

bash

npx -y @mvanhorn/printing-press install flight-goat --cli-only

Verify:
```
flight-goat-pp-cli --version
```
Ensure
```
$GOPATH/bin
```
(or
```
$HOME/go/bin
```
) is on
```
$PATH
```
.

If the

npx

install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.23+):

bash

go install github.com/mvanhorn/printing-press-library/library/travel/flight-goat/cmd/flight-goat-pp-cli@latest

--version

reports "command not found" after install, the install step did not put the binary on

$PATH

. Do not proceed with skill commands until verification succeeds.

本技能基于

flight-goat-pp-cli

二进制文件运行。在调用本技能的任何命令之前，您必须确认CLI已安装。 如果未安装，请先执行以下步骤：

通过Printing Press安装器安装：

bash

npx -y @mvanhorn/printing-press install flight-goat --cli-only

验证安装：
```
flight-goat-pp-cli --version
```
确保
```
$GOPATH/bin
```
（或
```
$HOME/go/bin
```
）已添加到
```
$PATH
```
环境变量中。

如果

npx

安装失败（如无Node环境、离线等），可以使用Go直接安装（需要Go 1.23及以上版本）：

bash

go install github.com/mvanhorn/printing-press-library/library/travel/flight-goat/cmd/flight-goat-pp-cli@latest

如果安装后执行

--version

提示“command not found”，说明安装程序未将二进制文件添加到

$PATH

中。请在验证成功前不要执行技能命令。

Development Tools

开发工具

AeroAPI is defined using the OpenAPI Spec 3.0, which means it can be easily imported into tools like Postman. To get started try importing the API specification using Postman's instructions. Once imported as a collection only the "Value" field under the collection's Authorization tab needs to be populated and saved before making calls.

The AeroAPI OpenAPI specification is located at:
https://flightaware.com/commercial/aeroapi/resources/aeroapi-openapi.yml

Our open source AeroApps project provides a small collection of services and sample applications to help you get started.

The Flight Information Display System (FIDS) AeroApp is an example of a multi-tier application using multiple languages and Docker containers. It demonstrates connectivity, data caching, flight presentation, and leveraging flight maps.

The Alerts AeroApp demonstrates the use of AeroAPI to set, edit, and receive alerts in a sample application with a Dockerized Python backend and a React frontend.

Our AeroAPI push notification testing interface provides a quick and easy way to test the delivery of customized alerts via AeroAPI push.

AeroAPI基于OpenAPI Spec 3.0定义，因此可以轻松导入到Postman等工具中。您可以按照Postman的操作指南导入API规范。导入为集合后，只需在集合的Authorization标签下填充“Value”字段并保存，即可发起调用。

AeroAPI的OpenAPI规范地址为：
https://flightaware.com/commercial/aeroapi/resources/aeroapi-openapi.yml

我们的开源AeroApps项目提供了一组服务和示例应用，帮助您快速上手。

航班信息显示系统（FIDS）AeroApp是一个使用多种语言和Docker容器的多层应用示例，展示了连接性、数据缓存、航班展示以及航班地图的使用。

告警AeroApp展示了如何在一个示例应用中使用AeroAPI设置、编辑和接收告警，该应用包含Docker化的Python后端和React前端。

我们的AeroAPI推送通知测试界面提供了一种快速简便的方式，测试通过AeroAPI推送的定制化告警的交付情况。

Command Reference

命令参考

aircraft — Manage aircraft

```
flight-goat-pp-cli aircraft <type>
```
— Returns information about an aircraft type, given an ICAO aircraft type designator string. Data returned includes...

airports — Manage airports

```
flight-goat-pp-cli airports get
```
— Returns information about an airport given an ICAO or LID airport code such as KLAX, KIAH, O07, etc. Data returned...
```
flight-goat-pp-cli airports get-all
```
— Returns the ICAO identifiers of all known airports. For airports that do not have an ICAO identifier, the FAA LID...
```
flight-goat-pp-cli airports get-delays-for-all
```
— Returns a list of airports with delays. There may be multiple reasons returned per airport if there are multiple...
```
flight-goat-pp-cli airports get-nearby
```
— Returns a list of airports located within a given distance from the given location.

alerts — AeroAPI alerting can be used to configure and receive real-time alerts on key flight events. With customizable alerting offered by our alert endpoints, AeroAPI empowers users to selectively pick various types of events/filters to alert on. By doing so, you can receive specially tailored alerts delivered to you for events such as flight plan filed, flight departure (out and off), flight arrival (on and in), and more!

To get started with alerting, the PUT /alerts/endpoint endpoint must first be used to set up the account-wide default URL that alerts will be delivered to. This step must be done before any alerts can be configured and will serve as the fallback URL that all alerts will be sent to for the account if a specific delivery URL is not designated on a particular alert. If this is not performed before configuring alerts, then you will receive a 400 error with an error message reminding you of this step when trying to interact with the POST /alerts endpoint. Once a URL is set via the PUT /alerts/endpoint endpoint, then alerts can be configured using the POST /alerts endpoint. The GET /alerts endpoint can also be used to retrieve all currently configured alerts associated with your AeroAPI key. The GET /alerts endpoint will allow you to easily retrieve the id of any specific alerts of interest configured for the account which can let you use the GET PUT and DELETE /alerts/{id} endpoints to retrieve, update, and delete specific alerts.

When configuring an individual alert, the target_url field can be set to a URL that’s different than the account-wide target endpoint set via the PUT /alerts/endpoint. If the target_url field is set on an alert, then that specific alert will be delivered to the specified target_url rather than the default account-wide one. If this field is not configured for the alert, then the alert will be delivered to the default account-wide endpoint. By setting this field, one can easily target different alerts to be received by different endpoints which can be useful for configuring per-application alerts or sending alerts to an alternate development environment without having to adjust a production alert configuration.

For each alert configured, one-to-many ‘events’ can be set for alert delivery. While most events will result in one alert delivery, both the arrival and the departure events can result in multiple alerts delivered (referred to as bundled). The departure event bundles the departure (actual OFF the ground) alert, along with the flight plan filed alert and up to 5 per-departure changes which can include alerts for significant departure delays of over 30 minutes, gate changes, and airport delays. FlightAware Global customers will also receive Power on and Ready to taxi alerts as part of the departure bundle. The arrival event bundles the arrival (actual ON the ground) alert, along with up to 5 en-route changes (including delays of over 30 minutes and excluding diversions) identified. FlightAware Global customers will also receive taxi stop times as part of the arrival bundle. Setting a bundled type and unbundled type for an On/Off will only result in a single alert in the case where events may overlap.

If there is a need to change the alert configurations, updating an alert using the PUT /alerts/{id} endpoint and a unique alert identifier (id) is preferred rather than creating an additional alert. By doing so, you can avoid duplicate alerts being delivered which could create unnecessary noise if they are not of interest anymore.

If at any point there is a need to delete an alert, the DELETE alerts/{id} endpoint can be leveraged to delete an alert so that it won’t be delivered anymore. As a reminder, specific alert IDs can be retrieved from the GET /alerts endpoint.

```
flight-goat-pp-cli alerts create
```
— Create a new AeroAPI flight alert. When the alert is triggered, a callback mechanism will be used to notify the...
```
flight-goat-pp-cli alerts delete
```
— Deletes specific alert with given ID
```
flight-goat-pp-cli alerts delete-endpoint
```
— Remove the default account-wide URL that will be POSTed to for alerts that are not configured with a specific URL....
```
flight-goat-pp-cli alerts get
```
— Returns the configuration data for an alert with the specified ID.
```
flight-goat-pp-cli alerts get-all
```
— Returns all configured alerts for the FlightAware account (this includes alerts configured through other means by...
```
flight-goat-pp-cli alerts get-endpoint
```
— Returns URL that will be POSTed to for alerts that are delivered via AeroAPI.
```
flight-goat-pp-cli alerts set-endpoint
```
— Updates the default URL that will be POSTed to for alerts that are delivered via AeroAPI. This sets the account-wide...
```
flight-goat-pp-cli alerts update
```
— Modifies the configuration for an alert with the specified ID. If a target URL address is provided, then the alert...

disruption-counts — Manage disruption counts

```
flight-goat-pp-cli disruption-counts get
```
— Returns flight cancellation/delay counts in the specified time period for a particular airline or airport.
```
flight-goat-pp-cli disruption-counts get-all
```
— Returns overall flight cancellation/delay counts in the specified time period for either all airlines or all airports.

flights — Manage flights

```
flight-goat-pp-cli flights get
```
— Returns the flight info status summary for a registration, ident, or fa_flight_id. If a fa_flight_id is specified...
```
flight-goat-pp-cli flights get-by-advanced-search
```
— Returns currently or recently airborne flights based on geospatial search parameters. Query parameters include a...
```
flight-goat-pp-cli flights get-by-position-search
```
— Returns flight positions based on geospatial search parameters. This allows you to locate flights that have ever...
```
flight-goat-pp-cli flights get-by-search
```
— Search for airborne flights by matching against various parameters including geospatial data. Uses a simplified...
```
flight-goat-pp-cli flights get-count-by-search
```
— Full search query documentation is available at the /flights/search endpoint.

foresight — Foresight endpoints provide access to FlightAware's Foresight predictive models and predictions for key events. Our advanced machine learning (ML) models identify key influencing factors for a flight to forecast future events in real-time, providing unprecedented insight to improve operational efficiencies and facilitate better decision-making in the air and on the ground. To learn more about the power of Foresight, visit https://www.flightaware.com/commercial/foresight/

These endpoints each mirror a non-Foresight equivalent endpoint of similar functionality, with the addition of all the ML 'predicted' values included in the Foresight response. The respective non-Foresight endpoint response includes a flag, 'foresight_predictions_available', which can optionally be used as a trigger to obtain and leverage Foresight predictions on an as-needed basis and manage cost. Foresight is only available to Premium tier customers. Contact integrationsales@flightaware.com for more information, pricing details, and to have your account enabled for Foresight.

```
flight-goat-pp-cli foresight get-flight-position-with
```
— Get flight's current position, including Foresight data
```
flight-goat-pp-cli foresight get-flight-with
```
— Returns the flight info status summary for a registration, ident, or fa_flight_id, including all available predicted...
```
flight-goat-pp-cli foresight get-flights-by-advanced-search-with
```
— Returns currently or recently airborne flights based on geospatial search parameters. If available, flights'...

history — Manage history

```
flight-goat-pp-cli history get-aircraft-last-flight
```
— Returns flight info status summary for an aircraft's last known flight given its registration. The search is limited...
```
flight-goat-pp-cli history get-flight
```
— Returns historical flight info status summary for a registration, ident, or fa_flight_id. If a fa_flight_id is...
```
flight-goat-pp-cli history get-flight-map
```
— Returns a historical flight's track as a base64-encoded image. Image can contain a variety of additional data layers...
```
flight-goat-pp-cli history get-flight-route
```
— Returns information about a historical flight's filed route including coordinates, names, and types of fixes along...
```
flight-goat-pp-cli history get-flight-track
```
— Returns the track for a historical flight as an array of positions. Data is available from now back to...

operators — Manage operators

```
flight-goat-pp-cli operators get
```
— Returns information for an operator such as their name, ICAO/IATA codes, headquarter location, etc.
```
flight-goat-pp-cli operators get-all
```
— Returns list of operator references (ICAO/IATA codes and URLs to access more information).

schedules — Manage schedules

```
flight-goat-pp-cli schedules
```
— Returns scheduled flights that have been published by airlines. These schedules are available for up to three months...

aircraft — 管理飞机信息

```
flight-goat-pp-cli aircraft <type>
```
— 根据ICAO飞机类型标识符字符串，返回该类型飞机的信息。返回的数据包括...

airports — 管理机场信息

```
flight-goat-pp-cli airports get
```
— 根据ICAO或LID机场代码（如KLAX、KIAH、O07等）返回机场信息。返回的数据...
```
flight-goat-pp-cli airports get-all
```
— 返回所有已知机场的ICAO标识符。对于没有ICAO标识符的机场，返回FAA LID...
```
flight-goat-pp-cli airports get-delays-for-all
```
— 返回存在延误的机场列表。如果一个机场存在多种延误原因，可能会返回多条记录...
```
flight-goat-pp-cli airports get-nearby
```
— 返回指定位置一定距离内的机场列表。

alerts — AeroAPI告警功能可用于配置和接收关键航班事件的实时告警。通过告警端点提供的可定制告警功能，AeroAPI允许用户选择性地设置各类事件/过滤条件来触发告警。您可以接收针对特定事件的定制化告警，例如航班计划提交、航班起飞（推出和离地）、航班到达（落地和入位）等！

要开始使用告警功能，必须先使用PUT /alerts/endpoint端点设置账户级别的默认告警交付URL。在配置任何告警之前必须完成此步骤，该URL将作为所有未指定特定交付URL的告警的 fallback URL。如果在配置告警前未执行此步骤，调用POST /alerts端点时将收到400错误，错误消息会提醒您完成该步骤。通过PUT /alerts/endpoint端点设置URL后，即可使用POST /alerts端点配置告警。您还可以使用GET /alerts端点检索与您的AeroAPI密钥关联的所有已配置告警。GET /alerts端点可让您轻松获取账户中感兴趣的特定告警的ID，以便使用GET、PUT和DELETE **/alerts/{id}**端点检索、更新和删除特定告警。

配置单个告警时，可以设置target_url字段为与账户级目标端点不同的URL。如果告警设置了target_url字段，则该特定告警将被发送到指定的target_url，而不是账户级默认URL。如果未配置该字段，告警将被发送到账户级默认端点。通过设置此字段，您可以轻松地将不同的告警发送到不同的端点，这对于配置应用专属告警或在不调整生产告警配置的情况下将告警发送到备用开发环境非常有用。

每个配置的告警可以设置一个到多个“事件”来触发告警交付。大多数事件只会触发一次告警交付，但arrival和departure事件可能会触发多次告警交付（称为捆绑告警）。departure事件捆绑了起飞（实际离地）告警、航班计划提交告警以及最多5次起飞前变更告警，包括超过30分钟的重大起飞延误、登机口变更和机场延误。FlightAware Global客户还将收到Power on和Ready to taxi告警作为起飞捆绑告警的一部分。arrival事件捆绑了到达（实际落地）告警以及最多5次途中变更告警（包括超过30分钟的延误，但不包括改道）。FlightAware Global客户还将收到taxi stop时间作为到达捆绑告警的一部分。如果为On/Off事件同时设置了捆绑类型和非捆绑类型，在事件重叠的情况下只会触发一次告警。

如果需要更改告警配置，建议使用**PUT /alerts/{id}**端点和唯一的告警标识符（id）更新告警，而不是创建新的告警。这样可以避免重复告警交付，减少不必要的干扰。

如果需要删除告警，可以使用DELETE alerts/{id}端点删除告警，使其不再被交付。提醒一下，特定告警的ID可以从GET /alerts端点获取。

```
flight-goat-pp-cli alerts create
```
— 创建新的AeroAPI航班告警。当告警触发时，将使用回调机制通知...
```
flight-goat-pp-cli alerts delete
```
— 删除具有指定ID的特定告警
```
flight-goat-pp-cli alerts delete-endpoint
```
— 删除账户级默认URL，该URL用于接收未配置特定URL的告警的POST请求...
```
flight-goat-pp-cli alerts get
```
— 返回具有指定ID的告警的配置数据。
```
flight-goat-pp-cli alerts get-all
```
— 返回FlightAware账户的所有已配置告警（包括通过其他方式配置的告警...
```
flight-goat-pp-cli alerts get-endpoint
```
— 返回用于接收AeroAPI交付告警的POST请求的URL。
```
flight-goat-pp-cli alerts set-endpoint
```
— 更新用于接收AeroAPI交付告警的POST请求的默认URL。此设置为账户级...
```
flight-goat-pp-cli alerts update
```
— 修改具有指定ID的告警的配置。如果提供了目标URL地址，则该告警...

disruption-counts — 管理航班中断统计

```
flight-goat-pp-cli disruption-counts get
```
— 返回指定时间段内特定航空公司或机场的航班取消/延误统计。
```
flight-goat-pp-cli disruption-counts get-all
```
— 返回指定时间段内所有航空公司或所有机场的整体航班取消/延误统计。

flights — 管理航班信息

```
flight-goat-pp-cli flights get
```
— 返回注册号、标识符或fa_flight_id对应的航班信息状态摘要。如果指定了fa_flight_id...
```
flight-goat-pp-cli flights get-by-advanced-search
```
— 根据地理空间搜索参数返回当前或最近的空中航班。查询参数包括...
```
flight-goat-pp-cli flights get-by-position-search
```
— 根据地理空间搜索参数返回航班位置。您可以通过此命令查找曾经...
```
flight-goat-pp-cli flights get-by-search
```
— 通过匹配各种参数（包括地理空间数据）搜索空中航班。使用简化的...
```
flight-goat-pp-cli flights get-count-by-search
```
— 完整的搜索查询文档可在/flights/search端点获取。

foresight — 前瞻（Foresight）端点提供对FlightAware Foresight预测模型和关键事件预测结果的访问权限。我们的高级机器学习（ML）模型识别影响航班的关键因素，实时预测未来事件，为提高运营效率和促进空中及地面的更好决策提供前所未有的洞察力。要了解更多关于Foresight的强大功能，请访问https://www.flightaware.com/commercial/foresight/

这些端点各自对应一个非Foresight的等效端点，功能相似，但Foresight响应中包含所有ML“预测”值。对应的非Foresight端点响应包含一个标志

foresight_predictions_available

，您可以选择将其作为触发器，根据需要获取和使用Foresight预测结果并管理成本。Foresight仅对高级套餐客户可用。如需更多信息、定价详情及开启账户Foresight功能，请联系integrationsales@flightaware.com。

```
flight-goat-pp-cli foresight get-flight-position-with
```
— 获取航班的当前位置，包括Foresight数据
```
flight-goat-pp-cli foresight get-flight-with
```
— 返回注册号、标识符或fa_flight_id对应的航班信息状态摘要，包括所有可用的预测...
```
flight-goat-pp-cli foresight get-flights-by-advanced-search-with
```
— 根据地理空间搜索参数返回当前或最近的空中航班。如果可用，航班的...

history — 管理历史数据

```
flight-goat-pp-cli history get-aircraft-last-flight
```
— 根据飞机注册号返回其最后一次已知航班的信息状态摘要。搜索范围限制在...
```
flight-goat-pp-cli history get-flight
```
— 返回注册号、标识符或fa_flight_id对应的历史航班信息状态摘要。如果指定了fa_flight_id...
```
flight-goat-pp-cli history get-flight-map
```
— 返回历史航班的轨迹，以base64编码的图片形式呈现。图片可以包含各种附加数据层...
```
flight-goat-pp-cli history get-flight-route
```
— 返回历史航班的申报航线信息，包括航线中各个定位点的坐标、名称和类型...
```
flight-goat-pp-cli history get-flight-track
```
— 返回历史航班的轨迹，以位置数组形式呈现。数据可追溯至...

operators — 管理运营商信息

```
flight-goat-pp-cli operators get
```
— 返回运营商的信息，包括名称、ICAO/IATA代码、总部位置等。
```
flight-goat-pp-cli operators get-all
```
— 返回运营商参考列表（ICAO/IATA代码及访问更多信息的URL）。

schedules — 管理航班时刻表

```
flight-goat-pp-cli schedules
```
— 返回航空公司发布的计划航班。这些时刻表最长可查询未来三个月的...

Finding the right command

查找合适的命令

When you know what you want to do but not which command does it, ask the CLI directly:

bash

flight-goat-pp-cli which "<capability in your own words>"

which

resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code

means at least one match; exit code

means no confident match — fall back to

--help

or use a narrower query.

当您知道要执行的操作但不知道对应的命令时，可以直接询问CLI：

bash

flight-goat-pp-cli which "<用您自己的描述说明功能>"

which

命令会将自然语言描述的功能查询解析为CLI精选功能索引中最匹配的命令。退出码

表示至少有一个匹配项；退出码

表示没有确定的匹配项——此时可以使用

--help

或缩小查询范围。

Auth Setup

认证设置

Set your API key via environment variable:

bash

export FLIGHT_GOAT_API_KEY_AUTH="<your-key>"

Or persist it in

~/.config/flight-goat-pp-cli/config.toml

Run

flight-goat-pp-cli doctor

to verify setup.

通过环境变量设置您的API密钥：

bash

export FLIGHT_GOAT_API_KEY_AUTH="<您的密钥>"

或者将其持久化存储在

~/.config/flight-goat-pp-cli/config.toml

文件中。

执行

flight-goat-pp-cli doctor

验证设置是否正确。

Agent Mode

Agent模式

Add

--agent

to any command. Expands to:

--json --compact --no-input --no-color --yes

Pipeable — JSON on stdout, errors on stderr
Filterable —
```
--select
```
keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
bash
```
flight-goat-pp-cli airports get mock-value --agent --select id,name,status
```
Previewable —
```
--dry-run
```
shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag

在任何命令后添加

--agent

参数。该参数等效于：

--json --compact --no-input --no-color --yes

。

可管道传输 — 标准输出为JSON格式，错误信息输出到标准错误
可过滤 —
```
--select
```
参数保留指定字段子集。点路径可深入嵌套结构；数组会遍历每个元素。这对于在冗长的API响应中精简上下文至关重要：
bash
```
flight-goat-pp-cli airports get mock-value --agent --select id,name,status
```
可预览 —
```
--dry-run
```
参数显示请求内容但不发送
离线友好 — 同步/搜索命令在可用时可以使用本地SQLite存储
非交互式 — 从不提示输入，所有输入均通过标志参数提供

Response envelope

响应信封

Commands that read from the local store or the API wrap output in a provenance envelope:

json

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse

.results

for data and

.meta.source

to know whether it's live or local. A human-readable

N results (live)

summary is printed to stderr only when stdout is a terminal — piped/agent consumers get pure JSON on stdout.

从本地存储或API读取数据的命令会将输出包装在来源信封中：

json

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

解析

.results

字段获取数据，

.meta.source

字段表示数据来自实时API还是本地存储。只有当标准输出为终端时，才会在标准错误输出中打印人类可读的

N results (live)

摘要；通过管道传输或Agent模式的消费者只会在标准输出中获取纯JSON数据。

Agent Feedback

Agent反馈

When you (or the agent) notice something off about this CLI, record it:

flight-goat-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
flight-goat-pp-cli feedback --stdin < notes.txt
flight-goat-pp-cli feedback list --json --limit 10

Entries are stored locally at

~/.flight-goat-pp-cli/feedback.jsonl

. They are never POSTed unless

FLIGHT_GOAT_FEEDBACK_ENDPOINT

is set AND either

--send

is passed or

FLIGHT_GOAT_FEEDBACK_AUTO_SEND=true

. Default behavior is local-only.

Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.

当您（或Agent）发现此CLI存在问题时，可以记录反馈：

flight-goat-pp-cli feedback "--since参数是包含性的，但文档说是排他性的"
flight-goat-pp-cli feedback --stdin < notes.txt
flight-goat-pp-cli feedback list --json --limit 10

反馈条目存储在本地

~/.flight-goat-pp-cli/feedback.jsonl

文件中。除非设置了

FLIGHT_GOAT_FEEDBACK_ENDPOINT

且传递了

--send

参数或设置了

FLIGHT_GOAT_FEEDBACK_AUTO_SEND=true

，否则反馈不会被POST发送。默认行为是仅本地存储。

请写下让您感到意外的内容，而不是正式的bug报告。简短、具体、单行描述：这样的反馈会更有价值。

Output Delivery

输出交付

Every command accepts

--deliver <sink>

. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:

Sink	Effect
`stdout`	Default; write to stdout only
`file:<path>`	Atomically write output to `<path>` (tmp + rename)
`webhook:<url>`	POST the output body to the URL ( `application/json` or `application/x-ndjson` when `--compact` )

Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.

每个命令都支持

--deliver <sink>

参数。输出会发送到指定的sink，同时（或替代）输出到标准输出，因此Agent无需手动管道即可路由命令结果。支持三种sink：

Sink	效果
`stdout`	默认值；仅输出到标准输出
`file:<path>`	原子性地将输出写入 `<path>` （先写入临时文件再重命名）
`webhook:<url>`	将输出体POST到指定URL（当使用 `--compact` 时为 `application/json` 或 `application/x-ndjson` 格式）

未知的scheme会被拒绝，并返回结构化错误信息，列出支持的类型。Webhook失败会返回非零退出码，并在标准错误输出中记录URL和HTTP状态码。

Named Profiles

命名配置文件

A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.

flight-goat-pp-cli profile save briefing --json
flight-goat-pp-cli --profile briefing airports get mock-value
flight-goat-pp-cli profile list --json
flight-goat-pp-cli profile show briefing
flight-goat-pp-cli profile delete briefing --yes

Explicit flags always win over profile values; profile values win over defaults.

agent-context

lists all available profiles under

available_profiles

so introspecting agents discover them at runtime.

配置文件是一组保存的标志值，可在多次调用中复用。当定时Agent每次运行都使用相同配置调用同一命令时，可以使用此功能——即HeyGen的“Beacon”模式。

flight-goat-pp-cli profile save briefing --json
flight-goat-pp-cli --profile briefing airports get mock-value
flight-goat-pp-cli profile list --json
flight-goat-pp-cli profile show briefing
flight-goat-pp-cli profile delete briefing --yes

显式标志参数始终优先于配置文件中的值；配置文件中的值优先于默认值。

agent-context

会在

available_profiles

下列出所有可用配置文件，以便Agent在运行时发现它们。

Exit Codes

退出码

Code	Meaning
0	Success
2	Usage error (wrong arguments)
3	Resource not found
4	Authentication required
5	API error (upstream issue)
7	Rate limited (wait and retry)
10	Config error

代码	含义
0	成功
2	使用错误（参数错误）
3	资源未找到
4	需要认证
5	API错误（上游问题）
7	请求受限（请等待后重试）
10	配置错误

Argument Parsing

参数解析

Parse

$ARGUMENTS

Empty,
help
, or
--help
→ show
```
flight-goat-pp-cli --help
```
output
Starts with
install
→ ends with
```
mcp
```
→ MCP installation; otherwise → see Prerequisites above
Anything else → Direct Use (execute as CLI command with
```
--agent
```
)

解析

$ARGUMENTS

的规则：

为空、
help
或
--help
→ 显示
```
flight-goat-pp-cli --help
```
的输出
以
install
开头 → 如果以
```
mcp
```
结尾 → 安装MCP；否则 → 参见上方的前置条件
其他情况 → 直接使用（添加
```
--agent
```
参数执行CLI命令）

MCP Server Installation

MCP服务器安装

Install the MCP server:

bash

go install github.com/mvanhorn/printing-press-library/library/travel/flight-goat/cmd/flight-goat-pp-mcp@latest

bash

claude mcp add flight-goat-pp-mcp -- flight-goat-pp-mcp

Verify:
```
claude mcp list
```

安装MCP服务器：

bash

go install github.com/mvanhorn/printing-press-library/library/travel/flight-goat/cmd/flight-goat-pp-mcp@latest

在Claude Code中注册：

bash

claude mcp add flight-goat-pp-mcp -- flight-goat-pp-mcp

验证：
```
claude mcp list
```

Direct Use

直接使用

Check if installed:
```
which flight-goat-pp-cli
```
If not found, offer to install (see Prerequisites at the top of this skill).
Match the user query to the best command from the Unique Capabilities and Command Reference above.

Execute with the

--agent

flag:

bash

flight-goat-pp-cli <command> [subcommand] [args] --agent

If ambiguous, drill into subcommand help:
```
flight-goat-pp-cli <command> --help
```
.

检查是否已安装：
```
which flight-goat-pp-cli
```
如果未找到，提供安装选项（参见顶部的前置条件）。
将用户查询与上方“独特功能”和“命令参考”中的最佳命令匹配。

添加

--agent

参数执行：

bash

flight-goat-pp-cli <command> [subcommand] [args] --agent

如果存在歧义，查看子命令帮助：
```
flight-goat-pp-cli <command> --help
```
。

pp-flight-goat

Original

Translation

Flight Goat — Printing Press CLI

Flight Goat — Printing Press CLI

Prerequisites: Install the CLI

前置条件：安装CLI

Categories

分类

Development Tools

开发工具

Command Reference

命令参考

Finding the right command

查找合适的命令

Auth Setup

认证设置

Agent Mode

Agent模式

Response envelope

响应信封

Agent Feedback

Agent反馈

Output Delivery

输出交付

Named Profiles

命名配置文件

Exit Codes

退出码

Argument Parsing

参数解析

MCP Server Installation

MCP服务器安装

Direct Use

直接使用