Skip to main content
Goal: Authenticate with the devkit, validate a local plugin folder, and submit it for Marketplace review. Prerequisite: Plugin repo with valid package.json name, GitHub origin remote (HTTPS form preferred), and metadata aligned with Manifest and submit. Optional: orderly-devkit skills install — see below.

​
Using agent skills for this tutorial

The orderly-plugin-submit skill is for publishing to the Marketplace. It aligns with orderly-devkit the same way as the sections below: Full skill–MCP alignment: Agent skills alignment; overview: Skills-first workflow. Example prompts: “Prepare my plugin folder for Marketplace: dry-run then submit” / “Draft a usagePrompt for @scope/plugin matching submit constraints.” Always confirm submit in the UI or chat before the agent runs the real command.

​
1. Log in

Credentials are stored under ~/.orderly/auth.json.

​
2. Dry run (validate only)

From the plugin root:
Fix any validation errors (npm name, repoUrl, pluginId, tags, usagePrompt length). See Manifest and submit.

​
3. Submit

Optional flags:
Invalid tags are dropped with a warning; valid tags only are kept. Verification: HTTP 201 response — plugin submitted (often status under_review). See status table in Manifest and submit.

​
4. List and update listings

Update metadata for an existing listing (requires pluginId in .orderly-manifest.json):

​
5. View a plugin by id

Requires orderly-devkit login in the current CLI implementation.

​
Next steps