fieldlisted

# Field Use this skill whenever a request touches Field jobs, quotes, invoices, payments, email templates, catalog entries, PDFs, or the `field` command. ## Bundled tool The dependency-free CLI is at `scripts/field-cli.js` under this plugin's root. Resolve the plugin root from this `SKILL.md` path and invoke the script with an absolute path: ```bash node "<plugin-root>/scripts/field-cli.js" --help ``` Prefer an installed `field` command when `command -v field` succeeds. If it is missing and the user has asked to set up or use Field, run: ```bash node "<plugin-root>/scripts/install-field-cli.js" ``` The installer writes only to a user-writable command prefix and prints the installed launcher path. ## Authentication Production is `https://field.embarkearthworks.au`. Check authentication before an operational request: ```bash field auth status ``` If authentication is missing, tell the user to run this in their own terminal: ```bash field auth login --url https://field.embarkearthworks.au ``` The prompt hides the service key and stores it at `~/.config/field/token` with user-only permissions. Never ask the user to paste a key into chat, place one in argv, print one, or read one back into the conversation. `FIELD_TOKEN` and `FIELD_TOKEN_FILE` are supported for managed runtime delivery. ## Working rules - Read the job or template before changing it and report the exact target. - Treat non-draft customer-facing quote revisions as locked history. - Payment documents