> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heylua.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Marketplace Overview

> Discover, install, and publish skills and agent templates

## The Lua Marketplace

The Marketplace is where developers share reusable pieces of agent functionality with each other — either a single **skill**, or a full **agent template**.

```bash theme={null}
lua marketplace                 # Interactive: pick Skills or Agent templates
lua marketplace skill           # Skill action menu
lua marketplace template        # Template action menu
```

<Note>
  The Marketplace command tree is `lua marketplace [noun] [action]`, where `noun` is `skill` or `template`. See the [Marketplace Command reference](/cli/marketplace-command) for every action and flag.
</Note>

## Skills vs. agent templates

Both are published, versioned, and installable — but they operate at different scopes.

<CardGroup cols={2}>
  <Card title="Skill" icon="wrench">
    A single reusable tool package — e.g. a CRM lookup, a payment integration, a moderation filter. Install it into an agent that already has its own persona, other skills, webhooks, and jobs. Composable: install as many as you need alongside your existing setup.
  </Card>

  <Card title="Agent Template" icon="layer-group">
    A published blueprint of an **entire agent** — its persona (with fill-in variables), skills, webhooks, jobs, triggers with editable presets, declared connections ("a CRM" — Salesforce or HubSpot), and the model. Deploying one gives you a working agent wired into the tools you've already connected — created fresh in one call, or installed onto an agent you already run.
  </Card>
</CardGroup>

**Use a skill** when you want to add one capability to an agent you're already building. **Use an agent template** when you want a working agent from a known-good blueprint — a one-off deploy from the catalog, or a fleet of near-identical agents kept in sync as the blueprint evolves. A common pattern: build and tune one merchant's support agent by hand, then publish it as a template so every new merchant onboards from the same starting point, and every improvement rolls out to all of them with a single `apply`.

Templates never touch a target agent's environment variable *values*, channels, or name — those stay per-agent. Persona travels with the template as a fill-in-the-blanks starting point, but an agent that already has a persona keeps it, and your post-install persona edits survive updates. See [Agent Templates](/marketplace/agent-templates) for the full model.

### Ecosystem Roles

<CardGroup cols={2}>
  <Card title="Publishing Skills" icon="code" href="/marketplace/creator-guide">
    Publish your skills to the world. Manage versions, environment variables, visibility, and listings.
  </Card>

  <Card title="Installing Skills" icon="download" href="/marketplace/installer-guide">
    Browse verified skills, search by capability, and install with one command.
  </Card>

  <Card title="Publishing Templates" icon="code-branch" href="/marketplace/publishing-templates">
    Turn a working agent into a template: draft, author, publish, review, and roll out updates.
  </Card>

  <Card title="Deploying Templates" icon="rocket" href="/marketplace/deploying-templates">
    Deploy a template in minutes — reuse your connections, confirm your automations, operate and update the install.
  </Card>
</CardGroup>

<Card title="Agent Templates" icon="layer-group" href="/marketplace/agent-templates">
  The model behind both: what a template contains, its lifecycle, review, and update consent.
</Card>

### Key Features

* 🌍 **Global Discovery**: Public skills and templates are indexed and searchable by name, description, and tags.
* 🔒 **Private Visibility**: List a skill or create a template as private — only your organization can find and install it. Everyone else gets a not-found, same as if it didn't exist.
* 📦 **Semantic Versioning**: Full support for `major.minor.patch` skill versioning; templates version as sequential integers per template.
* ⚙️ **Smart Configuration**: Environment variables are declared per-version and configured interactively (or via flags) at install time.
* 🔄 **Update Management**: Upgrade an installed skill to a newer version, or roll a template out to every consenting agent that has it installed — with previews before accepting, and re-consent whenever an update changes what a template can access.
* 🛡️ **Reviewed Public Catalog**: Public templates are platform-reviewed per version before anyone can install them; orgs can additionally allow, deny, or require approval for template installs.

<Note>
  You can jump directly into either domain non-interactively, e.g. `lua marketplace skill search --query "CRM"` or `lua marketplace template status --template-id tpl_abc`. See the [Marketplace Command reference](/cli/marketplace-command) for the full flag set.
</Note>