# Flight Live

> Use when the user asks to search live flights, compare dates or fares, or rank travel options.

- Skill: `anntnzrb/flight-live` (Agent Skill, multi-file: 21 files)
- Install (CLI): `npx skillmds@latest add anntnzrb/flight-live`
- Raw SKILL.md: https://api.skillmd.com/api/skills/anntnzrb/flight-live/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: AGPL-3.0-or-later
- Author: anntnzrb (https://skillmd.com/u/anntnzrb)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/anntnzrb/flight-live

---


# flight-live

Operator manual for the bundled read-only flight CLI.

## Credentials

No credentials. No API keys. No commercial APIs.

## Entry points

- From skill root: `uv run --script <skill-dir>/scripts/cli.py ...`
- From anywhere: `uv run --script "$SKILLS_DIR/flight-live/scripts/cli.py" ...`
- If `SKILLS_DIR` is not set: `uv run --script <skill-dir>/scripts/cli.py ...`
- For process integration: `uv run --script <skill-dir>/scripts/cli.py --mode rpc`

## Core rule

Prefer `--llm-json` unless user asks for human text.

## Fast pattern

```bash
uv run --script <skill-dir>/scripts/cli.py \
  --origin GYE \
  --destination MIA \
  --depart-start 2026-08-01 \
  --depart-end 2026-10-31 \
  --trip-type roundtrip \
  --stay-min 4 \
  --stay-max 10 \
  --llm-json
```

## Failure handling

Common failures:

- missing `nix` in PATH (hard fail)
- `agent-browser` unavailable via nix wrapper (hard fail)
- provider execution/network failures (hard fail)
- over-constrained filters (empty shortlist with guidance in `decision.actions`)

Recovery order:

1. verify `nix` works
2. run `nix run github:numtide/llm-agents.nix#agent-browser -- --version`
3. widen date window
4. disable `--nonstop`
5. raise/remove `--max-budget`
6. relax `--stay-min/--stay-max`

## Evidence fields to trust most

Top-level:

- `warnings`
- `summary.planner_received`
- `summary.after_filters`
- `summary.returned`
- `resolved.origin.iata` / `resolved.destination.iata`
- `insights.weekend_premium_pct`
- `decision.recommendation`

Per result:

- `effective_price`
- `nonstop`
- `depart_date` / `return_date`
- `score`
- `reasons`
- `hints`

## RPC usage

Use RPC for strict JSONL envelopes (`ping`, `get_schema`, `search`).

## Required follow-up reads

| Need | Read | When |
| --- | --- | --- |
| Search commands and trusted fields | `references/cheatsheet.md` | Constructing or interpreting a search |
| Decision workflow | `references/workflows.md` | Comparing options or presenting recommendations |
| JSONL request and response contract | `references/rpc.md` | Using `--mode rpc` |
| Failure diagnosis | `references/troubleshooting.md` | Any provider, filter, or RPC failure |