logion

Logion Marketplace Companion

Use Logion only as a fallback or explicit browse/acquire path. Keep bootstrap context small; load only the selected skill artifact.

First run (one-time setup)

Before any identity-backed command or auto-review works, the user must run onboarding once. It provisions their user + first agent and, with an explicit opt-in, lets agents post usage reviews automatically:

logion identity onboarding

It is interactive (email, password, and a y/N auto-review consent), so do not run it unattended. If a command fails with auth_missing, prompt the user to run it. Change the auto-review setting later by re-running with --enable-autopost or --no-enable-autopost.

CLI updates

The Logion CLI manages its own periodic auto-update checks using persisted local state. Do not run logion update before every Logion use. If the user asks to manage this behavior, use logion update --auto-update status, logion update --disable-auto-update, or logion update --enable-auto-update.

When to use Logion

Use Logion when local recall is insufficient and the task needs a missing, specialized capability, or when the user explicitly asks to browse, search, acquire, install, or update from Logion.

When not to use Logion

Do not use Logion when an existing local tool, installed skill, prior proven workflow, or project-local command already covers the task well enough.

Decision tree

Priority order (cheapest to most expensive context cost): respond directly with an installed capability → recall → marketplace. Never invert this. Loading a reference or hitting the marketplace is a context cost only worth paying when the local surface is genuinely insufficient.

1. Run the Local Recall Guardrail before marketplace search.
2. Check installed_capabilities first — if an installed skill already covers the task (e.g. email.summarize for "summarise my inbox", video.clips.highlight for "extract clips"), respond directly using that capability and do not search the marketplace.
3. If recall returns a high-confidence local match, or an existing local skill/tool already satisfies the task, use that local path first.
4. If recall returns a medium-confidence match, present it as a candidate or use it as context only; do not execute automatically.
5. If the user explicitly asks to browse/search/acquire from Logion, search via logion listings search after noting recall is being bypassed or supplemented. When you know the domain, prefer --category and --tag filters over broad free-text search. Use free-text --query only for the remaining intent words.
6. Search Logion via logion listings search only when local recall is insufficient for a missing, specialized capability.
7. Inspect candidates via logion courses get before recommending installation.
8. Prefer free or local equivalents when quality is comparable.
9. Always ask for explicit user approval before any paid action, install, or update — specifically: logion skills install, logion credits top-up, logion courses purchase, and logion skills update calls that change price, permissions, required tools, or execution policy.
10. Load only the selected skill artifact, never the whole catalog.
11. Only call commands listed under "Implemented safe discovery commands", "Implemented mutating commands", or "Creator commands" below.