Marketplace Guidelines

The Selu marketplace is where users discover and install agents. Before submitting your agent, make sure it meets the requirements below. Agents that don’t pass review will receive feedback — you can fix the issues and resubmit.

Submission requirements

1. Complete metadata

Your agent.yaml must include all required fields:

• name — unique, lowercase, hyphens only
• version — valid semver
• display_name — clear, descriptive
• description — one-line summary (max 160 characters)
• author — your marketplace username
• license — valid SPDX identifier

2. Both locale files

Every published agent must include English content. German translations are not required for agent packages (unlike docs pages), but they’re recommended for marketplace listings.

3. Working capabilities

All capabilities referenced in agent.yaml must either:

• Exist as local directories with a valid manifest.yaml and Dockerfile, or
• Reference a published, publicly accessible Docker image.

4. Security review

Capabilities undergo an automated security scan:

• Docker images must run as a non-root user.
• No hard-coded secrets or API keys in the image.
• No privileged container flags.
• Network access must match declared behaviour.

Danger

Agents that attempt to exfiltrate user data, access the host filesystem, or circumvent security controls will be permanently banned.

5. Quality bar

• The agent must do what its description says. No misleading claims.
• System prompts must include clear constraints — the agent should refuse off-topic requests gracefully.
• Capabilities must handle errors and return meaningful messages (not stack traces).
• Response latency should be reasonable — capabilities should respond within their declared timeout.

Submission process

1. Validate locally

   selu validate .
   selu test snapshot run .

2. Build and test all capabilities

   selu dev .
   # Test manually and with snapshots

3. Submit

   selu publish .

   This command packages your agent, pushes capability images to the Selu registry, and creates a submission for review.

4. Review

   A human reviewer checks your submission against the guidelines above. You’ll receive feedback via email (and in the CLI) within 48 hours.

5. Publish

   Once approved, your agent appears in the marketplace. Users can install it with:

   selu install your-agent-name

Listing content

When users browse the marketplace, they see:

• Display name and description from agent.yaml
• Tags — help with discoverability (add relevant tags)
• Author and license
• Version history and changelog

Tip

Write your description as if it’s a one-line pitch. Users decide whether to click through based on this alone.

Updates and delisting

• Publish updates with selu publish . — bump the version in agent.yaml first.
• Delist an agent with selu unpublish your-agent-name. Existing installs continue to work, but new installs are blocked.

Next steps

• Release Pipeline — Automate publishing with GitHub Actions.
• Versioning — How semver works in the Selu ecosystem.