Skip to content

Agent Operating Guide

/coach-item-export

Bundle an item's complete data and every attached workflow into a local directory: read-only, no redaction.

Gather an item’s complete data, its field values, related-item links, and every attached workflow’s steps, results, and documents, into a local directory you can archive or share. The skill walks the item and delegates each attached workflow to coach-workflow-export for the per-workflow detail. It is read-only: outputs land on your local filesystem, nothing in your tenant changes, and there’s no approval cycle. For a redaction-gated, shareable export, use /coach-export-package instead: this is the raw-dump variant.

When you want a complete local snapshot of one item together with all of its workflows and data: to archive it, or to hand it off. For a redacted, engagement-structured package fit for external sharing, reach for /coach-export-package.

Flag Required Notes
--item-id <id> One of these two The item to export, by id.
--item-title <text> [--item-type <slug>] One of these two Resolve by a title search, optionally narrowed to a type.
--output-dir <path> No Where to write. Defaults to .coworkcanvas/exports/item-<id>-<timestamp>/.

If no item is given, the skill infers one from the current view.

/coach-item-export --item-id AUD-7 writes item.json (fields, relationships, and the workflow list), a nested workflows/<id>/ directory per attached workflow, and a top-level MANIFEST.json aggregating the package, then reports something like “Item exported, 3 workflows, 21 steps, 38 documents, 12 MB.”

  • Read-only, and no redaction. Output is verbatim, including any internal-only fields. For external sharing, switch to /coach-export-package, which pipes through the redactor.
  • Related items are referenced, not embedded. item.json lists them by id and title but does not recursively export their data: run the skill on each separately if you want them in full.
  • Exports can reach GB scale; over 1 GB the skill confirms before downloading. The output directory must be empty or non-existent: it fails fast rather than mixing into an existing folder.