Build, validate and publish skills, employees, plugins, apps, connectors and collections to the NeboAI marketplace, from the AI tools you already use.
This repo has two parts:
- The publisher skill (
SKILL.md,references/,scripts/,examples/): an Agent Skills skill that teaches an AI tool how to turn an idea into a marketplace item and publish it. - The
neboaiCLI (cli/): a small Rust binary that signs you in, validates an item's files and publishes them.
Learn more at neboai.com/learn/neboai.
curl -fsSL https://raw.githubusercontent.com/NeboLoop/publisher/main/install.sh | bashInstalls the neboai binary to /usr/local/bin (override with INSTALL_DIR=...) and the skill to ~/.claude/skills/neboai (override with SKILLS_DIR=...), both from the latest release, checked against its SHA256SUMS.
irm https://raw.githubusercontent.com/NeboLoop/publisher/main/install.ps1 | iexInstalls neboai.exe to %LOCALAPPDATA%\Programs\neboai (added to your PATH) and the skill to %USERPROFILE%\.claude\skills\neboai.
brew tap NeboLoop/tap
brew trust neboloop/tap # Homebrew 7+ asks you to trust a third-party tap
brew install neboaipnpm add -g @neboai/publisher
# or: npm install -g @neboai/publisherThe package fetches the matching neboai binary from this repo's release on install, or on first run if your package manager skips install scripts.
The skill uses the open Agent Skills format. Copy it into your tool's skills folder:
git clone https://github.com/NeboLoop/publisher.git
mkdir -p <your-tool-skills-folder>/neboai
cp -R publisher/SKILL.md publisher/references publisher/scripts publisher/examples <your-tool-skills-folder>/neboai/Each release also has the skill as neboai-skill.tar.gz.
| Platform | Binary |
|---|---|
| macOS, Apple Silicon | neboai-darwin-arm64 |
| macOS, Intel | neboai-darwin-amd64 |
| Linux, ARM64 | neboai-linux-arm64 |
| Linux, x86_64 | neboai-linux-amd64 |
| Windows, x86_64 (also runs on Windows on Arm) | neboai-windows-amd64.exe |
neboai auth loginOpens your browser to sign in with your NeboAI account. Any account works: there is no fee, no developer-account step and no verification. Your publisher account (@your-handle) is set up for free the first time you sign in or publish. neboai publish also starts sign-in by itself if you haven't signed in yet.
neboai auth status # signed in? which handle?
neboai auth logoutIn Claude Desktop, ChatGPT or any app that supports remote MCP, add the NeboAI connector (https://neboai.com/mcp) instead of installing anything. The skill works through its tools. See Publishing via MCP.
- Install the skill and CLI, and sign in (above).
- Tell your AI tool what you want, for example: "I have an idea for a skill that turns my meeting notes into a follow-up email. Build it and publish it to NeboAI."
- It builds the files, checks them with
neboai validate, publishes withneboai publishand tells you the review outcome.
Or by hand:
neboai validate ./my-skill
neboai publish ./my-skill # public: submitted for review, listed once approved
neboai list # everything you've published, with its status
neboai status <id> # Draft / In review / Publishedneboai publish ./dir --visibility private (or loop) saves an item without listing it, so it isn't reviewed. Publishing a directory again updates the item to the version in its files. To publish under a team's account you belong to, set NEBOAI_ACCOUNT=<team-handle>.
Anyone can publish, free. Every public version is reviewed:
- Text-only items (skills, employees, connectors, collections) get an automated content scan. A clean scan is approved at once and the item is listed immediately.
- Items with binaries (plugins, and apps with a sidecar) are scanned in the background, and approved automatically when the scan is clean. Plugins and sidecar apps need at least one platform binary; a page-only app needs none.
- Anything the scan flags waits for a person on the NeboAI team.
A listed item stays listed when you publish an update. More in the publishing overview and the publisher skill guide.
| Type | Files | Guide |
|---|---|---|
| Skill | SKILL.md (+ references/, scripts/, assets/) |
building-skills, skill-format |
| Employee | AGENT.md + agent.json |
building-agents, agent-format |
| Plugin | PLUGIN.md + plugin.json + binaries in dist/plugin/<platform>/ |
building-plugins, plugin-format |
| App | AGENT.md (artifact_type: app) + manifest.json + ui/, plus sidecar binaries only if it has a backend |
building-apps, app-format |
| Connector | connector.json (an mcpServers block) |
connector-format |
| Collection | collection.json |
collection-format |
Working examples are in examples/. Listing advice: listing-quality.
neboai auth login | status | logout
neboai validate <dir> [--type skill|plugin|agent|app|connector|collection]
neboai publish <dir> [--type ...] [--visibility public|private|loop]
neboai list
neboai status <id>
neboai binaries list <id>
neboai binaries delete <item-id> <binary-id>
Credentials are saved in your user config folder (~/Library/Application Support/neboai/credentials.json on macOS, ~/.config/neboai/credentials.json on Linux, %APPDATA%\neboai\credentials.json on Windows). NEBOAI_BASE_URL points the CLI at another API (for local development).
cd cli
cargo build --release
./target/release/neboai --versionBump version in cli/Cargo.toml and package.json, merge, then push a tag vX.Y.Z. The release workflow builds the five binaries, publishes them with neboai-skill.tar.gz and SHA256SUMS to the GitHub release, updates Formula/neboai.rb in NeboLoop/homebrew-tap (secret TAP_GITHUB_TOKEN), and publishes @neboai/publisher to npm (secret NPM_TOKEN).