Packs

Packs bundle Stallari capabilities. A pack can include workflows, prompts, plugin requirements, model preferences, and review expectations.

Use Packs to understand what is installed locally. Use Marketplace to discover and install new packs.

What A Pack Can Contain

Part	Meaning
Workflows	Named units of work Stallari can run.
Skills or prompts	Instructions used by a workflow.
Plugin requirements	Service contracts the pack needs.
Model preferences	Suggested model tiers or routing hints.
Review policy	Human review expectations for sensitive output.

Exact fields depend on the pack version and manifest format.

Pack Detail

Pack detail should help you answer:

• What does this pack do?
• Who published it?
• Which plugins or data classes does it need?
• Does it create external side effects?
• Which workflows are available?
• Is anything missing before it can run?

If required plugins are missing, install or configure them before running the pack.

Running Work From A Pack

Some packs expose work that can be started from the app or Chat. Before running sensitive work, Stallari should show the relevant confirmation, plugin consent, or review gate.

After work starts, use Operations for live progress and Activity for durable details.

Troubleshooting

Symptom	Where To Check
Required plugin missing	Marketplace or Settings plugin controls.
Work cannot start	Status for helper/provider/plugin readiness.
Work started but failed	Activity detail for the run.

Related concepts

• Packs And Trust — how an installed pack’s capability scope, publisher identity, and review policy bind to actual runs