Bundle and publish

The SDK turns source code into a runtime artifact and manifest. The API validates both again when you publish.

Bundle

Run bundle from the plugin project root:

pnpm bundle

or:

npx itsmybot bundle .

Generated files:

.itsmybot/
  manifest.json
  runtime.js

manifest.json is derived from the plugin instance exported by src/index.ts. Do not edit generated files by hand.

Entrypoint contract

src/index.ts must export the plugin instance as default. Export defaultConfig too when the plugin has configuration.

import { Plugin } from "itsmybot";

import { GreetCommand } from "./commands/greet";
import type { Config } from "./config";
export { defaultConfig } from "./config";
import { metadata } from "./metadata";

class GreetPlugin extends Plugin<Config> {
  readonly id = metadata.id;
  readonly version = metadata.version;
  readonly name = metadata.name;
  readonly summary = metadata.summary;
  readonly category = metadata.category;
  readonly compatibilityDate = metadata.compatibilityDate;
  readonly capabilities = metadata.capabilities;
  readonly commands = [new GreetCommand()];
}

export default new GreetPlugin();

Presentation assets

Add marketplace presentation files before publishing:

README.md
icon.png
screenshots/overview.png
screenshots/settings.png

Rules:

• README.md becomes the long marketplace description.
• summary stays short and lives in plugin metadata.
• icon.png should be square, 256x256.
• screenshots can be png, jpg, or jpeg.
• max screenshots: 5.
• max screenshot size: 1920x1080.

Write README for server owners, not platform internals:

# Welcome Helper

Send configurable welcome messages from slash commands and mention replies.

## Commands

- `/greet target` sends the configured greeting.

## Configuration

- `Greeting`: text used in replies.
- `Public replies`: controls command reply visibility.

Publish beta

Publish uploads the generated artifact and opens Discord browser auth when needed:

pnpm publish

or:

npx itsmybot publish .

Publish validation checks:

• manifest metadata.
• runtime artifact shape.
• command options.
• event triggers.
• capabilities.
• config schema.
• presentation assets.

Fix source code when validation fails, then bundle and publish again.

Beta testing

New versions start as beta.

Use studio to install the beta build into selected guilds. Test:

• command registration.
• command replies.
• event triggers.
• config form behavior.
• permission and capability errors.
• marketplace presentation rendering.

Stable review

Stable versions are public marketplace releases. Request stable review only after beta testing passes.

Reviewers check:

• metadata is clear and stable.
• README explains user-facing behavior.
• screenshots match the plugin.
• capabilities match actions.
• no obvious unsafe runtime behavior.

After approval, the stable version can appear publicly in the marketplace.