Pack reference
One page per shipped pack. Each page covers what the pack does, the input/output schema, vault credentials it depends on, how to invoke it from the CLI today and from the Management UI when that lands, the closed set of typed error codes it can return, and how it composes with other packs via session chaining.
For a quick-lookup summary across all 36 packs (just the input/output contract), see PACKS.md. For agent-facing prompt guidance, see SKILLS.md. This per-pack reference is the deep view.
By family
| Family | Packs | Status |
|---|---|---|
| browser | browser.screenshot_url · browser.interact | ✅ Documented |
| web | web.scrape · web.scrape_spa · web.test | 🟡 Tracking issue |
| repo | repo.fetch · repo.map · repo.push | 🟡 Tracking issue |
| github | github.create_issue · github.list_issues · github.list_prs · github.post_comment · github.create_release · github.search | 🟡 Tracking issue |
| slides | slides.render · slides.narrate · slides.notes | 🟡 Tracking issue |
| doc | doc.ocr · doc.parse | 🟡 Tracking issue |
| desktop | desktop.run_app_and_screenshot + 16 REST primitives | 🟡 Tracking issue |
| vision | vision.click_anywhere · vision.extract_visible_text · vision.fill_form_by_label | 🟡 Tracking issue |
| fs | fs.read · fs.write · fs.list · fs.patch · fs.delete | 🟡 Tracking issue |
| shell | cmd.run · git.commit · git.diff · git.log | 🟡 Tracking issue |
| http | http.fetch | 🟡 Tracking issue |
| research / content | research.deep · content.ground | 🟡 Tracking issue |
| language | python.run · node.run | 🟡 Tracking issue |
Contributing a pack page
Use _template.md on GitHub as your starting point. The browser pages above are worked examples — same structure, same depth.
A typical pack page takes 30–60 minutes to write end-to-end against a running install:
- Read the handler in
internal/packs/builtin/<file>.gofor the actual error codes and any session-coupling. - Pick up the inputs/outputs from the
PACKS.mdrow and the agent guidance fromSKILLS.md. - Run a real CLI invocation against your local stack (see the install tutorial) and paste the redacted output.
- Open a PR linking to the family tracking issue.