Skip to main content

​
Becoming a Creator

As a creator, you can share your agent skills with the entire Lua community — or keep them private to your own organization. Whether it’s a specialized tool, a complex integration, or a utility job, the marketplace handles versioning, distribution, and discovery.
Looking to publish a whole agent configuration instead of a single skill? See Agent Templates.

​
Listing a Skill

To list a skill, it must be defined in your project and pushed to the server. The marketplace verifies the skill against your agent’s active skills on the server.
  1. Run the skill menu:
  2. Select “List a new skill on the Marketplace”.
  3. Choose the skill you want to publish (fetched from your agent on the server).
  4. Metadata: Follow the prompts to configure your skill’s listing details.
    • Display Name: Enter a user-friendly name (e.g., “Hotel Concierge”).
    • Visibility: Public (default) or private — see below.
  5. The skill is now listed!
Non-interactively:

​
Private Visibility

By default, a listed skill is public — anyone on the marketplace can search for it, view it, and install it. Set --visibility private to restrict it to your own organization instead:
A private skill is visible and installable only to members of the creator’s organization. Everyone else — including a search that would otherwise match it — gets a plain not-found, exactly as if the listing didn’t exist. There’s no separate “unlisted” state to reason about: visibility is the one switch.
Common use case: an internal skill library shared across your organization’s own agents — reusable tools your team builds once and installs onto every agent that needs them, without exposing them on the public marketplace.
The review flow, versioning, and every other marketplace mechanic (publishing versions, env vars, unlisting) work identically for private and public skills — visibility only changes who can find and install the listing.

​
Publishing Versions

Listing a skill creates the entry, but users can’t install it until you publish a version.
  1. Select “Publish a new version of a skill”.
  2. Choose your listed skill.
  3. Select the version to publish (e.g., 1.0.0).
    • The CLI detects versions that have been compiled and pushed to the server.
  4. Configuration:
    • Environment Variables: Define any variables your skill needs (e.g., HOTEL_API_KEY).
    • Changelog: Optionally add a note about what’s new in this version.
    • Complete any other required configuration steps.
Non-interactively:
You’ll be notified once the review is complete.
Semantic Versioning: The marketplace uses SemVer. Always ensure your version numbers (e.g., 1.0.1, 2.0.0) reflect the nature of your changes.

​
Managing Listings

You can manage your existing skills through the same menu:
  • Edit Metadata (edit): Change the display name of your skill.
  • Unlist (unlist): Remove the skill from the marketplace (hides it from search; existing installs keep working).
  • Unpublish Version (unpublish): Remove a specific version if it has issues.
  • View My Listings (mine): See a summary of your published skills, install counts, and latest versions.

​
Best Practices

  • Clear Documentation: Use descriptive names and helpful descriptions for your environment variables.
  • SemVer: Increment patch versions for bug fixes, minor for features, and major for breaking changes.
  • Vector Search: Your skill’s name and description are indexed. Make them relevant to what users might search for (e.g., “moderation”, “payment”, “weather”). Private skills are only searchable within your own organization, so this still matters for internal discovery.