> ## 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 snapshot of an **entire agent's** deployable manifest — every skill, webhook, job, processor, trigger, and the model — frozen from one agent's promoted version. Installing one materializes that whole manifest onto your agent and promotes a new agent version. Built for standing up many agents from the same blueprint, and pushing coordinated updates to all of them later.
  </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 to stand up a new agent — or a fleet of near-identical agents — from a known-good configuration, and keep them in sync as that configuration 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 persona, environment variable *values*, channels, or name — those stay per-agent. 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>
</CardGroup>

<Card title="Agent Templates" icon="layer-group" href="/marketplace/agent-templates">
  Publish, install, and roll out full agent configurations across a fleet.
</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 agent that has it installed.

<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>